The Tasks board

The Tasks board is a Kanban board your agents work. You lay out cards in lanes, hand a card or a whole lane to an engine, and watch the work move across the board. Each run gets its own git branch and lands in review, so a board full of agents does not become a merge accident.

Cards carry what a person would need to start: a prompt, and images you pasted or dropped in, which are handed to the agent as visual context and encrypted end to end just like the prompt text.

The lanes

Lane headers show a progress mark in the lane's status colour, empty, quarter, half, or full, followed by the task count. Each lane has an add control and an overflow menu that can add a card, move every card elsewhere, sort by newest, oldest, or alphabetically, or delete every card with a confirmation. Sorting is a view, not a rewrite: it does not mutate the persisted card order.

Context is prepared for you

There is no "prepare context" button, no "run anyway", and no readiness dialog to dismiss. Before a card runs, Pathrule assembles the context that card needs, and the run starts with it in place.

The reason this is autonomous rather than a step you confirm is that a confirmation on a background board is just a queue of stale dialogs. Preparation is claimed atomically, so two runs cannot prepare the same card twice, and the result is a receipt you can read after the fact rather than a prompt you had to answer before.

The Agent Command Center

Autonomous work is only acceptable if it is legible. The Command Center shows the live stages of a run and then a factual receipt of what it used:

• Which Pathrule memories, rules, and skills went in.
• Which files were touched.
• Tokens and cost.

It reports; it does not add another set of buttons to press.

The learning loop

When a run succeeds, it is reviewed deterministically, exactly once per conversation. The review costs no extra model call.

What it produces is proposals: a memory worth keeping, a rule that should have existed, a skill that would have shortened the run. Lasting knowledge changes stay proposal-first, so the board can learn without quietly rewriting your team's context while nobody is looking.

AI activity levels

AI activity has three levels:

• Low stays deterministic.
• Medium is the default and the balanced setting.
• High does more per run.

Medium and High are both bounded by the same rolling-token policy and by the workspace maximum, so a member cannot raise their own level past the ceiling an admin set, and no level escapes the hard usage limits on the plan. The level is set from the Tasks settings menu.

What to read next

• Pathrule Studio for the surfaces around the board.
• Writing memories for what the learning loop is proposing.
• Pathrule for iOS for following a run from your phone.