Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Command Surfaces
page:docs-agent-reference-command-surfacesa5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewarticlejsongraph
II.
Page overview

page:docs-agent-reference-command-surfaces

Reference · live

Command Surfaces overview

Inspect the raw attributes, linked wiki pages, and inbound or outbound graph edges for page:docs-agent-reference-command-surfaces.

PageOutgoing · 0Incoming · 1

Attributes

nodeKind
Page
sourcePath
docs/agent-reference/command-surfaces.md
sourceKind
repo-docs
title
Command Surfaces
displayName
Command Surfaces
slug
docs/agent-reference/command-surfaces
articlePath
wiki/docs/agent-reference/command-surfaces.md
article
# Command Surfaces This page is the concise command map for contributors and coding agents. It is intentionally grouped by surface so `AGENTS.md` and `CLAUDE.md` do not need to inline large command dumps. ## Core CLI: `babysitter` The `babysitter` binary is shipped by [`@a5c-ai/babysitter`](../../packages/babysitter/package.json) and [`@a5c-ai/babysitter-sdk`](../../packages/babysitter-sdk/package.json). The command families currently registered in the repo source live in [`packages/babysitter-sdk/src/cli/main/program.ts`](../../packages/babysitter-sdk/src/cli/main/program.ts). ### Agent-facing help `babysitter --help` is the automation surface. Its usage text is generated from [`packages/babysitter-sdk/src/cli/main/usage.ts`](../../packages/babysitter-sdk/src/cli/main/usage.ts) and centers on: - `run:*` and `task:*` for deterministic replay loops (includes `run:assign-process` for attaching a process to a bare run) - `session:*` for session binding and iteration guards - `skill:discover` - `process-library:active` - `profile:*` - `instructions:babysit-skill` - `harness:install` and `harness:install-plugin` ### Human-facing help `babysitter --help-human` is the operator surface. It adds: - `log`, `hook:*`, `compress-output` - `skill:fetch-remote` - `process-library:clone|update|use` - `plugin:*` - `tokens:stats` - `compression:*` - `harness:discover|list` - `instructions:process-create|orchestrate|breakpoint-handling` - `breakpoint:*` - `health`, `configure`, `version` ## Product CLI: `genty` The product CLI implementation lives in [`@a5c-ai/genty`](../../packages/genty/package.json) and is exposed as `genty`. Use `genty call` for new runtime orchestration examples. The legacy `babysitter harness:call` alias has been removed and must not appear in new tests or docs. Setup remains on the core CLI through `babysitter harness:install` and `babysitter harness:install-plugin`. Use it for human-invoked orchestration sessions and runtime services: - `create-run`, `call`, `yolo`, `plan`, `forever` - `resume-run`, `resume` - `retrospect`, `cleanup`, `assimilate`, `doctor`, `contrib` - `anycli`, `session-history` - `observe`, `tui` - `daemon:*`, `cost:stats`, `start-server` - `discover`, `list`, `invoke` ## External Agent Dispatch External agent tasks start as normal `ctx.task()` effects. The difference is the agent routing hint: `agent.responderType: "agent"` plus a required `adapter`. During orchestration, tasks-adapter chooses the responder backend. Internal responders continue through the normal agent-core path, human responders use the breakpoint path, and agent responders route to `AgentMuxResponderBackend`, which uses adapters and the lower-level `adapterBridge` integration. The command surfaces involved are split by responsibility: | Surface | Use | | --- | --- | | `babysitter run:create`, `run:iterate`, `task:list`, `task:post` | Create and replay the run, inspect pending effects, and post resolved task results. | | `babysitter process-library:active`, `skill:discover`, `profile:*` | Gather process-authoring context, available skills, and user/project preferences before deciding whether an external responder is appropriate. | | `genty discover`, `genty list`, `genty invoke` | Human-facing discovery and invocation surface for available runtime agents and services. | | `adapters doctor`, `adapters launch`, `adapters auth`, `adapters install` | adapters checks and adapter operations. See the adapters reference for the exact CLI flags. | Troubleshooting common external agent failures: | Scenario | Expected behavior | | --- | --- | | adapters is missing | If the task explicitly allows internal fallback, route internally; otherwise fail the task with an unavailable adapters error. | | Adapter is missing | Fail with an adapter-not-installed message and install guidance for the selected adapter. | | Adapter is unauthenticated | Fail with an authentication message and run the adapter auth flow before retrying. | | Task times out | Fail the task with timeout details; include partial output only when the responder backend provides it. | | Adapter process crashes | Fail the task with the adapter stderr or exit details so the next iteration can diagnose the crash. | | Fallback is disabled | Do not silently switch to an internal agent. The failed external responder is part of the task result. | Older design docs may still say `agent.external: true`, `fallbackToInternal`, or direct `adapterBridge` dispatch. The current contributor surface should describe the tasks-adapter responder route and use `responderType: "agent"` in new examples. ## Runs Directory Defaults The repo source now treats global runs storage as the default: - default scope: `~/.a5c/runs` - repo scope: `<repo>/.a5c/runs` when `BABYSITTER_RUNS_SCOPE=repo` - explicit override: `BABYSITTER_RUNS_DIR` or `--runs-dir` The implementation lives in [`packages/babysitter-sdk/src/config/runs.ts`](../../packages/babysitter-sdk/src/config/runs.ts) and the default config in [`packages/babysitter-sdk/src/config/defaults.ts`](../../packages/babysitter-sdk/src/config/defaults.ts). When reading existing runs, the SDK also probes repo-local `.a5c/runs` for backward compatibility. ## Plugin Commands Plugin concepts are covered in [Plugins Overview](../plugins.md). The dedicated command reference is [Plugin CLI Reference](../plugins/cli-reference.md). One current implementation detail worth remembering: `plugin:install`, `plugin:update`, and `plugin:configure` can auto-resolve the marketplace when `--marketplace-name` is omitted, as implemented in [`packages/babysitter-sdk/src/cli/commands/plugin/packageCommands.ts`](../../packages/babysitter-sdk/src/cli/commands/plugin/packageCommands.ts).
documents
[]

Outgoing edges

None.

Incoming edges

contains_page1
  • page:docs-agent-reference·PageContributor Reference

Related pages

No related wiki pages for this record.

Shortcuts

Open in graph
Browse node kind