Claude Code sessions in Venom
Install the Venom plugin for Claude Code so each finished session shows up in Session history and feeds the Inbox of Venom Notes, redacted on your machine and sent only to your own cloud.
Sessions you run in Claude Code do not pass through Venom Cloud, so Session history and the Inbox of Venom Notes stay empty for a team that works there. The Venom plugin for Claude Code closes that gap: when a session ends, it writes a short summary and sends it to your own cloud.
Install
In Claude Code:
/plugin marketplace add elishahbiz/venom
/plugin install venom@venomFrom a shell, the same two steps are claude plugin marketplace add elishahbiz/venom and claude plugin install venom@venom. From a local checkout, use its path: /plugin marketplace add /path/to/venom.
Then sign in once so the hook knows your cloud:
venom cloud loginThe hook reads the credentials that command keeps in ~/.venom/cloud.json. Without venom installed, set VENOM_CLOUD_URL and VENOM_CLOUD_KEY (a vck_ key from the console) in the environment Claude Code runs in; the variables win over the file.
The plugin also brings a set of skills (plain writing, audits, doc sync, Linear plans, RCAs, migrations, security audits) to every project: see Skills in the Venom plugin.
What gets sent
On SessionEnd, a Node script (Node 22 or newer, no dependencies, no model call) reads the session transcript and builds:
| Field | From |
|---|---|
| Goal | your first prompt |
| Result and outcome | the last answer (partial when the last tool call failed, abandoned when Claude never answered) |
| Files | files Claude edited or wrote |
| Decisions | plans from plan mode, markdown files it wrote, and the first few commands it ran |
| Model, repo, branch | the transcript and git remote get-url origin |
| Tokens, messages, duration | the transcript (cost is not in Claude Code's transcript, so it is 0) |
A session with no tool call and fewer than three messages sends nothing.
Before anything leaves the machine the summary is redacted with copies of the detectors venom itself uses: API keys and tokens, private keys, JWTs, passwords in URLs, secret-looking assignments, email addresses, phone numbers and your home directory. The cloud refuses a summary that still looks like it holds a secret.
The summary appears in Session history with a Claude Code badge, next to venom sessions, and Notes reads it into the Inbox of the member whose key sent it like any other summary (see How Notes learns).
Your org's switch
The org setting Collect session summaries applies. While it is off (the default), the hook sends nothing and prints one line saying so; it stays quiet until collection is turned on and off again. An admin turns it on under Sessions, History. Without credentials the hook prints one line pointing at venom cloud login.
The only network call is to your own cloud (/v1/session-summaries/settings, then /v1/session-summaries), made by the hook after a session ends. The hook has a short timeout, swallows every error and always exits 0, so it never blocks or fails a Claude Code session.
Upload API
The plugin uses the same endpoint as venom, POST /v1/session-summaries, with "source": "claude-code". source is venom (the default) or claude-code, and the admin list returns it. The session id is cc- plus Claude Code's session id, so a re-run of the hook replaces the earlier summary.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
"session not sent: run venom cloud login" |
No credentials. Sign in, or set VENOM_CLOUD_URL and VENOM_CLOUD_KEY. |
| "your org does not collect session summaries" | An admin turns on Collect session summaries under Sessions, History. |
| Nothing arrives and no message | The session was too short, or node is older than 22. Run node --version. |