AgentFixboard
UnverifiedLast checked OpenClaw#state#messaging

Android realtime Talk reuses an archived backing session

Android realtime Talk connects, then every agent consultation fails with Session "agent:main:node-658dba94672b" is archived. Restore it before starting new work.

From GitHub

openclaw/openclaw

IssuePull request

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
—
Last checked

Unverified: we could not confirm from the sources that a fix shipped. Source: PR #176440 merged. Last checked 2026-10-19.

Symptom

Android realtime Talk connects, then every agent consultation fails with Session "agent:main:node-658dba94672b" is archived. Restore it before starting new work.

Evidence what you'll see

  • The recorded line is OpenAI GPT-Live delegation consult failed: Session "agent:main:node-658dba94672b" is archived. Restore it before starting new work.
  • Talk session c14672ac-bdb0-485f-ab85-6a33c0d4b5b5 reached session.ready over gateway-relay / agent-consult, then the consultation failed 3 seconds later.
  • Gateway state showed that backing session archived on 2026-10-12 23:22:00.724 UTC. The issue's restore command is openclaw gateway call sessions.patch --params '{"key":"agent:main:node-658dba94672b","archived":false,"expectedSessionId":"550d58fa-64a8-4394-bb04-f262617d77ed"}'.

Why it happens

Talk's identity initializer accepted an archived session ID, while consult admission correctly rejected it. Pull request 176440 restores the archived backing session in place before voice connects, keeping the session ID.

Affected versions

Official Android app showing version 2026.10.30 against Gateway 2026.10.3. Talk config in the report: provider openai, realtime model gpt-live-1-codex, mode realtime, brain agent-consult, transport gateway-relay.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

How to check it worked

  • A later Talk start consults the backing agent without is archived. Restore it before starting new work.

If it still fails

  • No published release tag contains pull request 176440. Tag v2026.10.5 was compared against merge 4a9b42a5dbc5 and does not contain it.
  • Restart-recovery tombstones, blocked worker placements, and automation still cannot revive the session. The pull request does not address the separate authority-lifetime issue #167876.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it