Skip to content

docs: clarify set-mode mode ids are adapter-defined#27

Merged
Takhoffman merged 1 commit intoopenclaw:mainfrom
z-x-yang:docs/set-mode-adapter-defined
Mar 9, 2026
Merged

docs: clarify set-mode mode ids are adapter-defined#27
Takhoffman merged 1 commit intoopenclaw:mainfrom
z-x-yang:docs/set-mode-adapter-defined

Conversation

@z-x-yang
Copy link
Copy Markdown
Contributor

Summary

This docs update clarifies that set-mode values are adapter-defined and not guaranteed to be portable across all ACP adapters.

Changes

  • README.md
    • Replace acpx codex set-mode plan example with acpx codex set-mode auto.
    • Add note that unsupported mode ids are rejected by adapters (commonly Invalid params).
  • docs/CLI.md
    • Add behavior notes under set-mode explaining adapter-defined mode ids and rejection semantics.
  • skills/acpx/SKILL.md
    • Align example and behavior note with the same clarification.

Why

Users can copy examples like set-mode plan and reasonably expect universal behavior. In reality, whether plan is accepted depends on the selected adapter's exposed modes.

This keeps examples practical and reduces confusion without changing runtime behavior.

@Takhoffman Takhoffman merged commit a0e34df into openclaw:main Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants