Control Surfaces

Toolang exposes three main ways to drive agents:

• the CLI
• a per-agent local HTTP API
• a shared local bus API

Use the smallest surface that matches the job.

CLI first

Most workflows start in the CLI:

toolang new <name>
toolang clone <agent_ref>
toolang sync <agent_selector>
toolang invoke <agent_selector>
toolang run <agent_selector>
toolang start <agent_selector>
toolang bus serve

The CLI is the best default when you are:

• creating or cloning an agent
• inspecting local state
• running one-shot work from scripts or CI
• starting or stopping local runtimes

Agent API

Each started agent exposes a local HTTP API for direct UI or client use. The main endpoint families are:

• health
• agent and runtime metadata
• caps
• tasks, chores, and will
• chat
• runs
• events

Use the agent API when one specific running agent should serve a local app, editor, or UI.

Bus API

Toolang can also expose a shared local bus API over the global event projection:

toolang bus serve

The bus API is useful when you need one local endpoint that can:

• list known and active agents
• stream global or per-agent events
• proxy requests to active agents

How to choose

• choose the CLI for authoring, scripting, and machine operations
• choose the agent API for one running agent and its state
• choose the bus API for multi-agent local tooling

Read next

• Read Running Agents for invoke, run, and start.
• Read Troubleshooting if the API is up but the agent is not behaving correctly.
• Read Developer Control Surfaces for the full endpoint and registry model.