Guild Stack

Docs section

View

Inspect recorded work through the local dashboard or the optional Claude Code status line.

Start with Inspect runs in the local dashboardAll docs

Page evidence

Operational mapThe dashboard reads the run. It does not become the truth.
Views
  1. Runsmanifest + status
  2. Timelinephase events
  3. Knowledgederived graph
  4. Wikicanonical pages
Boundary
  1. 127.0.0.1local by default
  2. .guild/filesystem source
  3. No projector writeread-only view
Local views read manifests, receipts, and events from disk, then point back to the exact record behind each signal.
Diagram notes and sources
  • docs/v2/observability.md
  • docs/v2/architecture/modules/dashboard.md

Common tasks

Start with the signal, then open the record.

Open the local dashboard

Launch the benchmark UI against recorded project runs over loopback HTTP.

Read the active signal

Add the optional Claude Code status line for compact phase and loop context.

Trace from disk

Reconstruct the route from manifests, handoffs, verification, and events.

Route guides

Inspect projections without confusing them for truth.

View

  • Inspect runs in the local dashboard

    Launch the benchmark dashboard on 127.0.0.1, import recorded Guild Stack runs, and inspect timelines, knowledge, and wiki evidence without a cloud service.

  • Claude Code status line

    Add an opt-in Claude Code status line for active Guild Stack runs: loop round, cap, loop mode, restart count, and phase signal when available.

A useful view always points back to evidence.

Continue into Build to inspect the contracts and module ownership behind those records.
Build docsDocs gateway