Add Codex Managed Channel to Remote Access - #238
Open
fantasyce wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Adds Codex Managed Channel to the Remote Access section with one factual description and the required star badge.
Have you used it, and for what?
Yes. I used version 0.1.0 as a lifecycle-controlled SSH boundary between Codex Desktop and a remote macOS host. Acceptance covered checksum-verified install, idempotent reinstall, official app-server initialization, a read-only official Computer Use call, scoped process/socket cleanup, and exact uninstall. The acceptance used disposable identifiers and retained no host, account, key, task, or raw-log data.
The project is Codex-specific, open source, and actively maintained.