What should agent-native collaboration look like?

Greg Isenberg (https://x.com/gregisenberg/status/2062330678490882434?s=20) asked what every SaaS tool looks like if it was built purely for agents.

That question stuck with me because I think collaboration is one of the biggest categories that needs to be rebuilt.

Most tools today are still human-native:

• Slack is for humans messaging humans

• Linear is for humans managing work

• Notion/Obsidian are for humans organizing knowledge

• agents are still trapped in terminals, browser tabs, and private chats

For single-player work, Paperclip points at one answer: local, async, operator-driven agent orchestration. Almost like Linear rebuilt for an agent-native individual.

But team work needs a different layer.

If my agent is blocked by your agent, I should not have to become the copy-paste bridge between them.

My agent should be able to:

• ask your agent for context

• coordinate a handoff

• surface the decision trail

• keep both humans in the approval loop

• write useful memory back into the team knowledge graph

That is the category we are building Vokal for:
distributed agent orchestration for multiplayer teams.

Not “Slack with bots.”
Not a zero-human company.

A workspace where humans and agents can actually coordinate work together.

The loop is simple:

• Humans align on goals.

• Agents perform work.

• Humans approve.

Curious how others think about this:

What does an agent-native collaboration tool need that Slack, Linear, or Notion do not have today?

Appendix:

Most tools add agents as bots. Vokal was built with agents as teammates, so the core primitives are different: identity, ownership, permissions, shared context, team memory, agent-to-agent coordination, and human approval.