Skip to content

Expose typed MCP setup with confirmed save and restart - #37

Merged
frahlg merged 3 commits into
mainfrom
codex/mcp-setup-contract
Oct 18, 2026
Merged

frahlg merged 3 commits into
mainfrom
codex/mcp-setup-contract

Conversation

@frahlg

@frahlg frahlg commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

Expose setup through seven typed MCP tools: schema, status, draft edit/reset, validation, confirmed save and confirmed restart. The connected box owns the schema, driver catalogue, draft, checks and receipt; Cloud keeps no second configuration model.

Setup write access is an explicit owner choice. Full setup reads use the existing diagnostic scope. Tool security schemes and authentication challenges preserve existing read scopes when a client requests setup. Refused scope widening during refresh no longer consumes the valid read session. A denied box response is a tool error; a lost mutation reply reports an unknown outcome and directs the client to setup_status and the same receipt.

Paired Core #1732 and web client #99 are merged. The protocol pin names their exact Core head a17455aa. Native client #92 is paired.

History dependency #29 merged first. This branch contains only setup changes above that dependency.

Validation: vet, the full race suite, dev-tag suite and import checks passed. OAuth/Noise tests cover explicit grants, old read grants, exact numbers, HTTP failures, authentication metadata, preserved read scopes, and lost save/restart replies. The real consent template was rendered and inspected in a closed local browser fixture. The affected MCP/OAuth/key suites also passed with race checking against the published pin and go.work disabled. A fixed test clock keeps the burst-limit check independent of tool-list transfer time without changing its limits.

Runtime Go growth: internal/mcp +126 lines; internal/oauth +10 lines. No new key service or data storage layer.

This does not claim new-box onboarding, vendor sign-in, invitation redemption, directory listing or physical equipment verification. Keep deployment after the paired Core release is selected.

@chatgpt-codex-connector

Copy link
Copy Markdown

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

@frahlg
frahlg force-pushed the codex/mcp-setup-contract branch from e6f7298 to 3ab545c Compare October 18, 2026 16:15
@frahlg
frahlg marked this pull request as ready for review October 18, 2026 16:15
@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-18T16:17:28.714554Z 3ab545c 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 merged commit 61df484 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