Gives your agent persistent terminals and lets it launch and steer other coding agents inside them.
Caveat CLI
quolu · Agent
Caveat is a long-term memory layer for Claude Code, Codex and Cursor. You record an external-spec quirk or a repo-specific oddity once, and the relevant note surfaces before an AI repeats the mistake. Entries live in your own knowledge repository, and you can subscribe to repositories kept by teammates or a group. Sync sends private and public entries to a private remote owned by you or your group, and publish writes only public entries to a public mirror as an encrypted bundle.
Written by ooruby from the README of caveat-cli 0.20.3.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
A trap you have already found does not have to be rediscovered by your coding agent in its next session.
What you could do with it
- Search your own entries and subscribed repositories for a note about a tool that keeps failing the same way.
- Subscribe to a teammate's notes repository and pull its latest entries into your own searches.
- Let your agent record a new note through its MCP tool after it hits a repo-specific oddity.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Long-term memory CLI for Claude Code, Codex, and Cursor (markdown + SQLite FTS5 + MCP + hooks)
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.20.3, the file with digest sha512-GiTNzI2bQrmJ6SSd1sfX4DR/VrG6IBtlFPrmy8JZae/3zwEim6iwr9msCK1GCrsuJB0cR3zeSesrUNTx+rf4dw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y caveat-cli@0.20.3Pinned to 0.20.3, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- caveat-cli
- Version read
- 0.20.3
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/kitepon/caveat
- Commit
- 7eb238f28bc1
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/caveat-cli)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-07
More from quolu
See the storefrontSimilar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.