cupcake
A native policy enforcement layer for AI coding agents. Built on OPA/Rego.
Runssource: GitHubhomepageRustApache-2.0commit 27b94b84f6cf
Rust, Apache-2.0 licensed. The project labels itself: agent security, alignment, claude code, coding agents, cursor, factory ai, gemini cli and hooks.
cupcake runs. An Argusic agent installed it in 18 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Cupcake 0.5.2 builds from source, the CLI binary runs (cupcake --version prints 0.5.2), supports 4 harnesses (Claude Code, Cursor, Factory AI, OpenCode), compiles Rego policies into WASM via OPA, evaluates hook events against builtin policies (git_pre_check, protected_paths, git_block_no_verify), and returns Allow/Deny decisions.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- OPA CLI not in PATH: 10 integration tests (claude_code_routing_test) failed because they invoke a real Claude CLI binary which is a third-party commercial product1 minute
- Rust toolchain not installed in container1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test --workspace exited 0 with all tests passing except 10 that require a real Claude CLI binary; cupcake eval --harness opencode on PreToolUse events matched 3 policies and produced Allow decision; cupcake verify --harness opencode compiled policies into 367KB WASM module with 5 routing entries
- Model tokens used
- 116,492
- Exact commit tested
- 27b94b84f6cf
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 8 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s All data collected. Here's the summary: **Install succeeded.** Rust toolchain (1.91.0 via rustup) and OPA CLI (1.21.4) were installed. The … **Tests pass.** 314 unit tests, 35 CLI tests, and 31 integration test files pass (exercising Claude… **CLI verified.** `cupcake --version` prints `cupcake 0.5.2`. `cupcake init --harness claude` creat… tokens used 116,492 All data collected. Here's the summary: **Install succeeded.** Rust toolchain (1.91.0 via rustup) and OPA CLI (1.21.4) were installed. The … **Tests pass.** 314 unit tests, 35 CLI tests, and 31 integration test files pass (exercising Claude… **CLI verified.** `cupcake --version` prints `cupcake 0.5.2`. `cupcake init --harness claude` creat…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 18 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-securityalignmentclaude-codecoding-agentscursorfactory-aigemini-clihooksllm-as-a-judgemcpopaopencode
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cupcake)Questions
- Does cupcake run?
- Yes. cupcake runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test cupcake?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 27b94b84f6cf. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cupcake?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cupcake take to install?
- 18 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does cupcake need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cupcake?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for cupcake?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.