Live agent console — simulated demo feed
atlasschedulertop --agents --watchsimulated feedtasks: 8 · running 5 · blocked 1
PIDAGENTMODELCTX%STATE
0x1a3fatlas-schedulerarbarbiteratlas-core44%RUNNING
0x2b07refactor-authclaude78%RUNNING
0x2b11migrate-schemaclaude31%RUNNING
0x3c4awrite-testshaiku92%WAITING
0x3c80doc-generatorhaiku12%RUNNING
0x44d2deploy-runnergpt-4o57%BLOCKED
0x51e9lint-sweephaiku8%WAITING
0x5a2cindex-embeddingsembed-366%RUNNING
schedulerarbitrating write-lease on src/auth.ts
Fifty agents. One repo. Atlas decides who writes.
OS-level process manager for autonomous agents. From Singapore.
The Atlas syscall surface
$ atlas.spawn()
fork a new agent into the supervised process tree
pid 0x6b1e spawned · attached
$ atlas.lock(file)
acquire an exclusive write-lease on a path
lease granted · ttl 120s
$ atlas.budget(ctx)
cap token spend; evict on overflow
0x3c4a evicted at 92% ctx
$ atlas.route(tier)
dispatch work to the cheapest viable model
haiku · $0.0004/req
write-lease arbitration · single-writer guarantee
refactor-auth0x2b07
write-tests0x3c4a
deploy-runner0x44d2
gate
ATLAS
mutex::auth
contested node
src/auth.ts
1 approved
2 queued · fifo
Telemetry
0 write conflicts in production340ms median arbitrationL4 isolation8 agents supervised · 1 writerGet started with Atlas
boot the arbiter
$ atlas init
one binary · attach your agents · Atlas holds the write-lock from there