Skip to content

planned2.md

Latest commit

 

History

History
58 lines (37 loc) · 1.41 KB

planned2.md

File metadata and controls

58 lines (37 loc) · 1.41 KB

Command Tree Roadmap

The first command tree is intentionally small but structured so future features can be added without breaking mental models.

Current Foundation

  • version
  • doctor
  • config
  • engine
  • task
  • run

This gives the CLI a clear split between local concerns, engine diagnostics, task intake, and run inspection.

Why This Tree

config

Local developer state should be managed explicitly and separately from engine operations.

engine

Connectivity and service metadata checks belong in a dedicated surface rather than being hidden inside task commands.

task

Task creation and validation should feel distinct from run inspection. A task is the developer’s requested work unit; a run is the engine’s execution attempt.

run

Run inspection is expected to grow significantly, so it needs its own namespace early.

Planned Expansion

Near Term

  • run stream <runId>
  • task print-template
  • config unset <key>
  • engine providers

Medium Term

  • auth login
  • auth logout
  • profile use <name>
  • team use <team>
  • task create with interactive prompts
  • run retry <runId>

Long Term

  • policy group for route and rule diagnostics
  • provider group for richer operator actions
  • completion group for shell integration

The key constraint is that new commands should grow into existing concepts rather than reshuffling the tree every few releases.