feat: Remote permission server #1187
Open
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
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
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
This PR introduces a remote permission mode to Codex CLI, enabling the agent to request command approval decisions from a remote permission server.
Why
I needed this for a project I'm working on; this is the minimal set of features I needed for my use-case but happy to polish and extend if this is something people want. Remote permission opens the door for quite a lot of downstream applications. For example, as these things get increasingly capable and people start wanting to run many in parallel, something like this is needed to avoid ending up stuck staring at dozens of tmux panels.
How
--remote-permission,--permission-server-url, and--agent-idto configure the remote permission workflow.socket.io-based websocket client (requestRemotePermission) to connect to the server.runRemoteModetocli.tsx- similar to existingrunQuietMode.