AgentFixboard
UnverifiedLast checked OpenClaw#messaging#error-messages

Control UI forgotten-send retry fails with 'Personal authoring cannot move to a replacement run'

In Control UI chat with messages.visibleReplies: "message_tool", a turn that answers in plain text without message(action=send) fails the stranded-reply retry. The user sees Your request couldn't be completed: Personal authoring cannot move to a replacement run. Send a fresh message.

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 #182219 merged. Last checked 2026-10-24.

Symptom

In Control UI chat with messages.visibleReplies: "message_tool", a turn that answers in plain text without message(action=send) fails the stranded-reply retry. The user sees Your request couldn't be completed: Personal authoring cannot move to a replacement run. Send a fresh message.

Evidence what you'll see

  • The log is [diagnostic] lane task error: ... error="Personal authoring cannot move to a replacement run. Send a fresh message." errorName=SkillLibraryError taskKind=turn.
  • The same setup on a channel turn did not hit this. The Control UI turn carries a personal skill-authoring grant that refuses to bind to a second run.

Why it happens

The stranded-reply retry is built from the source run and keeps its skillLibraryAuthoring grant. That grant's bind() refuses the replacement run. Other internal follow-ups already swap in an expired personal-only grant. Pull request 182219 uses that same expire helper for the forgotten-send retry.

Affected versions

Reproduced on main adb8920e42e. The report says the source path is the same in 2026.10.6. macOS 26, source checkout. messages.visibleReplies: "message_tool".

Fix steps

0 of 2 done

Your check marks stay in this browser only.

How to check it worked

  • A Control UI turn that answers without message(action=send) no longer fails with Personal authoring cannot move to a replacement run. Send a fresh message. The retry starts.

If it still fails

  • No published release tag contains pull request 182219. Tag v2026.10.7 was compared against merge fade14fea653 and does not contain it (diverged).
  • The pull request says delivery still depends on the retry calling message(action=send).

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