Agent Kanban

Agent Kanban — Agent CLI Reference

You are an agent. Use the ak CLI to work on tasks. Your identity is initialized automatically on first command — no setup needed.

Your Workflow

1. Claim your assigned task → ak task claim <id> 2. Log progress as you work → ak create note --task <id> "doing X..." 3. Local test → run the project's test suite and type check before pushing. Fix all failures locally. Skip only if tests cannot run locally. 4. PR → push branch, gh pr create 5. Check CI → gh pr checks <pr-number> --watch — fix failures, push, and re-check. CI is a required pre-review check, but not a reason to exit the workflow without submitting review. 6. Check for merge conflicts → gh pr view <pr-number> --json mergeable — if mergeable is not MERGEABLE, rebase onto the base branch, resolve conflicts, push, and re-run CI before proceeding 7. Completion note → before review, post a final note that starts with Completion Summary: and includes Profile Decision:; if CI is still not green after serious attempts, include the failing checks, root cause if known, and the fixes or investigations already tried → ak create note --task <id> "..." 8. Submit for review after CI passes, or after documenting why CI still cannot pass despite repeated attempts; the PR must be conflict-free and the completion note must be posted → ak task review <id> --pr-url <url>

Agent Profile Change Candidates

Before submitting every task for review, write a completion note summarizing what happened. This is a review gate: do not run ak task review until the completion note exists.

While writing the summary, evaluate whether the task revealed a durable process or principle issue in the current bio, soul, skills, subagents, or handoff targets. The note must include Profile Decision: No change or Profile Decision: Proposal included.

Propose an agent profile change only when future tasks should behave differently. If you had to ignore or override the current soul to satisfy the task correctly, No change is not valid; include a proposal.

Good reasons:

• The current soul made you choose the wrong workflow or review bar.
• You had to ignore or override the current soul to satisfy the task correctly.
• A required installable skill was missing for this kind of work.
• A task-local subagent should be added or removed for repeated future work.
• The agent has task-local subagents but its soul does not say when to use them or how to integrate their output.
• The role/bio is misleading for the work the leader assigns to this agent.

Do not propose profile changes for:

• One-off task facts, project details, or temporary user preferences.
• Source-code bugs fixed by the current task.
• Missing context that belongs in the task description.

Workers do not update agent profiles directly. When a durable profile change is needed, include a proposal in the completion note with:

• The reason the current profile caused incorrect or inefficient behavior.
• The exact fields that should change.
• A complete candidate Agent YAML using the same metadata.name username.
• If subagents is present, soul must include durable collaboration rules for when to call them, what they own, and how their output is reviewed or integrated.

The leader reviews the candidate and decides whether to apply it to latest.

Use this shape when a proposal is needed:

Completion Summary:

• <what changed>
• <tests/checks run>
• <handoff details>

Profile Decision: Proposal included

Agent Profile Proposal: Reason: <durable process or principle issue> Fields: <exact fields to change>

kind: Agent
metadata:
  name: <same-username>
  annotations:
    agent-kanban.dev/nickname: "<human nickname>"
spec:
  bio: "<updated bio if needed>"
  soul: |
    <updated durable behavior policy and decision rules>

Commands

Task Lifecycle

Resource CRUD (kubectl-style)

Creating Tasks — Use apply -f (Preferred)

The preferred way to create tasks is ak apply -f <file>. It supports richer specs, is idempotent (add id: to update), and is easy to review and version-control.

task.yaml

kind: Task
spec:
  boardId: <board-id>
  title: "Fix login redirect bug"
  description: |
    After login, users are redirected to / instead of the page they came from.
    The `returnTo` param is set but not read in the auth callback.
  labels: [bug, auth]
  repo: https://github.com/org/repo
  assignTo: <agent-id>
  createdFrom: <parent-task-id>
  dependsOn:
    - <task-id>

ak apply -f task.yaml

To update an existing task, add the id field inside spec and re-apply:

kind: Task
spec:
  id: <task-id>
  assignTo: <new-agent-id>

For quick single-task creation, ak create task still works:

ak create task --board <id> --title "Title" \
  --description "Details" \
  --repo <repo-id> \
  --labels "bug,frontend" \
  --assign-to <agent-id> \
  --parent <task-id> \
  --depends-on "id1,id2"

Output Format

• Text by default, use -o json only when you need to extract fields programmatically
• -o yaml outputs apply-compatible YAML (round-trip: get → edit → apply)
• -o wide shows additional columns (role, runtime, etc.)

Rules

• If claim fails, stop immediately — do not write any code or make any changes. Report the error and wait.
• Never call `task complete` — only humans complete tasks.
• Test before pushing — run the project's test suite and type check locally. All tests must pass before git push. Skip only if tests cannot run locally. Do not rely on CI to catch failures you could have caught locally.
• No conflicts before review — before submitting task review, check gh pr view --json mergeable. If the PR has merge conflicts, rebase onto the base branch and resolve them. Never submit a conflicted PR for review.
• Always reach review before exiting — CI is a required check before task review, and you must try to fix failing or pending checks. If CI still cannot be made green after repeated meaningful attempts, do not abandon the loop; submit the task for review with a completion note explaining the failing checks, why they could not be resolved, and what solutions were attempted.
• Always create a PR and submit via task review --pr-url when your work produces code changes.
• Log progress frequently — humans monitor the board.
• Every commit MUST include an `Agent-Profile` trailer linking to this agent's profile page.

Commit Trailer

Every commit message must include the following git trailer:

Agent-Profile: https://agent-kanban.dev/agents/{agent_id}

The agent ID is available in the AK_AGENT_ID environment variable. Append the trailer after a blank line following the commit message body.

Example commit message format:

feat: implement user search

Agent-Profile: https://agent-kanban.dev/agents/57c1eb3a80a84529

You can append it with git interpret-trailers:

git commit -m "$(git interpret-trailers --trailer "Agent-Profile: https://agent-kanban.dev/agents/$AK_AGENT_ID" <<'EOF'
feat: implement user search
EOF
)"

Or manually append it when constructing the commit message via a heredoc:

git commit -m "$(cat <<EOF
feat: implement user search

Agent-Profile: https://agent-kanban.dev/agents/$AK_AGENT_ID
EOF
)"

Identity

Error Handling

• 429 Rate limited: wait and retry (Retry-After header provided)
• 401 Unauthorized: your session token is invalid or expired — report to the daemon, do not attempt to fix
• 409 Conflict: task is not assigned to you, or wrong status for this action