Hey everyone, another question from the Velozity team as we get closer to launch.
Last time we asked how AI work moves between people on a team. This time we want to dig into trust.
Right now most people keep their AI on a short leash: it drafts, it suggests, but a person clicks send. That's safe, but it also means every handoff between a person and their AI, or between two people's AIs, still needs a human in the loop to move things along.
We're building Velozity so agents can work more directly inside a team's shared space, chat, tasks, files, calendar, with a person approving anything that leaves the workspace rather than approving every single step along the way.
The guest room is clever. Sharing work with a client without exposing everything else is something I always struggle with.
@sanika_gujar Thanks, Sanika. That struggle is exactly why we built it.
A client comes in on a guest pass. They get limited access to your office and can meet you there without becoming a member of your workspace.
You also choose how long the pass lasts, and you can revoke it anytime. When the project ends, their access ends with it, and there's nothing to clean up afterward.
If you try it with a client, I'd love to hear how it goes.
@sanika_gujar
Thanks Sanika, that struggle is exactly why we built it. The client sees only the room you open for them, and everything else stays private.
@stormshot Yes, we built on open standards wherever one exists, so nothing here is a proprietary lock-in:
Tools for agents: Model Context Protocol (MCP). Everything an agent can do inside Velozity (read a space, post a message, drive the browser) is offered to it through MCP, the same standard Claude Code and Codex already use.
Talking to agents: Agent Client Protocol (ACP). Gemini, Kimi, OpenCode, and Cursor agents run over ACP. Claude Code and Codex are run through their own official command-line tools, unmodified.
Sign-in and connected apps: OAuth. You log in on the provider's own page, and we never see your password.
Calls and screen sharing: WebRTC.
If you meant a specific standard, such as a security certification or a data regulation, tell me which one and I'll give you a straight answer.
@stormshot
Yes. Data is encrypted in transit (TLS 1.2+) and at rest (AES-256), connected apps sign in through OAuth with limited scopes, and we follow GDPR and CCPA. Your data is never used to train AI models, and the cloud infrastructure we run on is independently audited (SOC 2 Type II, ISO 27001).
Details: velozity.ai/privacy
The difficult part is transferring work from one person/agent to another. Is it possible for me to delegate a task to an agent through a chat conversation or through a call transcript and get responses on the same thread?
Btw, Congratulations @ishudarshan and @see_akash 🎊✌️
@aymi_malik Thank you, Muhammad! And yes, that hand-off is exactly what we built for.
From a chat: tag an agent in the conversation, the same way you'd tag a teammate. It already has the context of that Space, so you don't re-explain anything, and it replies right there in the same thread.
From a call: the call is transcribed, tasks are created from what was agreed, and you can hand any of them to an agent. The task description becomes its brief, and the result comes back to the same Space for your team to review.
Agents can also pass work to each other, so a hand-off from person to agent to agent stays in one place and everyone can see where it stands.
@aymi_malik
Thanks, Muhammad! Yes, that handoff is exactly what Spaces are built for. Tag an agent in the conversation with the task and it replies right there in the same thread, so the request, the work and the answer stay together. Calls work the same way: once a call transcript is in the Space, you can ask an agent to pull out the tasks and follow-ups from what was said, and agents can hand work to each other too.
How does the autopilot feature decide when a page variation has enough traffic data to pick a clear winner?
@sansa_grey Hi Sansa, thanks for stopping by! Velozity doesn't do page variations or traffic testing. It's a shared workspace where your team and AI agents work together. Happy to answer any questions.
@sansa_grey
Adding to Ishu's note: there is no autopilot for page testing here, so nothing in Velozity picks a winning variation. Where it could still help a team running those tests is the work around them: the calls where you review results get notes on their own, and the follow-ups become tasks without anyone writing them up.
How much time does your team spend repeating the same context to different AI tools?
Congrats @ishudarshan & team!
Thanks for sharing @rohanrecommends!
@hamza_afzal_butt Thanks, Hamza. Honestly, it varies, and sometimes it still takes longer than you'd expect. What's changed for us is that there's no back-and-forth anymore.
Everyone works in the same space, so it feels like one ongoing conversation, a bit like a WhatsApp group where the whole team and their agents are talking together. The agents feel like teammates, and everybody stays in the loop the whole time.
@hamza_afzal_butt
Adding to what Ishu said, Hamza: the repeating mostly goes away because the context lives in the Space, not in each person's chat with a tool. The files, the conversation and the call transcripts are already there, so any agent you bring in starts from the same picture as the team. You brief once, and the next person or agent picks up where the last one left off.
The shared context between the team and AI agents is what caught my attention. Love it
@shahriardgm Thank you, Shahriar! 🙌 Shared context was the whole reason we built it. When the team and the agents work from the same conversation, files, and tasks, nobody has to explain things twice. What would you want your agents to remember first about your team's work?
@shahriardgm
The context builds up on its own as the team works, so there is no separate step of briefing the agents. A new teammate or a new agent joining later starts from the same history as everyone else, which is where it really starts to pay off.
The part I like is that agents sit alongside my teammates, so I don't have to move work between tools by hand.
@shreya_verma12 Thank you, Shreya! That's the part we care about most. Moving work between tools by hand is a hidden tax on every team, and it disappears once agents sit in the same place as your teammates. Which handoff has saved you the most time so far?
@shreya_verma12 Adding to Ishu's note: the reason it works is that the agent already has the context your teammates have, so there is nothing to copy over or explain again. A decision made in a call is already where the agent picks up the task. Curious which hand-off you would like us to make smoother next.