Run a backlog from the chat ​
Hand orc a stream of work, so that it places each task on a machine and an account with room.
Before you begin ​
- A task that ran by hand, as Run your first task shows.
- pueue on each machine that runs tasks, with its daemon started by
pueued -d. - A command that prints each account's room, or one login and the always-room command The backlog and the beat shows.
Name the machines and the accounts ​
To tell the beat where tasks may run:
- Save
~/.orc/backlog/dispatch.jsonwith each machine, its slots, its start command, and the quota.
{
"machines": [
{ "name": "mac", "slots": 2, "start": ["orc", "runner", "start"] },
{ "name": "linux-box", "slots": 4, "start": ["orc", "runner", "start", "--", "ssh", "linux-box", "orc"] }
],
"quota": {
"provider": "anthropic",
"command": ["my-quota-reader", "--json"],
"accounts": [
{ "name": "main", "tokenFile": "/Users/me/.secrets/main-token" },
{ "name": "second", "tokenFile": "/Users/me/.secrets/second-token" }
]
}
}Name the projects ​
To tell the beat where each project's checkout is:
- Save
~/.orc/backlog/projects.jsonwith each project and its checkout on each machine.
{ "projects": [{ "name": "orc", "checkouts": { "mac": "/Users/me/code/orc", "linux-box": "/home/me/code/orc" } }] }Start the beat ​
To start what can start every few minutes:
- Add
orc beatto cron or launchd on the machine that holds the backlog. - Run
orc beatonce by hand and read its lines.
Each line names what the beat did or why a task waits.
Add tasks and give them a priority ​
To hand over the work:
- Run
orc chatand say the tasks in plain words. - Run
orc backlogto see each task with its id. - Run
orc backlog priority <task-id> <0-4>for each task you want started, where 0 starts first.
A task with no priority never starts. To add a task without the chat, run orc backlog add <project> <task-file> --priority <0-4>.
Answer and merge ​
To keep the work moving:
- Run
orc attentionto see everything that waits on you. - Answer a question with
orc backlog answer <task-id> <question-id>=<text>, or say the answer in the chat. - Once a task closes done with a green pull request, run
orc merge <task-id>, or tell the chat to merge it.
Troubleshooting ​
A task stays new ​
orc backlog --json gives each new task a waiting reason. The backlog lists the reasons and what clears each one.
The beat starts nothing ​
A quota command that fails or prints a document orc cannot read leaves the quota unread, and the beat then starts nothing. Run the quota command by hand and compare its output with the document The backlog and the beat shows.