[codex] Restore CAS runtime slash commands#112
Draft
zeolenon wants to merge 3 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
openclaw.plugin.json.commandAliasesfor the plugin-owned/cas_*commands so newer OpenClaw cores can route them through the plugin command path./cas_verbosethrough the same runtime slash command metadata.Why
OpenClaw 2026.5.x uses plugin manifest metadata to discover and route runtime slash commands. Without the explicit activation hints and command aliases, commands such as
/cas_statusand/cas_verbosecan appear present in docs/config but fail to route to the Codex app-server plugin.Validation
pnpm typecheckpnpm testpnpm pack:smokecommands.listexposes/cas_verbose, plugin registration reportshasCasVerbose=true, and Codex/Gemini post-update agent smokes pass.