@orkastery/cli 0.6.10MIT Conduct 20 roadmaps with the calm of conducting one.
Orkastery is the platform that conducts your coding agents in parallel threads, proves every delivery against the repository and only calls you when the decision is truly yours.
No server and no built-in LLM. It runs on your Claude Code and Codex subscriptions.
One layer conducts all your runtimes, on all your machines.
You conduct from a single conversation. The ork CLI reserves the roadmap items, spreads the threads across machines, runtimes and accounts, isolates each one in its own worktree and brings everything back through a serialized merge.
main serialized merge, one at a time billing-api ✓ ls-remote2. pricing3. docs-modes ork roadmap pegar · each machine reserves the item before it startsEach thread writes only to its own worktree. Writing anywhere else is blocked by a lease, with a queue.
ork thread new One merge at a time. A push only counts when the remote confirms the SHA.
ork ship Quota exhausted or login lost: the same prompt carries on in the next profile. Subscriptions only; a paid key in the environment is cost.violation.
ork accounts add Before starting, each machine reserves the roadmap item. Two never take the same one.
ork roadmap pegar Agents got good. Conducting agents, not yet.
Point three agents at the same repository and you get three agents tripping over each other, plus a report saying everything went fine.
ork verify reruns the command on the real HEAD, and CI reruns it again on a clean runnerork docs verificar fails the PR when a page divergesMany products, one person, no burnout.
Run roadmaps in parallel on your own subscriptions. Stop switching between twenty terminals and being the status report of your agents.
Governance that does not depend on trusting the agent.
Independent CHECK on the exact SHA, proven push, decisions recorded with the why and the cost of changing. Since 0.6.9, Ork Mesh brings every builder’s work into one company network and requires the factory receipt in Git before the merge. Governed memory with OrkMind when the team needs it.
How much autonomy do you give the factory? Write a #TAG.
The factory was built to work with a lot of autonomy. The #TAG in the request sets the points where it calls you to decide or approve, the HITL (human-in-the-loop) points. Outside them, it carries on by itself. Delivery verification is the same in all four modes.
ork init default: delicate premises with reliable delivery.The mode sets the autonomy. Verification is always the same.
The simple decisions, Orkastery makes for you. You decide only what matters.
Every question from ork arrives short and organized, with alternatives and a recommendation, so you can decide in seconds. That lightness is a design goal, and it also has people with ADHD in mind.
ork board How many items are pending, urgent, blocking a thread or critical, and whether it can send them now.
Up to 5 objective ones at a time, with alternatives a–d and one recommended. Then, up to 2 open ones.
Recorded with the why, how to change it and the cost of changing now or later. You are informed.
A missed deadline waits or escalates. An answer only counts with the proof of the authenticated channel.
The factory does not stop when you sleep.
You close the laptop at 23:00. This is what the ledger records until coffee. Nothing here needed you.
Six threads open on three machines, each in its own worktree. None touches the files of another.
checkout-v2 failed two tests against the baseline. It goes back as GO-FIX with a typed spec, without waking you.
The quota of the claude-bg/personal profile ran out. The same prompt carries on in the claude-bg/team profile.
billing-api in a serialized merge. The push only counted when git ls-remote matched the local SHA.
An obvious decision made and recorded: the why, how to change it and how much changing costs now or later.
Six phases no agent skips.
Each phase has a contract. The result does not depend on believing the agent’s report. Tap a phase.
claims.unverifiableartifact.missinglease.busyclaims.failed · verify.regressiongit ls-remote matches the local SHA.git ls-remoteledgerEvery number has the command that proves it.
Reproducible commands check the work on the real tree. The baseline separates regression from earlier debt.
$ npm --prefix core run test:ci $ ork eval --so-cenarios $ ork eval --so-skills $ ork docs verificar ork demo30 s · no account · no modelork demonpm test -- soma.spec.tsclaims.failed · 2 of 5 cases on HEAD a41f9c2npm test -- soma.spec.tsStable local verify on a VM whose CPU is stolen by the hypervisor. On that machine, the reliable proof is CI.
Account state shared across projects, on the roadmap as RM-040.
Start conducting today.
Install in a minute. Run ork demo and watch a false claim get rejected in 30 seconds.