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: docs/CLI.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ agentpack task close
49
49
50
50
Write scopes are repo-relative paths. `.` means the repository root.
51
51
52
-
`task passport` prints the current `passport.json`. `task switch <id>` points the worktree at another open passport. `task update` patches objective, constraints, write scope, next actions, tags, and risk without changing lifecycle status; list fields are appended and deduplicated. Empty or no-op updates fail, and unknown risk values are rejected. `task audit` checks the current passport for stale source conclusions, branch/head drift, missing next actions, open verification, and closed-task anomalies. `task update-verification` writes verification status, evidence IDs, and summary into the passport; without flags it marks verification as `pending`, and with `--status`, `--evidence`, and `--summary` it can close the audit warning with evidence-backed verification. When a current passport exists, `resume` and MCP `load_context` include it above the repo-level ledger so agents can see the active task before broader history.
52
+
`task start` refuses to replace an active, blocked, or verifying current task; park or close the current task first when starting unrelated work. Invalid risk values are rejected instead of being treated as unknown. `task passport` prints the current `passport.json`. `task switch <id>` points the worktree at another open passport. `task update` patches objective, constraints, write scope, next actions, tags, and risk without changing lifecycle status; list fields are appended and deduplicated. Empty or no-op updates fail, and unknown risk values are rejected. `task audit` checks the current passport for stale source conclusions, branch/head drift, missing next actions, open verification, and closed-task anomalies. `task update-verification` writes verification status, evidence IDs, and summary into the passport; without flags it marks verification as `pending`, and with `--status`, `--evidence`, and `--summary` it can close the audit warning with evidence-backed verification. When a current passport exists, `resume` and MCP `load_context` include it above the repo-level ledger so agents can see the active task before broader history.
Copy file name to clipboardExpand all lines: docs/DOGFOOD.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,6 @@ Load a small context first:
8
8
9
9
```text
10
10
load_context(preset: "quick")
11
-
source_status()
12
11
```
13
12
14
13
Use `agent` instead of `quick` when the task needs more history.
@@ -40,9 +39,11 @@ Record only durable context. Agentpack is not an activity logger, and it should
40
39
41
40
Default cadence:
42
41
43
-
- At task start, load Agentpack context and source status.
42
+
- At task start, load Agentpack context.
43
+
- Call source status only when you need a full stale-source check beyond the loaded context.
44
44
- During normal coding, keep working locally; record only durable decisions, dead ends, source conclusions, and evidence.
45
-
- At the end of a coherent step, record the useful sources/evidence, update status and next actions, then checkpoint.
45
+
- Sequence state-changing Agentpack calls; do not run them in parallel with audit, status, or checkpoint calls.
46
+
- At the end of a coherent step, record aggregated evidence, update status and next actions, then checkpoint.
46
47
- Use full safe mode for risky or release-like changes: record important findings as they happen and run the full verification loop.
47
48
48
49
This keeps Agentpack useful without turning every micro-step into ledger traffic. The intended default cost is one context load near the start and one durable save near the end.
@@ -84,8 +85,10 @@ Git still owns code history. Agentpack owns task memory.
84
85
85
86
While dogfooding, look for friction:
86
87
87
-
- Did the agent call `load_context`and `source_status`early enough?
88
+
- Did the agent call `load_context` early enough without repeating status checks unnecessarily?
88
89
- Were unchanged sources avoided when recorded conclusions were enough?
90
+
- Did `record_source` capture only reusable source conclusions instead of one event per changed file?
91
+
- Were state-changing Agentpack calls sequenced so audits read the latest state?
89
92
- Were decisions and dead ends recorded at useful moments?
Generated Codex, Claude Code, and Cursor instructions tell connected agents to use the MCP tools as a small hybrid continuity loop:
12
12
13
13
1. Start by calling `load_context` with a focused query and compact preset.
14
-
2. Call `source_status`before relying on previously recorded source conclusions.
14
+
2. Call `source_status`only when you need a full stale-source check beyond the context you just loaded.
15
15
3. Record durable decisions, dead ends, evidence, and reviewed source conclusions while working.
16
16
4. Call `checkpoint` after meaningful progress so the next session inherits status, next actions, git state, and compact resume context.
17
17
18
+
For small tasks, prefer one aggregated evidence item plus one checkpoint summary. Do not call `source_status` repeatedly when `load_context`, `task_audit`, or a recent status check already answered the question. Do not call `record_source` for every changed file just to clear an audit warning; refresh a source record only when its durable conclusion changed.
19
+
18
20
The CLI exposes the same operations for setup, inspection, debugging, demos, and web-chat fallback. See [CLI.md](CLI.md) for manual command examples.
- Add Task Passport update flow for objective, constraints, write scope, next actions, tags, and risk.
8
+
- Expose `task_update` through MCP alongside `task_audit` and `task_update_verification`.
9
+
- Preserve `.` as a repo-root write scope.
10
+
- Protect the current-passport workflow: `task start` now refuses to replace active, blocked, or verifying work.
11
+
- Reject invalid task risk values consistently in `task start`, `task update`, and MCP `task_update`.
12
+
- Clarify generated Codex, Claude, and Cursor instructions so agents use compact ledger cadence instead of repeated status checks or per-file source-record spam.
13
+
- Add collaboration modes and safety guidance to generated project instructions.
14
+
- Align CLI, MCP, Dogfood, and Task Passport docs with the implemented behavior.
15
+
16
+
Verification before release:
17
+
18
+
-`npm test`
19
+
-`npm run mcp:smoke`
20
+
-`npm pack --dry-run`
21
+
- privacy scan for local paths and secret-like values
22
+
-`git diff --check`
23
+
-`agentpack doctor`
24
+
-`agentpack task audit`
25
+
26
+
Release gate:
27
+
28
+
- Complete final review of the accumulated local commits.
29
+
- Push only after review is accepted.
30
+
- Cut the npm release only after the pushed branch is stable and docs match the release scope.
Copy file name to clipboardExpand all lines: docs/TASK-PASSPORT.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,6 +184,8 @@ agentpack task close
184
184
185
185
`resume` and MCP `load_context` read the current passport automatically when one exists, then show the broader repo-level ledger below it.
186
186
187
+
`task start` creates a new current passport only when there is no current task, the current task is closed, or the current task is parked. If the current task is active, blocked, or verifying, Agentpack asks you to park or close it first so unrelated work does not silently overwrite the handoff pointer. Invalid risk values are rejected instead of being treated as unknown.
188
+
187
189
`task audit` is a diagnostic pass for continuity risk. It checks the current passport for branch/head drift, missing next actions, open verification, stale source conclusions, and closed-current-task anomalies.
188
190
189
191
`task update` patches the current passport without changing lifecycle status. It can add objective, constraints, write scope, next actions, tags, and risk after the task has already started. List fields append and deduplicate; omitted fields are preserved. Empty or no-op updates fail, and unknown risk values are rejected.
Copy file name to clipboardExpand all lines: src/integrations/install.ts
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ ${collaborationModesSection()}
30
30
31
31
At the start of a task:
32
32
- call \`load_context\` with a small preset first
33
-
- call \`source_status\` before re-reading previously inspected files
33
+
- call \`source_status\` only when you need a full stale-source check beyond the context you just loaded
34
34
35
35
During work:
36
36
- call \`record_source\` only when you have a durable conclusion about an important file; avoid repeated records for the same file unless the conclusion changed
@@ -40,11 +40,14 @@ During work:
40
40
41
41
Avoid turning Agentpack into an activity log:
42
42
- do not record every file read, mode switch, minor diff check, or routine command
43
-
- for small tasks, prefer one final source record per touched important file plus one verification evidence and one checkpoint
43
+
- do not call \`source_status\` repeatedly when \`load_context\`, \`task_audit\`, or a recent status check already answered the question
44
+
- do not call \`record_source\` for every changed file just to make an audit warning disappear; prefer a checkpoint summary for batch changes and refresh source records only when the durable conclusion changed
45
+
- for small tasks, prefer one aggregated verification evidence and one checkpoint; add source records only for important implementation files with reusable conclusions
44
46
45
47
Default cadence:
46
48
- start with Agentpack context
47
49
- work locally without recording every micro-step
50
+
- sequence state-changing Agentpack calls; do not run them in parallel with audit/status/checkpoint calls
48
51
- record durable findings and evidence before a checkpoint
49
52
- use full safe mode for risky or release-like changes
0 commit comments