swarmvault task

Record a local, git-friendly task ledger for agent work. Tasks are not transcripts; they are compact durable artifacts that capture the goal, linked context packs, decisions, graph evidence, touched paths, outcome, and follow-ups.

Usage

swarmvault task start <goal> --target <path-or-node> [--budget <tokens>] [--agent <name>]
swarmvault task update <id> [--note <text>] [--decision <text>] [--changed-path <path>] [--context-pack <id>] [--status active|blocked|completed|archived]
swarmvault task finish <id> --outcome <text> [--follow-up <text>]
swarmvault task list
swarmvault task show <id>
swarmvault task resume <id> [--format markdown|json|llms]

What It Writes

• state/memory/tasks/<id>.json - the structured task record
• wiki/memory/tasks/<id>.md - the markdown companion with stable frontmatter
• wiki/memory/index.md - the task index

task start also builds an initial context pack and links it to the task unless you provide an existing pack. The 2.0 memory command group remains a compatibility alias over the same files.

Related Commands

query, explore, and context build accept --task <id> so saved outputs and context packs can attach to an active task. --memory <id> remains a compatibility alias.

Examples

swarmvault task start "Implement the auth refactor" --target ./src --agent codex
swarmvault task update <id> --decision "Keep session state in the existing store."
swarmvault task update <id> --changed-path packages/engine/src/memory.ts
swarmvault context build "Review auth refactor" --target ./src --task <id>
swarmvault task finish <id> --outcome "Auth refactor shipped" --follow-up "Run installed-package smoke"
swarmvault task resume <id> --format llms

Graph and Viewer

After swarmvault compile, task records become graph nodes and decisions become decision nodes in state/graph.json. The graph viewer includes task history with status filters, task details, linked context packs, changed paths, and related graph navigation.