Launched this week
Vokal
A collaboration space for 10x teammates with their Al agents
1K followers
A collaboration space for 10x teammates with their Al agents
1K followers
Your Codex and my Codex can’t talk, so we play human telephone in Slack: copy prompts, paste summaries, ask for reviews, and lose the run. Vokal brings 10x teammates and their agents into one live workspace in minutes, whether they run local Codex, Claude Code, or Hermes — or in the cloud. Name your agents, give them roles, access, and memory, and work will happen in a shared collaboration space instead of through copy-paste handoffs.
Congrats on the launch! Curious what happens when two agents disagree on the same task does Vokal flag the conflict somehow or just pick one of the outputs?
Vokal
@munis_abbas We don’t silently pick one output.
If two agents disagree, their outputs stay visible in the same task/thread with agent identity and context attached. The team can compare the reasoning, ask a follow-up, or assign a reviewer agent/human to reconcile it.
For us, the important part is not pretending agents always agree. It’s making disagreement visible enough that a human can make the final call instead of losing one side in a private chat.
How does Memory / Knowledge Base work in practice? Is it more like saved prompts, team decisions, or both?
Vokal
@shijun_liu So agents have local memories, Knowledge Base is team level. Majority of them are saved and updated by agents automatically when it make sense, but human can also manually update, as well as add external knowledge (thinking processes, values, runbooks, etc.) to the workplace.
The Slack copy paste problem is very real once different people start using different AI tools. I like the idea of agents having roles and owners instead of everyone keeping their own private workflow. The useful part for teams might be less abt adding another AI tool and more abt making the work visible enough for others to review and continue. How does Vokal handle permissions when one agent needs context from another teammate's workflow?
Vokal
@ada_johnsen That’s the exact problem we’re trying to avoid: shared context should not mean blanket access.
In Vokal, agents are workspace members with an owner, role/profile, channel membership, permissions, and optional connected-app access. If the context is in a shared thread/channel/task where the agent is a member, the agent can work from that context. If it comes from an external tool, the agent needs the right connected-app grant/account for that role.
If the context is private to another teammate or outside the agent’s granted tools, Vokal does not magically give the agent access. The teammate can bring the context into the shared thread, create a handoff, or grant the right app/account access.
So the model is: make work visible where the team chooses to collaborate, but keep access scoped by channel membership, agent role, and app grants.
DeckSpeed
The emphasis on visible work is important. If agents are doing meaningful tasks, teammates need goals, blockers, outputs, and review history.
Vokal
@hanzhizhang0405 Exactly. Once agents move from 'personal assistant' to doing real team work, visibility becomes part of the workflow, not a nice-to-have.
For each meaningful agent run, the team should be able to answer: what was the goal, what context was used, what changed, where is it blocked, who reviewed it, and what should be remembered for next time.
That is the layer we’re building Vokal around.
How granular are the app permissions? I’d want agents to access the right tools without giving them the whole company.
Vokal
@song_kirby That is exactly the control model we care about. App access is scoped to the agent/profile, not just “connect the company account and let every agent use it.”
In practice, an agent can inherit the app access its role needs, and you can also override or directly grant access for a specific agent. We also track which connected account/toolkit is assigned, whether access is ready or missing, and which agents are using which apps.
For sensitive actions, our bias is review-first: let agents read the context they need and prepare drafts or handoffs, rather than silently mutating external systems.
So the goal is right agent, right app/account, visible usage. Not blanket access to the whole company.
the copy-paste handoff between slack and whatever agent you're running is so real. half my team's context gets lost in that gap. one workspace where the agents and humans are in the same thread makes way more sense than the screenshot-in-slack workflow we're doing now
Vokal
@tina_chhabra Exactly. The screenshot-in-Slack workflow loses the important parts: the prompt, source context, intermediate reasoning, tool actions, corrections, and why the final output changed.
Our goal with Vokal is to make the agent run itself part of the team thread, not something that happens elsewhere and gets summarized afterward.
So humans can ask, agents can work, teammates can add context, and the handoff/review stays in one place.
Jinna.ai
Congrats on the launch! I’ve seen a few projects like these, and my experience tells me that indeed, keeping team in sync becomes a bottleneck in this fast AI dev tooling world.
How does your tool approach integration with team’s agents, for instance Claude/Code? Does it replace the «brain» of that tools with its own, or integrates it via MCP/other means, or both?
Vokal
@nikitaeverywhere Great question! you own agent memory stays where it is. Vokal just provides ACP+MCP to integrate your local agents with the team.