context-attachment-manager
A local plugin for image-heavy chats in Codex, Claude Code and other AI agents: earlier images become short placeholders instead of going out with every message, the model fetches the original back by its ID (also after compaction), and the prompt cache keeps working.
Runs with mockssource: GitHubTypeScriptMITcommit bec2d3faee86
TypeScript, MIT licensed. The project labels itself: ai agents, claude, claude code, claude code plugin, codex, codex cli, codex plugin and coding agent.
context-attachment-manager runs, with stand-ins for the services it depends on. An Argusic agent installed it in 13 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Context Attachment Manager v0.11.2 engine runs on port 17891 (health 200), all 345 unit tests pass, install/uninstall cycle verified with no errors
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.
- Node 18 is too old (project requires Node 24+)3 minutes
- Install time
- 13 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test: 345 passed, 0 failed, 0 skipped. curl http://localhost:17891/__cam/health returned 200 with JSON body confirming version 0.11.2 running. cam install self-test passed (6 MCP tools offered). cam status confirms proxy enabled, engine running, version 0.11.2.
- Model tokens used
- 53,636
- Exact commit tested
- bec2d3faee86
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec /bin/sh -lc 'cd /work/repo && export NVM_DIR="$HOME/.nvm"; [ -s "$NVM_DIR/nvm.sh" ] && '"\\. \""'$N… succeeded in 8252ms: ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 8033.802442 Everything works. Here's the final report: tokens used 53,636 Everything works. Here's the final report:
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 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
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 13 minutes to install, slower than the median of the 121 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 122 ai-agents projects Argusic has installed and timed, context-attachment-manager was the 90th fastest to reach a running state, and 94 of 122 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 | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
ai-agentsclaudeclaude-codeclaude-code-plugincodexcodex-clicodex-plugincoding-agentcontext-engineeringcontext-managementdeveloper-toolsgemini-cliimage-generationllmmcpmultimodalopenai-codexopencodeprompt-cachingtoken-optimization
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/context-attachment-manager)Questions
- Does context-attachment-manager run?
- context-attachment-manager runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 13 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test context-attachment-manager?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bec2d3faee86. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test context-attachment-manager?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does context-attachment-manager take to install?
- 13 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 context-attachment-manager need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing context-attachment-manager?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does context-attachment-manager compare with the alternatives?
- Of the 122 ai-agents projects Argusic has installed and timed, context-attachment-manager was the 90th fastest to reach a running state, and 94 of 122 reached one at all.
- Where is the evidence for context-attachment-manager?
- 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.