In List, choose Prioritise to edit value and effort, see their calculated score, and move tasks in board-wide manual order. The URL records selected clients, status, other filters, layout and sort. Reloading or updating the web app keeps those choices; Back and Forward restore earlier choices. Copy the URL to share the same filtered view. Links include filter names, so avoid putting private information in search fields when sharing them. Tokens and setup codes are never copied into navigation links.
Agents can use list --sort score, list --sort priority, and
priority-move '#12' --before '#8' (or --after, --top, --bottom) with kit v50.
Ranking is board-wide even when a list is filtered; status and Kanban ranks are unchanged.
If you selected Tasks when you made your board, you also have these views. They are under Tasks in the view bar (the people views are under People):
@your-github-username), newest first, with the task, its description and the comment. Your own comments are not shown. New means posted since you last opened that task. Click a row to open the task at that comment. Today shows an @Mentions tile when you have mentions. The filters apply here too.Open a task to edit its properties. Status and priority share a compact row, as do its due date and Waiting for. People, labels and the combined Client & project control use the full width. The client/project picker filters projects after you choose a client and keeps long names readable on a phone.
Views and utility screens can be bookmarked: the address keeps the selected view or settings section. Help, Settings, Search and Copy offer Copy link to this screen; settings sections also offer their own links. Shared screen links include the board, branch and file path, never your GitHub token. They do not grant repository access.
A card is a note to someone who was not there. A good card has a title that says the outcome in plain words, details that say what, why and what “done” means, steps you can tick, and a link for every pull request, document, file or web page it talks about. Writing “see #481” in the text is not enough: add the page to the card’s links so people can click it and search finds it; a linked pull request also shows in the Pull requests panel. Write a good card has the five tests, a bad card and the same card written well. Agents follow the same guide.
Open a person and type in ☑ Tasks. The task is linked to that person and their company, and it shows on Today when it is due.
AI agents can claim a task, report progress and finish it. While an agent works on a task, the card shows its status. See AI assistants.
When a task is parked on a person or an event (a client’s approval, a colleague’s pricing, DNS), use Waiting for
instead of using a label or a due date. Open the task and use Waiting for in its details: say what or whom it waits on
and, if you like, the day to chase. The card stays in its column and keeps its due date. It shows a
waiting on …, Nd chip, which turns amber once the chase day has passed. With no chase day, the task is due for a
chase after 7 days (a board can change this with settings-set --waiting-days N; 0 turns it off). The Waiting
filter shows only waiting tasks. Clear ends the wait, and marking the task done ends it too; the history keeps it.
A waiting task can’t be sent to Claude: Assign to Claude and @claude are off until the wait is cleared, and an
agent’s claim is refused. Agents that need a decision mark the card waiting, comment with @you and the question,
assign it to you and stop. An agent never clears a wait it did not set, or one on someone else; you do.
Agents and scripts use wait ID --on "Acme finance" [--who p_id|login] [--nudge +3|YYYY-MM-DD] [--note ..] and
unwait ID --note "why". today lists waits due for a chase under CHASE NOW, list --waiting (or
--waiting-on me) lists waiting tasks, and people shows how many tasks wait on each person.
A task can run after other tasks: #63 after #62, say. Set it with task-set '#63' --after '#62' (repeat
--after for more; --not-after '#62' removes one, --no-after clears them), or add "Title" --after '#62'. Each id
must be a task on the board; a task can’t run after itself, and a loop is refused. The card shows an after #62 chip
for each task not done yet (amber when that task is missing or cancelled), and the task’s details list every link and
its state. show prints them, and list adds [after #62].
The links are a hint and a gate, never a trigger. Nothing moves a task into To do because the tasks before it are done: you do that, and moving a chain into To do is approving it. Relay (if you use it) starts a task only once every task it runs after is done, and tells you when a Backlog task is ready to approve or a chain has stopped. A task that is no longer on the board counts as done only if the archive holds it as Done; otherwise it shows as missing.
Type a label on a task to create it. To rename, recolour or delete labels, or add one with a colour, open Settings → Board → Labels. Renaming or deleting a label updates every task that uses it, and Undo reverts the whole change. The agent tool does the same with label-set and label-rm.
Open Settings → Board → Columns. You can rename a column, move it up or down, add a new one, or remove one. Each change is saved at once and Undo reverses it.
A column’s name can change, but its hidden id stays, so cards, the Done column and AI agents keep working. To remove a column that still has cards, Keeptrack asks where to move them. To do, In progress and Done cannot be removed, because agents use them, and a board always keeps at least one column. Agents and scripts have matching commands (columns, column-add, column-set, column-move, column-rm).
Open Settings → Board → Sections and switch Tasks or People & pipeline (CRM) on or off. Keep at least one section on.
Turning a section off only hides its dedicated views. Today remains available and combines whichever sections are enabled. Nothing deletes tasks, people or history, and turning a section on again shows the same records. If you turn CRM on before there are any people, it opens as an empty CRM. The first person you add creates their record automatically.