agent-chaperone / agent-chaperone
“Screens an AI agent's tool calls before they run and tool results before the agent reads them. An MCP proxy plus a hooks adapter for a client's built-in tools.”
Jev-Based rank #180In Eval #34
- 1Stars
- —Stars Δ / 1d
- —Stars Δ / 7d
- —Stars Δ / 30d
- 1Forks
- 0Watchers
GitHub ↗Official docs ↗Back to ranking
TL;DR
agent-chaperone/agent-chaperone showed up as Jev / System One related work: Open replica or independent decision engine — not Jev, not endorsed.
The author describes it as: “Screens an AI agent’s tool calls before they run and tool results before the agent reads them. An MCP proxy plus a hooks adapter for a client’s built-in tools.” That is their claim, not a bench this site ran.
Who it’s for
- Agent / harness authors who need a typed gate, route, or prune step
- Computer-use and browser-loop authors who already have text state from OCR or the a11y tree
- Anyone who needs the unofficial line: jev.pro does not issue keys and is not TypeSafe
What’s inside
Top-level entries on GitHub at generation time: .changeset, .editorconfig, .github, .gitignore, .prettierignore, .prettierrc, AGENTS.md, CHANGELOG.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, CURRENT_STATE.md, LICENSE, NOTICE, README.md. Read those before you trust a one-line install.
How to use
- Clone and follow the author’s TypeScript toolchain. Do not invent a package name.
git clone https://github.com/agent-chaperone/agent-chaperone.git
cd agent-chaperone
- If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
- Send a complete
stateand typed questions. Code owns control flow after the probabilities.
Hosted Jev still looks like a function call — wrapper or not:
{
model: "jev-1.13.0",
state: { source: "agent-chaperone/agent-chaperone", brief: "..." },
questions: {
gate: { type: "noul", instructions: "Should we act on this state?" },
route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
},
}
Try this
One typed action per frame
Using agent-chaperone/agent-chaperone, send Jev a text brief of the current screen and ask for Choice{click, type, wait, give_up}. Do not ask Jev for coordinates or screenshots — it is text-only.
Schema-safe ≠ correct
On a case agent-chaperone/agent-chaperone gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.
FAQ
Does this replace the TypeSafe SDK?
Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.
Are the star chips live?
Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.
Sources
Public repository metadata and TypeSafe documentation. No private claims.