autonome-pi

Autonome's Pi package for shared extensions, workflow tooling, and skills.

Contents

• thread-phase-visualizer — generic TUI monitor and event store for thread-phase-ui/v1 workflow events.
• detach — /detach and /detach-status commands for handing an interactive Pi session off to tmux so it can survive an SSH logout.
• codebase-exploration-workflow — fanout codebase exploration workflow using Pi subagents.
• code-review-workflow — git diff/commit code review workflow using Pi subagents.
• dynamic-workflows — simple validated composer for ordered agent, fanout, shell, and artifact phases, plus a separate advanced JavaScript harness tool.
• mission-workflow — Droid/Missions-style long-running software mission extension with plan approval, validation contracts, strict handoffs, per-feature worktrees/commits, command + adversarial validators, durable registry/resume, coverage artifacts, and repair loops.
• skills/dynamic-workflows and skills/mission-workflow — on-demand Pi skills that teach other sessions/configurations how to use these workflow tools safely.

Install

pi install git:git@github.com:autonome-research/autonome-pi@v0.17.1

For active development:

pi install git:git@github.com:autonome-research/autonome-pi@main

To migrate an installation that still uses the old repository identity:

pi remove git:git@github.com:Code4me2/pi-thread-phase-tools@v0.12.0
pi install git:git@github.com:autonome-research/autonome-pi@v0.17.1

Pi identifies git packages by repository URL, so remove the old source before installing the renamed one to avoid loading both copies.

Usage

• /detach [--name <tmux-name>] [--now|--wait] [prompt] hands the current session off to tmux; /detach-status reports the latest handoff. See detach/README.md.
• Select /workflows from the slash-command menu under the editor, or press ctrl+shift+t, to open the interactive thread-phase dashboard; select a run for details or request cooperative cancellation via x.
• Background dynamic workflows durably return control to the launching Pi session after success or failure; failed continuations identify failed phases/errors/partial artifacts, while user-cancelled runs never auto-continue.
• /codebase-explore starts codebase exploration in the background by default.
• /code-review runs code review workflows.
• dynamic_workflow composes validated subagent workflows directly from flat agent, fanout, shell, and artifact phases. dynamic_workflow_harness is the separate advanced JavaScript interface; dynamic_thread_phase_workflow is an inactive deprecated compatibility alias.
• mission_workflow plans and activates approved Droid/Missions-style software missions. Always run action: "plan" and get user approval before action: "activate".
• Tool/API inspection remains available through thread_phase_runs.
• Workflow skills are included in the package and should load automatically when tasks ask for dynamic workflows, mission workflows, structured workflow specs, JS harness workflows, or multi-phase dynamic execution.

Current status

Latest release: v0.17.1.

Recent changes:

• Recovered and completed the workflow-agnostic visualizer improvements on the renamed repository baseline.
• Added bounded/corruption-tolerant JSONL reads, immutable owner/session verification, aggregate ownership budgets, and crash-safe index reconciliation.
• Added interactive monitor search/filter/sort, responsive phase/fanout/artifact pagination, safe artifact editor actions, and consistent owner/stale displays.
• Added durable once-only continuation delivery with pending/delivered recovery across extension reloads and Pi session persistence boundaries.
• Added comprehensive visualizer projection, cancellation, continuation, session-scope, large-log, and TUI interaction tests.
• Renamed the package and repository from pi-thread-phase-tools to autonome-pi.
• Added the tmux-backed /detach extension and /detach-status command.
• Cooperative cancellation uses cancel request files under ~/.pi/agent/thread-phase/cancel/<runId>.json instead of direct monitor PID killing.
• dynamic_workflow now accepts the workflow directly—no outer spec wrapper—and uses the clearer agent, fanout, shell, and artifact phase names.
• Permissions are explicit phase defaults/overrides: r, w, rw, and rwx; shell and Pi bash execution require rwx.
• Advanced unsandboxed JavaScript control flow moved to dynamic_workflow_harness, which requires explicit permissions: "rwx".
• dynamic_thread_phase_workflow remains registered for compatibility but is inactive by default, avoiding a duplicate legacy schema in normal model context.
• Structured specs now have a strict phase schema, semantic reference/permission/resource preflight, bounded supervised fanout, explicit retries, collision-safe artifacts, multipart Pi output handling, partial failure results, and background readiness acknowledgements containing runId + pid.
• Reusable or operationally important workflows should graduate into standalone TypeScript extensions using thread-phase directly.
• Dynamic workflow runs carry system-generated chain provenance. A terminal successful or failed parent accepts at most one session-scoped successor through after; cancelled parents cannot continue a chain.
• Reusable structured workflows and self-contained harnesses can be loaded by safe template name from ~/.pi/agent/workflows/; template loading is bounded, rejects traversal/symlinks, preserves provenance, and still enforces normal validation and permission ceilings.
• Structured workflows support fail-closed resumeRunId recovery through atomic checkpoint manifests and bounded, hashed phase-output artifacts; spec, cwd, model, session, phase identity, containment, size, and integrity must verify before reuse.
• The workflow dashboard is available through selectable /workflows and ctrl+shift+t entry points, shows compact elapsed-time and aggregate-token metrics, and labels phase/fanout rows with observed inference models instead of redundant worded statuses.
• Usage events are aggregated into run, phase, and fanout-item summaries and rendered in tools/monitor/completion cards.
• npm test runs smoke coverage for extension load, permission denial before harness import, structured validation, JS harness mode, structured shell mode, usage projection, and mission registry/resume/strict-handoff checks.
• The package now ships workflow skills so fresh Pi sessions get progressive-disclosure guidance for dynamic workflows and mission workflows.
• Hardened mission_workflow with adversarial post-milestone validation, runner-owned handoff metadata, durable trusted checkpoints for resume, strict validation-cursor fingerprints/evidence checks, merge-blocking transient lockfile quarantine, stale lastError archival after successful resume/completion, cancellation-safe validation, contaminated-branch detection/reset, assertion coverage reports, generated-junk protection, transient uv.lock cleanup with audit artifacts, short content-addressed repair IDs, runner-provided handoff skeletons, compact result payloads, and capped repair loops.
• The generic visualizer now deduplicates repeated artifact paths, closes phase-event-only phases when a workflow reaches a terminal status, keeps compact run/monitor summaries focused on recent or active phases, and removes stale/dead or terminal workflows from the below-editor live-status widget.
• Thread-phase dependency is ^6.1.0, using the built-in node:sqlite runtime plus authoritative lifecycle, supervised fanout, atomic terminal events, cancellation, ownership, heartbeat, defensive error normalization, and bounded cursor reconciliation.
• Mission continuation/failure-mode notes are in docs/mission-workflow-continuation.md; the DX/agent-X roadmap for making missions closer to a full software production pipeline is in docs/mission-workflow-completeness-roadmap.md.

Remaining work

High-value follow-ups:

• Dynamic workflow hardening: add broader permission-matrix coverage.
• Usage budgets: optionally fail/stop workflows when projected token usage exceeds configured limits.
• Mission workflow follow-ups: validation categories/completion levels, operational-readiness contracts, heterogeneous model role policy, smarter repair planning, richer agent handoffs/shared mission notes, registry integrity/resume explain mode, external integration test conventions, and larger dogfood tests.

Notes

This package intentionally stores workflow runtime data outside the package under:

~/.pi/agent/thread-phase/

Do not commit generated run logs or artifacts.