Dependencies
Reuse package downloads in fresh sandboxes. Keep dependency setup from repeating work already done in CI.
Coding Agents
Fresh sandbox.
Less repeated build work.
Give coding agents access to dependencies and compiler results your trusted builds already published. Spend less time preparing the same environment in every worktree.
Trusted CI
Publishes build cache
BoringCache workspace
Dependencies
Compiler results
Docker layers
Sandbox 1
Read-only cache
Sandbox 2
Read-only cache
Share build state across separate sandboxes.
Each agent keeps its own checkout. Compatible builds can use the same workspace cache while their new outputs stay local.
Compiler results
Reuse completed compilation across compatible builds, even when agents work in separate environments.
Docker layers
Reuse image layers and tool caches when agents build and test inside Docker.
Restore during environment setup.
Commit cache settings in .boringcache.toml, then run the CLI from a compatible sandbox’s setup hook. Use a credential limited to restore access as well as the read-only command.
For a Node.js project, this restores the npm package cache before installing dependencies.
Set up an agent sandbox →workspace = "my-org/app" [entries.npm] path = ".npm-cache" tag = "npm-cache" [profiles.ci] entries = ["npm"]
boringcache run --profile ci --read-only -- npm ci --cache .npm-cache
Agents read.
Trusted builds publish.
Give agent environments read access to a workspace. Keep publishing credentials in trusted CI, so agent changes cannot replace shared cache.
Configure agent access →Agents read. Trusted builds publish.
- Trusted CI Publish cache for the next agent, developer, or CI job Read + publish
- Agent sandboxes Read shared cache and keep new build outputs local Read only
Connect the builds your agents already run.
Use the same workspace for CI and compatible local or sandbox builds. Onboard your repository, then run builds with read-only cache access.
boringcache onboard boringcache cargo --read-only -- test