agentpack-cli 0.1.6 → 0.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/docs/ROADMAP.md CHANGED
@@ -2,9 +2,11 @@
2
2
 
3
3
  ## North Star
4
4
 
5
- Agentpack is a local task-state layer for AI coding agents. It captures useful working context that usually gets lost in long sessions, restarts, and compaction: decisions, dead ends, inspected sources, evidence, checkpoints, and budgeted resumes.
5
+ Agentpack makes agent continuity native to the repo.
6
6
 
7
- Agentpack is not an orchestrator or a broad automatic memory engine. It is the portable context ledger for humans, single agents, and agent teams working on a repo.
7
+ It is a neutral task passport for agentic workspaces: a compact, portable record of decisions, source conclusions, evidence, dead ends, checkpoints, and next actions that survives chat compaction, client switches, worktree handoffs, machines, branches, and orchestrators.
8
+
9
+ See [VISION.md](VISION.md) for the fuller strategic framing.
8
10
 
9
11
  ## Product Principles
10
12
 
package/docs/VISION.md ADDED
@@ -0,0 +1,43 @@
1
+ # Vision
2
+
3
+ ## Strategic North Star
4
+
5
+ Agentpack makes agent continuity native to the repo.
6
+
7
+ It is a neutral task passport for agentic workspaces: a compact, portable record of decisions, source conclusions, evidence, dead ends, checkpoints, and next actions that survives chat compaction, client switches, worktree handoffs, machines, branches, and orchestrators.
8
+
9
+ ## Product Bet
10
+
11
+ As agent UIs evolve from chat boxes into execution workspaces, handoffs will become common: chat to worktree, IDE to background agent, local repo to cloud sandbox, Claude to Codex, Cursor to CI.
12
+
13
+ Branches and transcripts are not enough. Agents need reviewed task state that is portable, inspectable, and client-neutral.
14
+
15
+ Agentpack is not trying to replace execution engines. Codex, Claude Code, Cursor, LangGraph, Temporal, OpenAI Agents SDK, and similar systems can own execution loops, retries, approvals, tool calls, and durable runs. Agentpack should own the neutral repo-scoped continuity layer that those surfaces can share.
16
+
17
+ ## What Agentpack Should Own
18
+
19
+ - repo-native continuity
20
+ - semantic checkpoints
21
+ - source-inspection cache
22
+ - dead-end memory
23
+ - evidence-linked handoffs
24
+ - MCP-first access
25
+ - portable bundles between worktrees, machines, and clients
26
+ - orchestrator recipes later
27
+
28
+ ## Operating Principles
29
+
30
+ - Git stores code state. Agentpack stores reviewed task state.
31
+ - Execution engines run the work. Agentpack preserves what future agents need to continue it.
32
+ - Continuity should be native to the repo, not reconstructed from chat history.
33
+ - Prefer small, inspectable, local files before hosted sync or hidden databases.
34
+ - Prefer portable MCP, CLI, and file surfaces over framework lock-in.
35
+ - Record durable context, not every action.
36
+
37
+ ## Non-Goals
38
+
39
+ - Do not become a general chat archive.
40
+ - Do not replace LangGraph, Temporal, OpenAI Agents SDK, Codex, Claude Code, Cursor, or other execution engines.
41
+ - Do not make cloud sync or hosted memory required for the core workflow.
42
+ - Do not treat automatic full-session capture as the default source of truth.
43
+ - Do not require embeddings or network calls before deterministic file/hash/source summaries stop being enough.