Skip to content

MANUAL RUN: codeSplitters Executor hookup on the live site (OAuth sign-in) #418

Closed as not planned

Description

@QuinnsCode

Split out of #411. This is setup on your machine against the live site, with no code. It needs the OAuth PR for #411 deployed first (release as usual).

  1. npm install -g executor, then executor web.
  2. Add Integration → https://codesplitters.notryanquinn.workers.dev/api/openapi.json.
  3. Add account → pick the oauth scheme, client_id executor (any name works for a localhost redirect). A codeSplitters consent page should open: choose read or read-and-write, then Allow. If Executor only offers a bearer token, make a new one on your profile page instead (don't reuse the "claude code" one).
  4. Policies: codesplitters.* → approve; repos.deleteRepo, branches.mergeBranch, files.commitFile, deploys.deploy → require approval.
  5. npx add-mcp http://127.0.0.1:4788/mcp --transport http --name executor, then restart the agent.
  6. Check: Executor appears under "Apps signed in" on your profile page, and signing it out there makes its next call a 401.

Also worth a try: claude mcp add --transport http codesplitters https://codesplitters.notryanquinn.workers.dev/api/mcp with no header, then /mcp in Claude Code → Authenticate. It should open the same consent page.

Notes from #389: Executor's previewSpec takes the spec as a string, but addSpec needs {kind: "url", url}. Executor gates every non-GET call behind approval by default.

Activity

  1. added
    manual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close it
    on Oct 10, 2026
  2. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Claude Code half done on live (2026-10-10): claude mcp add --transport http codesplitters https://codesplitters.notryanquinn.workers.dev/api/mcp with no header → /mcp → Authenticate → consent page → "Authentication successful. Connected to codesplitters." Discovery, dynamic registration, PKCE and the token swap all worked against the deployed build.

    Still to do here: the Executor steps (1–6 above), and a profile-page sign-out check (the app's next call should 401).

  3. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Still open here: the Executor steps 1–6 above (step 6 is the sign-out → 401 check). Claude Code's OAuth sign-in is done.

    Tidying on your Mac, all optional:

    • Your user-scope codesplitters MCP entry still uses a token. To switch it to sign-in: claude mcp remove codesplitters -s user, then claude mcp add -s user --transport http codesplitters https://codesplitters.notryanquinn.workers.dev/api/mcp, then /mcp → Authenticate. After that, delete the old "claude code" token on your profile page.
    • ~/cs-oauth-test was only for the test and can go.

    🤖 Generated with Claude Code

  4. QuinnsCode commented on Oct 11, 2026

    @QuinnsCode
    OwnerAuthor

    Tracked in #609, the one hands-on checklist. The steps here still apply; tick them there.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    manual runNeeds the owner to run it by hand (tokens, sign-ins); agents can't close it

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions