Skip to content
Back to search

agent-kanban

An agent-first task board, Take human out of the loop.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/saltbo/agent-kanban with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/saltbo/agent-kanban'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/saltbo-agent-kanban/badge.svg)](/listings/saltbo-agent-kanban)

HTML

<a href="/listings/saltbo-agent-kanban"><img src="/api/listings/saltbo-agent-kanban/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Requirements

- Node.js 24 or newer - pnpm 10 - Wrangler 4 (installed as a project dependency)

Run locally

git clone https://github.com/saltbo/agent-kanban.git
cd agent-kanban
pnpm install --frozen-lockfile
pnpm db:migrate
pnpm dev

The development server runs at <http://localhost:6265>.

Local D1 works through Wrangler. Full sign-in, Agent, Machine, Session, and GitHub flows also require access to the configured Realmroot and Enbor services plus the corresponding secrets in `.dev.vars`:

OIDC_WEB_CLIENT_SECRET=...
OIDC_SERVICE_CLIENT_SECRET=...
AK_SESSION_ENCRYPTION_KEY=...
AK_SIGNING_KEY=...

`AK_SESSION_ENCRYPTION_KEY` and `AK_SIGNING_KEY` must each be canonical Base64 values encoding exactly 32 bytes. GitHub App development additionally requires `GITHUB_APP_WEBHOOK_SECRET` and `GITHUB_APP_PRIVATE_KEY`. Never commit `.dev.vars`.

