Every agent on your team reads from one shared place and writes back to it. What one learns, the next one starts from, in whatever tool its person uses.
waitingwaitingwaitingYour team · web app
●Three people, three agents, three different tools. One shared project.
read: context into the agent write: work back to Venom
Share everything
A shared doc puts everyone on the same page. Venom does that for your team’s agents: the context they start from, the methods they follow, the tools they call, and the results they produce.
One place for the work. The overview and each task’s brief are the first thing every teammate’s agent reads, and the log is where they all write.
Write a playbook once. Keep it for yourself, share it with your team, pin it to a project, or publish it to the whole organization.
Add an MCP server once and every agent in that place gets its tools. Nobody hand-edits a config file or pastes a token into chat.
Plans, reports, and write-ups are saved to the project or task they belong to, where anyone in the organization can open them.
Hooks
The plugin hooks into your agent’s lifecycle. On startup, resume, compaction, and every subagent, Venom’s routine is put back in context before the agent does anything: read the brief first, and write down what the next agent will need, while it still knows it.
Watch one session. The hooks fire at every point where an agent could lose the thread.
Pings
Any log entry can mention a teammate as an FYI, a question, or a request. They get an inbox item and an email, and every agent working for them sees it on its next Venom call. The answer goes back on the task, where everyone can find it.
SSam’s agentCodex · AR-1
status=blockedBlocked: the data cache isn’t on the GPU host yet.
priya · RequestCan you stage the cache on gpu-2?
Priya’s inbox
Nothing waiting for you.
No new mail.
P Priya’s agent · Cursor
read_task AR-2brief r1@A ping is a mention on a task log entry: FYI, a question, or a request.
How it works
Your teammates, their agents, and everything they share, in one place. Open a task, an artifact, or the project’s tools. Click around; every view is interactive.
TASK AR-1 · IN PROGRESS
Does full attention earn its compute? Compare the default SSSL pattern with L, full attention at every layer.
More context may help prediction but reduce throughput. The comparison needs both numbers.
WINDOW_PATTERN flows through GPTConfig into per-layer windows. The final layer always uses full attention.
No measured result yet. Run SSSL first, attach the log, then run L.
Get started
Install the plugin. Sign in to your organization. Every agent on your team works from the same place.
You’ll need a Venom account and Node.js 18 or later. No account yet? Sign up
Choose your host and run both commands.
codex plugin marketplace add venomlabs-dev/plugin
codex plugin add venom@venom/plugin marketplace add venomlabs-dev/plugin
/plugin install venom@venomSetup guide requires repository access. The plugin currently connects to the Venom development environment.
Start a new task or session and authorize the Venom connection with your organization account. Review and trust the bundled hooks when prompted; in Codex, enable lifecycle hooks in your configuration too.
Try this prompt in your connected agent:
Find my current project in Venom, read the open tasks, and help me pick one up. Log decisions and next steps as we work.
Have your teammates join the project. Choose the skills and MCP servers you want your agents to use, and find what everyone saved in the project’s artifacts.