User GuidePluginsAPI Reference

Built-in agents

What the Lead, the Steward and the Sentinel do for a project, when they wake, what they can't do, and what they don't do yet.

taiku comes with three agents you can add to a project. Open Dashboard → Agents, pick the project under Built-in roles, and choose Add beside one. The sheet that opens has a How it works row with the same words as this page, and shows what the agent is allowed to do before you agree.

Each section ends with Not yet: what the agent can't do today. A line leaves this page when the gap is fixed.

Lead

What it does

Turns what you ask for into pieces of work: what each one is, who should do it, and what comes first.

When it wakes

When an agent writes to it or you answer its question.

What it can and can't do

It can plan, keep a list of the work with who does each piece, ask you one question at a time, and write to your other agents. It can't write code or touch the repository.

What you'll see

You'll see its questions and its plan in your conversation.

Not yet

  • It can hand work to another agent only by message.
  • It doesn't notice on its own when an agent stops moving.

Steward

What it does

Keeps your pull requests moving and tells you what each one waits on.

When it wakes

When a pull request opens or changes, when CI on your default branch finishes or a check fails, when another agent writes to it, and every two hours.

What it can and can't do

It can read pull requests, checks and statuses, and sort each one as ready, waiting on CI, failing, waiting on review or stale. It can't merge, approve, push, change settings or deploy.

What you'll see

You'll see its sorting in the CI and Waiting for review panels, and its reply in your conversation, with anything urgent first.

Not yet

  • It can't read Actions runs or the merge queue.
  • It can't add a pull request to the merge queue.
  • Its reports to the Lead aren't sent.

Sentinel

What it does

Reviews each pull request for security at its latest commit and records ok, ok with notes, or block.

When it wakes

When a pull request opens or changes.

What it can and can't do

It reads the pull request and the changed files on a box of its own, and never reviews a pull request it could have opened. It can't merge, push or approve on GitHub.

What you'll see

You'll see its verdict on the pull request's row in Reviews, and as a comment on the pull request once you let it post there.

Not yet

  • Nothing stops a merge on its verdict.
  • It's the only reviewer. Design and code reviewers are planned.
  • It doesn't post a status check to GitHub.

On this page