Configure

Agent adapters

Choose the agent that answers when you talk and works in your workspace.

Choose an integration

Each adapter turns its agent's text, tool activity, and permission requests into the shared voice session. The table describes the implemented paths, not release certification.

Agent	Connection	Key distinction
Hermes	ACP to your installed Hermes, or a Hermes dashboard gateway	Uses the Hermes you have installed by default. A pinned, isolated runtime is opt-in; its protected bridge restricts tools and disables delegation.
Codex	App Server JSON-RPC	Tool lifecycle and approvals; no worker roster mapping.
Claude Code	Claude Agent SDK	Permission callback and native task lifecycle events.
Cursor	ACP or Python SDK	ACP approvals; the protected SDK path disables tools.
Pi	RPC subprocess	Sleeptalk's built-in default. Packaged permission extension; ephemeral default session.
oh-my-pi	RPC; isolated SDK for protected setup	Worker events in general mode; restricted tools in protected mode.
OpenClaw	WebSocket gateway or ACP	Preview. Gateway admission does not complete private onboarding.

Use Just a model to talk to a model with no agent and no tools. It needs one OpenRouter, OpenAI, or Anthropic key, or a local Ollama. Use custom agents for your own integration over a command, HTTP, a bridge, or a plugin.

Select and check the agent

Open the settings page to select and configure the agent:

Run from your workspace

sleeptalk settings

The settings page lists installed agents first and checks the integration when you switch. Complete any required agent login on the runtime host. For the terminal wizard, run sleeptalk settings --terminal. See settings.

An agent setting up Sleeptalk for you passes --agent to sleeptalk host ensure and sleeptalk host input link. See agent setup. Each agent page lists its prerequisites and protected-path limits.

Check the profile before a call:

Validate the selected profile

sleeptalk doctor --config /path/to/profile.toml

Fix the first failure it reports before you start a call. A passing check does not prove microphone playback, and it does not certify every model and transport combination.

What an event means

Text becomes speakable sentences. Tool events carry start, progress, completion, or failure. A permission request asks for a decision; it grants nothing by itself. Worker events need a child identity and evidence from the adapter.

Agent pages cover typed events and the older activity notifications some adapters still send. Support varies by connection and policy. A detected worker does not mean Sleeptalk can cancel it on its own.

What you hear depends on the call destination and your tool narration setting. See tool calls and sub-agents.

Conversation continuity

--conversation-id on host start-voice and sleeptalk link records the originating conversation on the call ticket. It does not resume that agent thread by itself. Resuming needs the adapter's own session setting; for example, Codex uses agent.gateway_session_id for an explicit thread ID. Confirm the adapter accepted the session; otherwise treat the call as new.

See the support matrix for current limits.