actionbook
Let your AI agent get the sources behind logins and paywalls.
Runs with mockssource: GitHubhomepageRustApache-2.0commit 0e31254cc10a
Rust, Apache-2.0 licensed. The project labels itself: ai agents, browser automation, rust and skills.
actionbook runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Actionbook CLI v1.6.0 builds, reports version and help; MCP server starts and reaches the live API; JSON UI renders reports to HTML; SDK, MCP, tools-ai-sdk, openclaw-plugin, and json-ui packages all build and their 169 unit tests pass; the Rust CLI passes 482/483 lib tests (1 test requires lsof which is not available)
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 92 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.
- Rust CLI test diagnose_port_holder_returns_pid_for_occupied panics because lsof is not in the container2 minutes
- pnpm not on PATH after npm install to --prefix1 minute
- tools-ai-sdk test mock used getActionByIdDescription/getActionByIdSchema but get-action-by-id.ts imports getActionByAreaIdDescription/getActionByAreaIdSchema1 minute
- dify-plugin test requires `uv` (Python package manager) which is not installed
- Install time
- 8 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- actionbook --version returned '1.6.0'; actionbook --help printed full usage text; pnpm --filter @actionbookdev/sdk test exited 0 (78 passed); pnpm --filter @actionbookdev/mcp test exited 0 (45 passed); pnpm --filter @actionbookdev/tools-ai-sdk test exited 0 (7 passed); pnpm --filter @actionbookdev/openclaw-plugin test exited 0 (39 passed); node packages/mcp/dist/cli.js printed 'Server started' and 'API health: ok'; node packages/json-ui/dist/cli.js render example-report.json produced valid HTML; cargo test --lib -- --skip diagnose_port_holder... exited 0 (482 passed); all 6 build artifacts exist in dist/ or target/
- Model tokens used
- 98,397
- Exact commit tested
- 0e31254cc10a
- 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
- Behaviour against real services
- this run was verified against stand-in services only
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 2, 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.
[2026-11-14T04:25:15.859Z] [INFO] [Actionbook MCP] API health: ok exec /bin/sh -lc 'export PATH="$HOME/.cargo/bin:/home/runner/bin:$PATH" && echo "---CLI UNIT TESTS (excl… succeeded in 706ms: ---CLI UNIT TESTS (excluding lsof test)--- test result: ok. 482 passed; 0 failed; 0 ignored; 0 measured; 1 filtered out; finished in 0.76s ``` ``` tokens used 98,397 ``` ```
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
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 8 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
Of the 124 ai-agents projects Argusic has installed and timed, actionbook was the 76th fastest to reach a running state, and 96 of 124 reached one at all.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.08 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.06 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/actionbook)Questions
- Does actionbook run?
- actionbook runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test actionbook?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0e31254cc10a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test actionbook?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does actionbook take to install?
- 8 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 actionbook need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing actionbook?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does actionbook compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, actionbook was the 76th fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for actionbook?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.