Share context across a team
Log what your agent did and decided to a shared task, so a teammate's agent can read it before it starts.
To share context between Claude Code sessions across a team, have each agent log what it did and decided to a task in a shared Venom project. A teammate's agent reads that task before it starts, in Claude Code or in any other connected agent. Nothing is copied between sessions. Both agents read and write the same record.
Collaboration is asynchronous. Jordan's agent saves its work, and Sam's agent reads it later. Neither sees the other's session.
What gets shared.
A task in a project holds four things:
| Part | What it holds |
|---|---|
| Brief | The current objective, constraints, and completion criteria. |
| Log | Updates with a summary and body, and the person and agent who wrote each one. |
| Status | Where the work stands: open, in_progress, blocked, done or cancelled. |
| Artifacts | Plans, reports, and other deliverables saved to the task. |
The log is for outcomes, decisions and their reasons, useful evidence, blockers, and next actions. Code stays in its repository; the task links to it.
How do you share it?
Connect each person's agent to the same project.
Everyone on the team connects their agent to Venom and selects the same organization. See Connect with MCP or the Quickstart.
Work from a task.
Jordan asks the agent to read the checkout project and resume or create a task. The agent is told to read the task before it acts, and to create one for new build work.
Log at milestones.
The agent is told to log decisions, outcomes and next steps, and to keep the status true. Jordan's agent might record the design decision and an open security question. With Venom Full in Claude Code or Codex, the agent is also reminded to log after a commit or pull request, and asked once more at the end of the turn if nothing was logged.
How does a teammate's agent find it?
Sam starts a session in any connected client. Venom's guidance tells the agent to check mentions, find the project with list_projects and read_project, then read the task's brief and recent updates. If Sam gives it a task ref such as checkout-1, it opens that task directly.
Sam's agent adds its findings to the same task. Jordan's next session reads them.
What stays private?
The shared record holds useful context, not a copy of every conversation. Agents are told to skip routine tool calls and transcripts, and never to include secrets. Unsaved chat is not recovered.
Other limits:
- Content never crosses from one organization to another.
- A connection works in one organization, with the permissions of the person who authorized it.
- Personal skills and personal MCP servers stay with their author.