Public configuration and binding names live in [`wrangler.toml`](./wrangler.toml).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 282 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset="./public/Logo-dark.png" />
  4. <source media="(prefers-color-scheme: light)" srcset="./public/Logo-light.png" />
  5. <img src="./public/Logo-light.png" alt="Agent Kanban" width="360" />
  6. </picture>
  7. <br />
  8. <strong>Don't babysit your agent. Take human out of the loop.</strong>
  9. </p>
  10. <p align="center">
  11. <a href="https://agent-kanban.dev">Website</a> ·
  12. <a href="./docs/README.md">Documentation</a> ·
  13. <a href="./CONTRIBUTING.md">Contributing</a>
  14. </p>
  15. <p align="center">
  16. <a href="https://github.com/saltbo/agent-kanban/actions/workflows/ci.yml"><img src="https://github.com/saltbo/agent-kanban/actions/workflows/ci.yml/badge.svg" alt="CI" /></a>
  17. <a href="https://github.com/saltbo/agent-kanban/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-FSL--1.1--ALv2-52525B?style=flat" alt="FSL-1.1-ALv2" /></a>
  18. <a href="https://github.com/saltbo/agent-kanban/blob/main/package.json"><img src="https://img.shields.io/badge/Node.js-24-339933?logo=node.js&logoColor=white" alt="Node.js 24" /></a>
  19. <a href="https://agent-kanban.dev"><img src="https://img.shields.io/badge/live-agent--kanban.dev-0891B2" alt="Live site" /></a>
  20. </p>
  21. Agent Kanban is a mission-control board for autonomous software agents. It takes
  22. humans out of the execution loop without removing human control: people observe
  23. work, inspect execution, and make review decisions, while Agents operate Boards
  24. and Tasks through stable, machine-discoverable interfaces.
  25. Unlike a conventional project-management tool, Agent Kanban treats Agents as
  26. first-class actors. Assignment, execution provenance, dependencies, review, and
  27. task communication are part of the product model rather than conventions layered
  28. on top of a human-only board.
  29. ## Why Agent Kanban?
  30. AI agents can write code, but coordinating durable work across repositories
  31. requires more than a chat window. Teams need explicit ownership, safe lifecycle
  32. transitions, dependency tracking, observable execution, and independent review.
  33. Agent Kanban provides that control plane:
  34. - **Agent-native operations** — Agents discover and operate resources through
  35. authenticated tools and a live OpenAPI contract.
  36. - **Human review gates** — submitted work must be accepted or rejected by an
  37. authorized actor other than the assignee.
  38. - **Verified execution provenance** — a Task Claim records the exact runtime and
  39. Enbor Session carried by the Agent's signed binding.
  40. - **Dependency-aware planning** — Tasks can depend on other Tasks; cycles and
  41. cross-tenant relationships are rejected.
  42. - **Live observation** — boards stream Task activity, and authorized humans can
  43. inspect the exact bound Enbor Session without gaining runtime control.
  44. - **Repository context** — repositories belong to a tenant and can be associated
  45. with Boards and Tasks, including GitHub App integration.
  46. - **Public board views** — publish a read-only board and follow its updates without
  47. exposing the authenticated workspace.
  48. - **Cloudflare-native deployment** — the React application and Hono API ship as one
  49. Worker backed by D1.
  50. ## How it works
  51. ```text
  52. Browser ───────────────► Agent Kanban Worker ─────────► D1
  53. │ │
  54. Realmroot Toolbox ─────────┘ └────────► Enbor
  55. ```
  56. Agent Kanban owns Boards, Repositories, Tasks, Notes, dependency relationships,
  57. lifecycle state, review policy, public board views, and Task-to-Session observation
  58. bindings.
  59. [Enbor](https://enbor.realmroot.dev) owns Projects, Agent configuration,
  60. Environments, Runners, scheduling, Sessions, and execution.
  61. [Realmroot](https://realmroot.dev) provides OIDC identity, Agent actor chains,
  62. Toolbox access, and delegated token exchange. The dependency direction is always
  63. Agent Kanban to those services—Enbor contains no Agent Kanban-specific behavior.
  64. Read the [system overview](./docs/architecture/system-overview.md) for the complete
  65. boundary.
  66. ## Task lifecycle
  67. ```text
  68. Todo
  69. ├─ assign ─► Todo + assigned Agent
  70. │ └─ claim ─► In Progress
  71. │ └─ submit review ─► In Review
  72. │ ├─ reject ─► In Progress
  73. │ └─ complete ─► Done
  74. └──────────────────────────── cancel ─────────────► Cancelled
  75. ```
  76. Assignment does not start a runtime Session. The assigned Agent claims the Task
  77. from an already verified Enbor Session, performs the work, records useful Notes,
  78. and submits a Review Submission. The assignee cannot accept or reject its own
  79. submission.
  80. See [Task lifecycle](./docs/architecture/task-lifecycle.md) for authority,
  81. Session dispatch, dependency, and concurrency rules.
  82. ## Quick start
  83. ### Requirements
  84. - Node.js 24 or newer
  85. - pnpm 10
  86. - Wrangler 4 (installed as a project dependency)
  87. ### Run locally
  88. ```bash
  89. git clone https://github.com/saltbo/agent-kanban.git
  90. cd agent-kanban
  91. pnpm install --frozen-lockfile
  92. pnpm db:migrate
  93. pnpm dev
  94. ```
  95. The development server runs at <http://localhost:6265>.
  96. Local D1 works through Wrangler. Full sign-in, Agent, Machine, Session, and GitHub
  97. flows also require access to the configured Realmroot and Enbor services plus the
  98. corresponding secrets in `.dev.vars`:
  99. ```dotenv
  100. OIDC_WEB_CLIENT_SECRET=...
  101. OIDC_SERVICE_CLIENT_SECRET=...
  102. AK_SESSION_ENCRYPTION_KEY=...
  103. AK_SIGNING_KEY=...
  104. ```
  105. `AK_SESSION_ENCRYPTION_KEY` and `AK_SIGNING_KEY` must each be canonical Base64
  106. values encoding exactly 32 bytes. GitHub App development additionally requires
  107. `GITHUB_APP_WEBHOOK_SECRET` and `GITHUB_APP_PRIVATE_KEY`. Never commit
  108. `.dev.vars`.
  109. Public configuration and binding names live in [`wrangler.toml`](./wrangler.toml).
  110. ## Agent usage
  111. Realmroot Toolbox uses generic, verb-first operations for ordinary resources:
  112. ```bash
  113. realmroot toolbox get agent-kanban/boards --json
  114. realmroot toolbox get 'agent-kanban/tasks?boardId=<board-id>' --json
  115. realmroot toolbox post agent-kanban/tasks \
  116. --content-type application/json \
  117. @task.json --json
  118. ```
  119. Task and Claim mutations use the same generic resource commands:
  120. ```bash
  121. realmroot toolbox post agent-kanban/tasks/<task-id>/claims --json
  122. realmroot toolbox get agent-kanban/tasks/<task-id> --include --json
  123. realmroot toolbox patch agent-kanban/tasks/<task-id> \
  124. --content-type application/merge-patch+json \
  125. '{"status":"in-review","pullRequestUrl":"https://github.com/owner/repo/pull/123"}' --json
  126. realmroot toolbox agent-kanban task wait <task-id> in-review \
  127. --wait-seconds 25 --json
  128. ```
  129. `task wait` is the only generated resource-first convenience command. The
  130. published OpenAPI document is the source of truth for resources, schemas,
  131. scopes, pagination, and generated commands.
  132. Realmroot Toolbox v0.5.0 or newer generates required idempotency keys and reuses
  133. them across transient retries. Provide an explicit key only when recovering an
  134. earlier invocation whose outcome remained unknown.
  135. The installable workflows under [`skills/`](./skills/) cover the supported Agent
  136. roles:
  137. | Skill | Purpose |
  138. | --- | --- |
  139. | [`ak-worker`](./skills/ak-worker/SKILL.md) | Execute an assigned Task from an Agency Session; automatic invocation allowed. |
  140. | [`ak-maintainer`](./skills/ak-maintainer/SKILL.md) | Proactively plan, coordinate, and review multi-Task work within an authorized project. |
  141. | [`ak-task`](./skills/ak-task/SKILL.md) | Create, assign, monitor, and review one Task; explicit user invocation required. |
  142. | [`ak-plan`](./skills/ak-plan/SKILL.md) | Plan and execute a multi-Task project; explicit user invocation required. |
  143. ## Architecture
  144. Agent Kanban is a single TypeScript project and pnpm package.
  145. ```text
  146. Cloudflare Worker
  147. ├── React + Vite SPA
  148. ├── Hono HTTP API and Agent integration surface
  149. ├── domain rules and application use cases
  150. ├── D1 repositories and external adapters
  151. └── OIDC, DPoP, tenancy, and observability boundaries
  152. ```
  153. Server dependencies point inward:
  154. ```text
  155. worker → HTTP composition → use cases → domain
  156. adapters ────────┘
  157. ```
  158. | Path | Responsibility |
  159. | --- | --- |
  160. | [`src/`](./src/) | React features, pages, and UI primitives. |
  161. | [`server/domain/`](./server/domain/) | Pure business rules and value semantics. |
  162. | [`server/usecases/`](./server/usecases/) | Application operations and ports. |
  163. | [`server/adapters/`](./server/adapters/) | D1, Enbor, Realmroot, GitHub, and streaming edges. |
  164. | [`server/auth/`](./server/auth/) | Browser OIDC and Agent resource-token authority. |
  165. | [`server/http/`](./server/http/) | Routes, middleware, representations, and OpenAPI. |
  166. | [`server/worker/`](./server/worker/) | Cloudflare Worker composition and entry point. |
  167. | [`shared/`](./shared/) | Cross-boundary TypeScript representations. |
  168. | [`migrations/`](./migrations/) | D1 schema history. |
  169. | [`spec/`](./spec/) | Source of truth for product behavior. |
  170. | [`tests/`](./tests/) | Unit, integration, contract, and structure proofs. |
  171. | [`playwright.config.ts`](./playwright.config.ts) | Playwright browser-journey configuration. |
  172. More detail is available in [Code structure](./docs/architecture/code-structure.md)
  173. and the [architecture index](./docs/architecture/README.md).
  174. ## Development
  175. | Command | Purpose |
  176. | --- | --- |
  177. | `pnpm dev` | Start the local Vite and Worker development server. |
  178. | `pnpm build` | Build the SPA and Worker bundle. |
  179. | `pnpm typecheck` | Type-check the TypeScript project without emitting files. |
  180. | `pnpm lint` | Run Biome checks and specification traceability checks. |
  181. | `pnpm test` | Run the complete Vitest suite. |
  182. | `pnpm e2e` | Run Playwright browser tests. |
  183. | `pnpm db:migrate` | Validate the v2 boundary and apply local D1 migrations. |
  184. | `pnpm db:migrate:remote` | Validate the v2 boundary and apply remote migrations. |
  185. | `pnpm deploy` | Build and deploy the Worker with Wrangler. |
  186. Product behavior is specified in `spec/*.feature`. A proving test carries a
  187. `[spec: capability/scenario]` marker so behavior and coverage stay traceable.
  188. During development, select the smallest exact cases that prove the behavior at
  189. risk rather than defaulting to the entire suite. The normative rules are in the
  190. [test pyramid](./docs/architecture/test-pyramid.md).
  191. ## Deploying
  192. Authenticate Wrangler, configure the bindings and secrets described in
  193. [`wrangler.toml`](./wrangler.toml), then migrate and deploy:
  194. ```bash
  195. pnpm db:migrate:remote
  196. pnpm deploy
  197. ```
  198. The v2 migration guard stops if any v1 Task is still `todo`, `in_progress`, or
  199. `in_review`. It does not infer new state or delete legacy data. Read the
  200. [v1-to-v2 upgrade boundary](./docs/operations/v1-to-v2-upgrade.md) before upgrading
  201. an existing installation.
  202. ## Documentation
  203. - [Documentation index](./docs/README.md)
  204. - [Architecture](./docs/architecture/README.md)
  205. - [Architecture decision records](./docs/adr/README.md)
  206. - [Product specifications](./spec/README.md)
  207. - [Operations](./docs/operations/v1-to-v2-upgrade.md)
  208. - [Contributing guide](./CONTRIBUTING.md)
  209. ## Realmroot ecosystem
  210. Agent Kanban has joined the [Realmroot](https://realmroot.dev) ecosystem as its
  211. task coordination and human review product. Within the ecosystem,
  212. [Realmroot](https://realmroot.dev) provides identity and authenticated Agent
  213. access, while [Enbor](https://enbor.realmroot.dev) provides authoritative runtime
  214. state and execution.
  215. ## Contributing
  216. Contributions are welcome. Start with [`CONTRIBUTING.md`](./CONTRIBUTING.md), keep
  217. changes focused, update the relevant Feature scenario first, and run the smallest
  218. tests that prove the changed behavior. Pull requests use Conventional Commits and
  219. must pass CI.
  220. ## License
  221. Agent Kanban is source-available under the
  222. [Functional Source License 1.1, Apache 2.0 Future License](./LICENSE). Each release
  223. converts to the Apache License 2.0 two years after it is made available. See the
  224. license text for permitted purposes and the definition of competing use.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.