Skip to content

Slash commands: cockpit and truth-surface wiring #1887

@Hmbown

Description

@Hmbown

Scope

Wire command outcomes into the truth surface so slash commands do not feel like invisible side effects. The cockpit/sidebar should show the active command, last event, failure reason, recovery hint, and detail handle when output is summarized.

Command families in scope:

  • State and telemetry: /status, /statusline, /tokens, /cost, /cache, /system, /context
  • Safety and recovery visibility: /compact, /undo, /retry, /diff, /change, /edit
  • UX/reporting surfaces: /home, /links, /feedback where they affect current session state

PEEK framing

Use Distiller / Cartographer / Evictor as the cockpit discipline: distill noisy command output into decision-quality rows, place each row in Now/Recent/Pending/Budget/Levers, and evict stale rows before losing the detail handle.

Acceptance

  • /compact is visible as a real Budget/Levers affordance, especially around the 60 percent context-pressure hint.
  • Command failures expose the actionable error and a detail handle instead of stale CLI snippets.
  • Recent command/tool rows are bounded but auditable.
  • Tests cover at least one successful command receipt, one failed command receipt, and one summarized output with detail access.

Related: #1884, #1551, #1735, #1607, #1682.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationImprovements or additions to documentationenhancementNew feature or request

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions