iiRecord
Agentic AI Atlas · GAP-USER-001: Operator Command Layer
page:docs-harness-features-backlog-gaps-user-experience-gap-user-001a5c.ai
II.
Page reference

page:docs-harness-features-backlog-gaps-user-experience-gap-user-001

Reading · 1 min

GAP-USER-001: Operator Command Layer reference

Operator command layer that surfaces key babysitter commands as in-session actions during breakpoint interactions, enabling operators to inspect status, modify configuration, and manage effects without leaving the orchestration flow.

Pagewiki/docs/harness-features-backlog/gaps/user-experience/GAP-USER-001.mdOutgoing · 0Incoming · 1

GAP-USER-001: Operator Command Layer

FieldValue
Categoryuser-experience
PriorityHigh
EffortL
StatusPartial

Description

Operator command layer that surfaces key babysitter commands as in-session actions during breakpoint interactions, enabling operators to inspect status, modify configuration, and manage effects without leaving the orchestration flow.

Current State

50+ babysitter CLI commands are terminal-only. During orchestration, the operator interacts only through breakpoints (no embedded SDK dashboard exists yet).

Target State

Key commands (run:status, task:list, tokens:stats, run:events) surfaceable during breakpoint interactions. Operators can inspect and act without breaking orchestration flow.

Dependencies

  • GAP-UX-005 -- structured status view for in-session display

Key Files

ComponentPath
CLI commandspackages/sdk/src/cli/
Breakpoint typespackages/sdk/src/breakpoints/types.ts
Interaction modulepackages/sdk/src/interaction/

Recommendation

Phase 2 implementation. Create operator command layer that wraps key CLI commands for in-session invocation during breakpoint interactions.