[codex] add hosted one-command agent connections - #42
Merged
Conversation
junseo2323
changed the title
junseo2323
marked this pull request as ready for review
June 22, 2026 00:55
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 changed
context-hub connect <agent>with browser sign-in, API-token creation, and automatic MCP registration.context-hub.0.2.0.Why
Users previously had to copy JSON configuration manually and the main guide mixed local and hosted setup. The new flow connects a supported agent to the hosted Hub with one terminal command.
Validation
npm run typecheckEMBEDDING_PROVIDER=noop npm test— 105 tests passednpm run buildnpm run web:buildcontext-hub connect --helpand version0.2.0.