Skip to content
Spec{0}

Diagnostics

Settings → Diagnostics is the one place to look when something feels off — slow board, stuck claim, weird agent behavior. Everything here is local to your machine.

Log channels

Spec0 writes structured logs to eleven channels:

  • core — startup, shutdown, lifecycle.
  • ipc — main ↔ renderer round-trips.
  • events — domain events appended to the log.
  • cards — card mutations.
  • agents — agent identity, session lifecycle.
  • mcp-server — Spec0’s MCP HTTP server.
  • mcp-wire — the raw JSON-RPC frames (see below).
  • agent-sdk — internal agent-SDK calls (subset of cards used for in-app authoring).
  • artifacts — uploads, resolves, downloads.
  • persistence — SQLite operations, migrations.
  • renderer — UI-side log lines forwarded to the main process.

You can filter by channel, severity, correlation id, or free-text. Logs are sink-redacted — API keys, absolute paths, chat content, emails are stripped before they hit disk.

MCP wire log

A rolling in-memory ring of the last 1000 JSON-RPC frames per connected MCP session. Use it when you’re debugging an agent integration:

  • See the exact tool input the agent sent and the exact response Spec0 returned.
  • Spot malformed requests, unexpected errors, or unsupported tool names.

The wire log is in-memory only — when Spec0 quits, it’s gone. To preserve a slice, copy the frames into a card comment or save as a file via the Export button on the panel.

Metrics

Per-minute rollups, 24-hour ring:

  • Event append/read rates.
  • MCP tool-call counts and duration percentiles.
  • IPC durations.
  • Agent SDK call counts.
  • Artifact store sizes.

Useful for spotting trends — e.g. if MCP tool durations creep up, you’ll see it here before it manifests as agent timeouts.

Event-log inspector

The event log is the audit stream behind every Spec0 mutation. The inspector lets you browse it:

  • Scope filter (global / project / card / chat).
  • Kind filter.
  • Actor filter.
  • Time window.
  • Click an event to see the full payload.

Useful for forensics — “what exactly happened to card c14 between 14:00 and 14:30?”

What Spec0 does not collect

No telemetry is uploaded. No anonymous statistics are sent. No crash reports leave your machine unless you opt in to Settings → Crash reports. The Diagnostics pane shows you what you’d be looking at on Spec0’s servers — if there were any.