Skip to content

Share MCP access with six-character invitation codes - #38

Merged
frahlg merged 3 commits into
mainfrom
codex/mcp-shared-access
Oct 18, 2026
Merged

frahlg merged 3 commits into
mainfrom
codex/mcp-shared-access

Conversation

@frahlg

@frahlg frahlg commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

An owner can share their home with another person's MCP client through a six-character code such as K7M-4PX. The recipient keeps its own key. Core grants only the intersection of the invitation and the client's request after Noise proves that key; the signed roster then completes ordinary OAuth/PKCE.

Publish a strong Core invitation through TLS and return a unique alias valid for at most ten minutes. Keep bearer mappings in memory; keep only keyed digest reservations in SQLite so a restart cannot reuse an unexpired code for another home. The original browser cookie, Origin and separate attempt limits protect redemption. Cancellation, expiry and revocation still come from Core. A lost reply retries the same invitation. A Cloud restart requires the owner to republish it. The current deployment uses one OAuth process; multiple processes need routing for the in-memory mapping.

Paired Core protocol: srcfl/ftw@codex/mcp-shared-access, pinned to v0.0.0-20261018181148-499d5de65104. Base this PR on setup PR #37. The canonical webapp and native contract copies use the same branch name. Merge after Core #1735 and its registry pair, then deploy with the common next Core beta.

Validation: GOWORK=off vet, the complete race suite, dev-tag suite and import checks pass on the combined final head f518a8d. Affected-package race tests pass for OAuth, MCP, store, keys and uplink. The TLS test covers publishing six characters, the recipient's own OAuth cookie/key, Noise proof, narrower rights, Keep/PKCE, an MCP read and 401 after revoke. Core's own tunnel test covers its proof/commit path separately. Tests also cover collision, restart reservations, lost replies, cancellation, key forgetting, and expired secret cleanup. No real ChatGPT or hardware session is claimed. Full CI passes on head 3d6a6e0, including vet, complete race tests, development-tag tests, import boundaries, fuzzing, MCP inspector and Linux builds. The actual consent template was rendered and inspected in a closed local browser fixture. go.work stays untracked and outside the Docker context.

Production Go growth relative to #37: keys +45 lines, MCP +59, OAuth +370, store +79, uplink +15, command wiring +2. Tests excluded.

@chatgpt-codex-connector

Copy link
Copy Markdown

To use Codex here, create an environment for this repo.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-18T18:08:04.483786Z f073eeb Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@frahlg
frahlg force-pushed the codex/mcp-shared-access branch from f073eeb to 3d6a6e0 Compare October 18, 2026 18:16
@frahlg
frahlg changed the base branch from codex/mcp-setup-contract to main October 18, 2026 18:22
@frahlg
frahlg merged commit fed553c into main Oct 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant