Forward unrecognized slash commands to Codex#281
Open
duclvz wants to merge 1 commit into
Open
Conversation
Let Codex resolve slash commands that the adapter does not own.
benbrandt
reviewed
Jul 10, 2026
benbrandt
left a comment
Member
There was a problem hiding this comment.
@AlexandrSuhinin Maybe you all had this this way for a reason? But I think this change seems reasonable
Collaborator
We initially supported skills with the $ prefix: the same way they are supported in CLI. But anyway I'm not against this change, probably it is still better than throwing an error. |
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.
Pass slash commands not handled by the ACP adapter through as raw prompts, allowing Codex to resolve skills freely. Built-in commands continue to be handled locally.