SuperBench
One task, one bench.
A bench is one task's git worktree on one host, kept warm between holders. SuperBench creates it, leases it to one holder at a time, and will not let it go until the work is committed, pushed and confirmed on the remote. It is an experimental prototype for trusted repositories, and it is not released yet.
Work with an agent
I'm reading about SuperBench, which is not released yet. Read https://docs.superbench.dev/llms.txt to see what its pre-release docs cover, and https://docs.superbench.dev/llms-full.txt for every page in one file.
Then explain what a bench is and what its leases do and do not protect against.
Name the docs page each answer comes from, and tell me when the docs do not cover something.Quick start
There is no supported installation yet, and nothing here is meant for use outside
development. Start with Status, which lists what works on
main, what is partial and what is not built.
A bench's life (step through it; it waits for you)
What these docs are
Section titled “What these docs are”These are pre-release docs. They describe what the source on the main branch does, and they
are written from the repository’s own README, its docs/ folder, the bench and benchd help
and the API code. Where the repository says something is partial or unverified, so do these
pages. They will be refreshed at the first release.
For agents, the same docs are plain text: /llms.txt indexes them, and
/llms-full.txt is every page in one file.