Org memory
Keep the short facts your team agrees on in Venom Cloud, review what members propose, and see the exact block venom loads into a session for a repository and key group.
Org memory is a list of short facts ("Staging deploys go through make deploy-staging", "Never edit generated
files under gen/") that venom puts into a session's prompt when it starts. Each fact has a scope: the whole org or
some key groups (a key group holds API keys, daemons and policies; the API calls it team), and every repository or the ones matching a pattern. Members propose facts; admins approve, edit,
confirm and retire them.
The page is /memory, in the console's Team group. Reading and proposing need routing:read (owner, admin,
developer, viewer); adding directly, deciding and editing need org:manage (owner, admin).
Add a fact
- Open
/memory. - In the composer, write one fact (at most 500 characters, plain text) and set its owner (who to ask about it).
- Pick the scope: the whole organisation or some key groups, and optionally a repository pattern such as
acme/weborgithub.com/acme/*. - Choose Add (owners and admins) or Propose (everyone else). An added fact is live from members' next session; a proposal waits for review.
From the CLI, members propose and read facts with:
venom memory propose "Integration tests need docker compose up first" --repo
venom memory org refresh--repo limits the proposal to the current repository, --team to your key group (the one your key belongs to).
The page
| Part | What it does |
|---|---|
Tabs Approved, Waiting for review, Rejected (?tab=) |
each with a count |
| Search | filters the facts by text |
| Fact row | text, scope, owner, how it came in (console or CLI), and "Confirmed n days ago"; after 90 days a review badge |
| On a proposal | Approve, Edit, Reject, each with an optional note for the proposer (500 characters) |
| On an approved fact | Still true (confirms it today), Edit, Retire |
| What venom loads | pick a repository and key group: the block venom puts in the prompt, word for word, with its size against the 4,000-character budget |
Venom loads the approved facts whose scope includes the member's key group and the repository of the checkout. Facts past the budget are left out, and the block says how many were hidden.
Limits
| Limit | Value |
|---|---|
| fact text | 500 characters |
| approved facts per org | 100 |
| pending proposals per org | 200 |
| owner | 120 characters |
| repository pattern | 200 characters: owner/name or host/owner/name, * within a segment, ** across segments |
| decision note | 500 characters |
| proposals from the CLI | 20 per key per day |
| loaded block | 4,000 characters |
A duplicate (the same words, ignoring a leading "remember that") is not added twice. A fact that looks like a
secret is refused. The audit log records memory.* events with the scope, a hash and the length, never the text.
Troubleshooting
| Message | Cause and fix |
|---|---|
| "A memory is at most 500 characters: one fact, said briefly." | split it into several facts |
| "A repository pattern is owner/name or host/owner/name…" | use a form like acme/web or github.com/acme/* |
| "A pattern that matches every repository is the same as none: leave it empty." | clear the pattern field |
| "Your role cannot change the org's memory (org:manage)." | use Propose; an admin reviews it |
| A fact doesn't appear in sessions | check its scope in What venom loads; it may be past the 4,000-character budget |
Related
- Context and memory: how venom combines org memory with its own.
- Team library and starter packs: starter packs can add memory facts.
- Venom Cloud