A self-hosted service that implements ready GitHub issues with coding agents in sandboxes, for maintainers who run it on their own machine.
Scriptorium is a factory: one process on a host serves every repository its
host configuration lists. It picks up issues a person marked ready and runs
each one's agent in a sandbox, a container built from the repository's own
toolchain image with the factory's agent layer of Git, the GitHub CLI and the
agent CLIs on top. A provider is an agent CLI and the subscription behind it,
such as Claude Code or Codex. Releases are published here as
scriptorium-vX.Y.Z tags. The stream began in Repo Canon, the shared repository
conventions this repository follows, where Scriptorium lived until
scriptorium-v1.0.5.
On a Linux host with Node.js 24 or 26, pnpm 11, Git, the GitHub CLI and Docker, check out the latest release and start the process with the host configuration's path:
git clone https://github.com/lutzseverino/scriptorium.git
cd scriptorium
git checkout "$(gh release view --repo lutzseverino/scriptorium --json tagName --jq .tagName)"
pnpm install --prod --frozen-lockfile
node src/main.ts /etc/factory/host.jsonscriptorium-v1.0.5 and earlier install from
Repo Canon's releases
instead, from the checkout's factory/ directory.
Host installation and configuration covers the host configuration, the token command, the state directory and restarts; the host keeps its own service definition and credential files.
- Serves many repositories from one process, with one oldest-first queue.
- Accepts readiness only from a person holding a role the host authorizes.
- Builds each toolchain image from the repository's
.scriptorium/Dockerfile. - Removes its own obsolete images after it builds, and its old build cache when a host opts in.
- Caps each provider's concurrent sandboxes and stops its new claims at high usage.
- Pauses a provider's runs near or at its usage limit and resumes them unattended.
- Holds a drained provider's new claims until its owner resumes it, when the host asks.
- Retries a failed first attempt once, on the host's retry model.
- Restarts without spending a run's retry.
In a repository the host serves, a maintainer marks an issue ready and picks its model:
gh issue edit 42 --add-label state:ready --add-label model:claude-opus-5-5On its next pass the factory labels the issue factory:running, runs the
agent on branch factory/issue-42, and keeps the claim while the agent's pull
request is open.
The operator owns the host configuration.
Each repository owns its factory configuration,
.scriptorium/config.json, and its toolchain image, .scriptorium/Dockerfile, under
the sandbox image contract.