antil gives every worker its own running app, shares the heavy resources, and is building seals that reuse tests only when their code and environment still match.
apps & urls
Every worker gets its own running app, ready only when it answers.
shared resources
Run the heavy server once. Give every worker its own room inside.
proof & cache
Same code and environment: reuse the proof. Changed or unknown: run.
start in 5 minutes
Section titled “start in 5 minutes”Run a shop with a Vite storefront, a Node API, Postgres, Redis, and checkout tests. Give two agents separate worktrees and open both shops side by side.
run the shop →You need macOS, Git, Node.js, Bun, Docker Desktop or OrbStack, and the antil binary. Allow extra time for the first container download.
what works today
Section titled “what works today”Tunnels: local HTTP addresses, separate ports, and checked readiness. Chambers: one Postgres engine with a private database per worker, or an explicitly shared seeded database. Seals: coming; named test commands run today, but every new test request runs again.
Recipes for Redis, object stores, and other resources are coming. The shop uses Docker Compose to share Redis manually. Private-network HTTPS is coming.
A worker means you or an agent working in one git worktree. “Private database” means separate working data for cooperative workers; antil is not a security sandbox for untrusted code.
one foundation
Section titled “one foundation”All three parts rely on the same foundation: one JSON contract for agents, work that survives a daemon restart, and no automatic repetition when an earlier command’s outcome is unknown.
free here. cloud across machines.
Section titled “free here. cloud across machines.”The local tool is free and open source, for you and your agents. antil cloud is paid and in early access. Sharing proof, trust, or resources across people and machines belongs to cloud and is not available yet. Local seals are planned as part of the free tool. See what comes next.