The work card
Every piece of work the Conductor runs has a card or a row. Shut, it says where the work stands, where its time went and what each of its terminals is doing, and carries any question waiting for you. Open, it stays short, with the full history one click away.
Where the cards are
The works take the wide side of the Conductor, and the chat is a panel on the right. While a file is open, the reader takes the works’ place, and ← Work brings them back as they were. The works scroll by themselves.
On a phone the works are the Work tab, beside Chat. The tab shows how many works need you. The status line’s N pieces of work opens it, and so does tapping a work chip in the chat.
The works come in four groups:
| Group | What is in it |
|---|---|
| Needs you · N | Works waiting on you, as cards with their question: one asked a question, another holds a green PR handed over for you to merge. |
| In progress · N | Every other work that is building something, one row each. |
| Watching · N | Terminals you asked the Conductor to watch, one row each. |
| Finished | Works that ended, collapsed until you click it, one line each: title and repository, how it ended, how long it ran, and when. |
A row puts the title, the stage line, the terminals and the age side by side. When the works column is narrower than about 830px, its terminals drop under its title. On a phone every work in progress is a card. With nothing in progress the list says Nothing in progress.
The works sidebar
A sidebar beside the works lists every work, one entry each, whether a work is picked or not. It stays in place and scrolls by itself. A phone has no sidebar.
| Part | What it shows |
|---|---|
| Top row | All work names where you are. With a work picked it is ← All work, which goes back. The row keeps one height, so the entries never move. |
| Needs you · N | Pinned at the top, each work with the violet chip saying how long it has waited. |
| Groups | In progress, Watching and Finished, each counting its works. Finished folds with the list’s own Finished. |
| An entry’s first line | The repository’s monogram, the title, and how long the work has stood where it is. |
| An entry’s second line | The dock status mark of each terminal (three, then +N), the dock’s PR mark, and where the work stands. |
Drag the sidebar’s edge to make it wider or narrower, as you do the Dock’s. Double-click the edge to reset it. kolu remembers the width on this device.
In a window under 1280px wide the sidebar is a strip of initials. A work that needs you wears a violet ring, and hovering shows its title, where it stands and for how long.
A work’s face
| Line | What it says |
|---|---|
| Title and age | What the work is, and how long it has run. |
| repo · branch · host · mode | Where it is: the repository’s monogram, the branch in the dock’s colour, then the PR as a link (PR #n, draft PR #n) and, while live, the dock’s PR mark. In progress, you 12m is its total wait on you. |
| Where it stands | Who it waits on and why, coloured by them, and for how long. Under Needs you it leads with what is wanted, as in Needs you · Merge PR #700 · green for 12m. |
| Stage strip | Its six stages, below. |
| Terminals | One row each: its dock status mark, its role, its name (click it to go to the tile), what it runs, how it stands and for how long, Look (a live window), and Take over or Hand back. |
| The question waiting for you | Its form, to answer without picking the work. The same decision the chat and the reader show: answering it in any of them answers it. |
A PR recorded before kolu kept PR addresses shows its number as plain text. A work still in progress gets the link the next time kolu reads its PR.
The stage strip
The strip is one thin line of six segments, always in this order: Plan, Approve, Build, Review, Checks, Merge.
Every segment is named under its bar. A stage the work has been in also prints its own time there, in one unit (Plan 4m, Checks 1h). The stage in hand’s time keeps growing. A stage not reached yet has its label and no time.
What the marks mean:
- The colour is whose time the stage mostly was: violet you, amber CI, teal the agents. A Build that has been the agents’ for two hours stays teal while it waits on you.
- A ring marks the stage the work is in. On a finished work, the last stage’s label is emphasised instead.
- A dashed segment is a stage that did not happen. A faint one has not been reached.
Which stages a work has comes from its mode:
| Mode | Its stages |
|---|---|
| Full | All six. |
| Trivial | Build, Checks and Merge. Nobody plans, approves or reviews, so those segments read as not happening. |
| Watch | None, and no strip. |
- In a full work, answering the setup form counts as Plan time. A trivial work has no Plan, so its setup is in no stage; that time still counts as you in the time line.
- The build ends when the implementor’s PR is ready for review: at once if it opened ready, or when a draft is marked ready. A PR turned back into a draft returns the work to Build. A PR already open when the implementor joined does not end it by being open.
- CI’s time is Checks, except on a draft, where it is still Build. A green PR handed to you is always Merge.
A work whose mode is not chosen yet shows six quiet segments.
On a card, the strip is the index into the timeline. Clicking a segment that has happened opens the card on that stage’s events.
What every card offers
Under a card’s stage strip, and at the top of an open row, a card offers Open PR #N ↗ while a green PR waits for you to merge it. It opens the pull request on its forge. There is no merge button: you merge on the forge, or tell the Conductor to.
Picking a work points the chat at it. A work chip in the conversation also offers About this work, because it is named there rather than picked from a card.
Reach a work from anywhere
Every work has an address, #/work/…. Opening it enters the Conductor, picks that work and scrolls to it, or to one question of it. A link to a work kolu no longer holds says so. Link to any view lists the address forms.
The command palette lists what needs you first: a Needs you row says what is wanted and then names its work, and a Works row gives the title and where the work stands. Both keep their own headers while you search. The ◆ mark on a dock row is a link to that terminal’s work.
The picked work
Click a work, a card or a row, or its entry in the sidebar, and it is picked: it fills the works’ side. The chat narrows to the picked work. Click ← All work, or the work’s head again, to go back.
A work that needs you and a finished work can be picked too. On a phone it is a page of its own with ← All work above it. A reload stays on it.
A switch in the head of a picked work in progress has three views. It opens on Terminals while a terminal of the work is up, and on Details otherwise. Code is in front only when you choose it. A finished work shows only its details.
- Terminals: each terminal of the work live, in a pane with the Look window’s head and Inspect, which opens Details on that terminal. One or two stack; three or more, or a window under 1280px wide, show one pane with a tab each. Fit width (one choice for every pane) opens a wider terminal fitted, and is offered only while it is wider.
- Code: the work’s own folder in the Code tab’s view, read on the work’s machine: the tree, the Local and Branch changes, and the files. It stays after the work’s terminals have ended. When there is room, the tree stands beside the file, at a width you drag and this device keeps. Which of All files, Local and Branch you were on, and the file open in each, are kept for the work, across a reload and in another browser.
- Details: the terminals’ rows and the parts below. Clicking a stage on the strip shows Details.
Code shows less in two cases:
| Case | What you see |
|---|---|
| kolu has not read the work’s folder yet | One line saying so, the same as the Worktree part. |
| No terminal of the work stands in its folder | The tree, the changes and the files still show. Comments are off, and a picture or a download says in one line why it cannot be fetched. |
What Details hold
Click a terminal’s role to unfold its row. A terminal that is up shows the Right panel’s own parts for it: the agent card, Compose to send it text, and the program in front. Compose writes to that terminal on its own machine, through the same lock as your keys.
Below the rows:
| Part | What you get |
|---|---|
| Worktree | Once for a work in progress: its branch and repository, the PR and checks, odu’s CI, and the folder, as the Right panel shows them. It stays after the terminals end. |
| Files | The worktree’s .waterfall/ files, at any depth, and the copies kolu kept. A folder is one chip with its file count, such as mockup/ · 49. Click it to unfold it. Click a file to open it in the reader. |
| Pull request | Its number as a link: open, merged or closed, and draft while it is one. The last check result, failed ones in one line (7 failing: ci::nix, ci::unit, +5) to click. While open, whether GitHub would merge it. |
| Setup | One line: the mode, each role’s harness and model, and what happens on green. |
| Decisions | The latest three, one line each. all N shows the rest. Click a row for the question. |
| Timeline | The events of one stage, with their time and duration. |
The timeline shows the stage the work is in, or the one you clicked on the strip, and a finished work’s last stage. whole timeline · N events unfolds all of it in place. A watch, which has no stages, shows its latest five events.
A line runs through the event dots. The space between two events grows with the wait between them, up to about four rows, so a long wait is visibly a long stretch of line. A wait near that maximum prints its time on the line, such as 3h.
A question reads Asked: and your answer You:. A run of files one agent wrote into a folder is one row, such as Wrote mockup/ · 49 files. A line too long for the row is cut, and a folder’s row lists its files, with more beside it.
What a timeline keeps
A timeline is kept short in four ways:
- A work keeps its latest 30 agent state changes; older ones fold into one N earlier agent state changes line.
- While a PR’s checks run, only GitHub’s latest answer about merging it is kept.
- One commit keeps at most 8 check results and 8 merge answers. Past that, an old one in the middle is dropped, never the first or the newest.
- kolu lists the first 200 files and folders in
.waterfall/, and draws a run of files written into one folder as one row.
Nothing else is dropped, and kolu keeps the last 20 finished works with their files.
How a work ends
A work ends three ways: the forge merges or closes its pull request, you click Stop on the card and confirm, or the Conductor stops it. Declining the setup of a work nothing has happened in removes it.
An ended card’s line says how it ended, such as Merged #181 · 1d ago. Open, it shows where the time went, the kept files, the decisions and the timeline, where the merge and the end it caused are one row. It never shows terminals, a lock or a question, and it offers Reopen.
kolu copies the work’s .waterfall/ files when it ends, up to 50 MiB per work. Under Files (kept), a line starting Not kept: names what was left out and why: a file past that size, a listing that stopped at 200 files and folders, or a copy that failed.