Three agents, one project
Each teammate keeps their own agent. All of them connect to the same Venom project.
You can use Claude Code, Codex and Cursor on the same project by connecting each one to the same Venom project. Each person keeps the agent they prefer. The agents share tasks, decisions, skills and tools through one remote MCP server, so there is no new harness to adopt.
What does each agent get?
Venom gives every connected agent the same guidance: read the project and task before acting, create a task for new build work, log decisions, outcomes and next steps, and check mentions. What delivers it depends on the client.
| Agent | Setup | Reminders |
|---|---|---|
| Claude Code | Install Venom Full. See Claude Code. | Hooks, plus the venom skill. |
| Codex | Install venom and Venom Full, and enable lifecycle hooks. See Codex. | Hooks, except PreCompact. |
| Cursor | Add the MCP server and the Venom rule. See Cursor. | The always-applied rule and a one-line reminder in tool responses. |
With Venom Full, Claude Code and Codex are shown your projects and unread mentions on the first prompt, and are asked once to log after a milestone with nothing logged. Venom Full's hooks don't cover Cursor. These all ask; the agent makes the tool calls.
Walk-through.
The checkout project belongs to a team of three. Jordan uses Claude Code, Sam uses Cursor and Lucia uses Codex.
- Everyone connects to Venom and selects the same organization. Each person's agent works with their own permissions.
- Jordan's agent creates a task, saves the design decision and the code link, and logs an open security question.
- Sam's Cursor agent reads the task and the project's review skill, checks the linked code, and logs its findings to the same task.
- Lucia's Codex agent reads both entries and continues with the next step.
Each log entry shows who wrote it and which agent they used. Nobody has to share a session or a screen. The work moves through the task.
What stays the same?
- Tasks, skills and tools are shared by the project, not by the client.
- Permissions follow the person who authorized each connection.
- Your client's approvals still apply.
What differs?
Venom Full's hooks cover Claude Code and Codex. Clients without hooks rely on their rule or context file and the reminder in each Venom tool response. A turn that never calls Venom gets no tool-response reminder, so ask the agent to read the task when you start.