You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Agent Kanban is that workspace. Every agent gets an Ed25519 identity — a crypt
28
28
29
29
```
30
30
Human talks to an agent runtime (Claude Code, Codex, Gemini CLI)
31
-
→ Agent auto-registers as a leader via `ak` CLI
31
+
→ Leader agent uses `ak` with its own identity
32
32
→ Leader breaks the goal into tasks and assigns to workers
33
33
→ Daemon dispatches workers, each in its own worktree
34
34
→ Workers claim, implement, and open PRs
@@ -116,7 +116,15 @@ The `-g` flag installs globally so the skills are available across all your repo
116
116
117
117
### 4. Use your agent runtime
118
118
119
-
Open any agent runtime (Claude Code, Codex, Gemini CLI) in a repo. The first `ak` call auto-registers the runtime as a leader agent with its own Ed25519 identity. Use the installed skills to manage your AI team:
119
+
Open any agent runtime (Claude Code, Codex, Gemini CLI) in a repo.
120
+
121
+
A leader agent can create its own identity:
122
+
123
+
```bash
124
+
ak identity create --username alex --name "Alex Chen"
125
+
```
126
+
127
+
After that, `ak` reuses that leader identity across sessions for the same runtime. Then use the installed skills to manage your AI team:
120
128
121
129
-**`/ak-plan v1.0 <goals>`** — analyze the codebase, create a board with tasks and dependencies, assign to agents
122
130
-**`/ak-task fix the login redirect bug`** — create a single task, assign it, monitor → review → merge
@@ -127,7 +135,8 @@ The leader creates and assigns tasks; the daemon picks them up and dispatches wo
127
135
128
136
Every agent gets a unique cryptographic identity:
129
137
130
-
-**Ed25519 keypair** — generated per agent spawn
138
+
-**Leader identity** — created explicitly once per runtime, then reused across sessions
139
+
-**Ed25519 keypair** — generated per agent session
131
140
-**Fingerprint** — derived from the public key
132
141
-**Identicon** — visual representation of the fingerprint
133
142
-**JWT auth** — agents sign their own tokens, verified server-side
@@ -178,6 +187,10 @@ Task Lifecycle:
178
187
task cancel <id> Cancel a task
179
188
task release <id> Release back to todo
180
189
190
+
Identity:
191
+
identity create Create a leader identity for the current runtime
192
+
whoami Show the current runtime's agent identity
193
+
181
194
Output:
182
195
-o json|yaml|wide Output format (default: text table)
Copy file name to clipboardExpand all lines: docs/designs/agent-kanban-v1.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,15 +211,15 @@ The skill must explicitly document that agents can **create tasks** — not just
211
211
| Shared types | Proper workspace package with build step | Works with CF bundler + npm publish |
212
212
| Skill location |`packages/skill/` in pnpm workspace | Version-controlled with CLI, install script copies to `~/.claude/skills/`|
213
213
| Claim atomicity |`db.batch()` for atomic claim | Prevents race condition on concurrent /claim |
214
-
| Agent identity | API key = Machine (not Agent). Agents auto-register on claim. | One key per computer, zero per-agent config. Forward-compatible with v2 roles. |
214
+
| Agent identity | API key = Machine (not Agent). Leader identity is created explicitly, then reused by runtime. | One key per computer with stable per-runtime agent identity. |
215
215
216
216
### Identity & Auth Model (revised)
217
217
218
-
The original design had one API key per agent. Revised to Machine-level auth with auto-registered agent instances.
218
+
The original design had one API key per agent. Revised to Machine-level auth with an explicitly created leader identity per runtime.
219
219
220
220
**API key = Machine.** One key per computer. Configured once via `agent-kanban config set api-key`. All agents on that machine share the same key.
221
221
222
-
**Agent = auto-registered on first claim/create.**No pre-registration needed.
222
+
**Leader identity = created explicitly once per runtime.**After that, the CLI reuses the local identity cache and restores the unique server-side leader for that runtime if the local cache is missing.
id, machine_id → api_keys.id, name (auto-generated), role_id (null), created_at
206
+
agents
207
+
id, name, username, runtime, kind, created_at
208
208
209
209
tasks
210
210
assigned_to → agents.id (not api_key name)
211
211
created_by → agents.id or "human"
212
212
```
213
213
214
-
One API key per Machine. One Machine can have many concurrent agent instances. Agent instances are auto-created when they first claim or create a task — zero manual setup.
214
+
One API key per Machine. One Machine can have many concurrent agent instances. Leader identities are created explicitly once per runtime, then reused across sessions. If the local identity cache is missing, the CLI restores the unique server-side leader for that runtime.
0 commit comments