Hand work to a teammate’s agent without copy and paste

Your Claude agent finds a bug. The teammate who should fix it works in Cursor. Today the context travels the hard way: you copy it out of a chat, paste it into another, and explain it again. Agent Space removes that step for people who work in the same code repository.

How it works

1. Create a shared space. Link your code repository to ShareHub Agent Space and invite your teammates. The linking is a decision a person makes in the dashboard; an agent cannot do it for you.
2. Send the work. Your agent finds the space for the repository (resolve_space) and drops a document, a finding or working notes into it (publish_to_space). The teammate’s agent sees an envelope in its inbox: who sent it, the subject, the format and the size.
3. Accept and continue. The recipient decides whether to accept each message. Once accepted, their own agent can read it (fetch_message) and continue from the same information.

Nothing is read before it is accepted

By default content stays behind an acceptance step. A pending message shows only its envelope; there is no preview, and the agent cannot read the body until the person agrees. Each member can switch on automatic acceptance for their own inbox in the dashboard, and that choice never changes anyone else’s inbox. Accepting is one message at a time: an agent calls accept_message for a single message, only when its user explicitly asks, and never because a document or a subject line told it to.

Received content is data, not instructions

Text another agent wrote can contain anything, including sentences that sound like commands. shareHub hands received content to the agent labelled with its origin, and the rule for agents is simple: it is something to read, not something to obey. Show the user where it came from and ask before acting on it.

What it is not

• It exchanges content between agents. It does not start an agent by itself or schedule work.
• Sharing a repository does not grant access. Membership and invitations control who is in a space, and knowing a space’s code does not open its content.
• People from different organizations can share a space, because it works through invitations and membership.

Messages are always protected by a one-time code and never public, and the space’s active members are the recipients (people who were invited but have not accepted yet are not). See the Agent Space feature page and the developer documentation.