Parent: #103
Depends on: runtime boundary design (#105)
Context
The public entry point for runtime packages should be the existing Agentic CLI. Users should not have to learn a separate command first.
The first visible step is adding a runtime command namespace, even before the local runtime package is fully implemented.
Goal
Add the agentic runtime ... command namespace to core with clear help text and minimal safe behavior.
Candidate commands
Initial surface, subject to the runtime boundary design:
agentic runtime list
agentic runtime add <name>
agentic runtime init <name>
agentic runtime run [target]
agentic runtime status
The first PR may implement only a subset if the boundary design recommends that.
Behavior expectations
- Commands should explain that runtimes are optional packages.
- Unknown runtime names should produce actionable errors.
- If
local is not installed yet, the CLI should tell the user what package/command is needed.
- The command parser should follow existing Agentic CLI conventions.
- JSON/human output behavior should follow existing CLI patterns.
Non-goals
- Do not implement package-manager install/discovery here unless the boundary design makes that the smallest coherent slice.
- Do not create the local runtime package here.
- Do not implement Pi integration here.
- Do not add Cloudflare behavior here.
Acceptance
agentic runtime --help or equivalent command help exists.
- Runtime subcommands are routed through the existing CLI dispatch table.
- Tests cover command parsing/error behavior.
- The command namespace is documented enough for the next runtime package issue to build on it.
Parent: #103
Depends on: runtime boundary design (#105)
Context
The public entry point for runtime packages should be the existing Agentic CLI. Users should not have to learn a separate command first.
The first visible step is adding a
runtimecommand namespace, even before the local runtime package is fully implemented.Goal
Add the
agentic runtime ...command namespace to core with clear help text and minimal safe behavior.Candidate commands
Initial surface, subject to the runtime boundary design:
The first PR may implement only a subset if the boundary design recommends that.
Behavior expectations
localis not installed yet, the CLI should tell the user what package/command is needed.Non-goals
Acceptance
agentic runtime --helpor equivalent command help exists.