acp run time not configured | Friends of the Crustacean 🦞🤝 | Page 1

formal galleon Apr 27, 2026, 11:06 AM

#

my agent is doing a major file and keeps timing out bc of
agents.defaults.llm.idleTimeoutSeconds so i tried to do sub agents and it said this "I hit a blocker with sub-agent deployment (ACP runtime not configured)"

untold horizonBOT Apr 27, 2026, 11:06 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

teal cosmosBOT Apr 27, 2026, 11:16 AM

#

First, can you paste openclaw --version? Version matters a lot for ACP/sub-agent behavior.

Likely issue: your agent tried to spawn an ACP session, not a native OpenClaw sub-agent. ACP is for external harnesses like Codex / Claude Code / Gemini CLI; native sub-agents use sessions_spawn with the default runtime: "subagent" and don’t require ACP. The docs call out that ACP errors like ACP runtime backend is not configured mean the acpx backend/plugin is missing/disabled, and recommend /acp doctor. (docs.openclaw.ai)

For your case:

{
  agents: {
    defaults: {
      llm: {
        idleTimeoutSeconds: 300 // or 600; 0 disables idle timeout
      },
      timeoutSeconds: 1800,
      subagents: {
        runTimeoutSeconds: 1800

#

      }
    }
  }
}

Then restart the gateway.

If you want native sub-agents, tell the agent explicitly:

Use sessions_spawn with runtime: "subagent" / default runtime. Do not use ACP.

If you want Codex/Claude Code/Gemini ACP sessions, run:

#acp run time not configured