Repository navigation
remote: connect your brain in Claude on the web and phone (brain mcp --http, mcp-router, brain_capture) - #227
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
One authenticate_post for the router and the vault server, one normalize_email (schemas), a default DrainReport in the cycle, a single shared RSA key for the tests, one JSON-RPC builder, and no HMAC warning. Claude-Session: https://claude.ai/code/session_0145uCzuUjLpe6rbH4WTf43Z
Merged
This branch was successfully deployed
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
Claude on the web and in the phone app can only reach a server over HTTPS. This lets each person connect their own brain to Claude: one connector address per company, everyone clicks Connect and signs in with their work email. Spec:
docs/superpowers/specs/2026-10-06-remote-mcp-design.md(local, gitignored).brain mcp --httpserves one person's compiled vault on loopback. It answers only to a request signed for that person's email.brain mcp-routerroutes each signed-in email to that person's process. It holds no vault.brain_capturesaves a note into the person's Inbox. Notes wait in a per-person spool andbrain cycle --spool-root DIRfiles them throughingest_note.remoteauth.pychecks the signed identity (RS256 only, issuer/audience/expiry, key rotation) an identity edge such as Cloudflare Access attaches. brainkit runs no sign-in server.brainkit[remote](PyJWT, floor>=2.10.1); base install and dependencies are unchanged.deploy/brain-box/brain-mcp@.serviceandbrain-mcp-router.service;brain-liveness.shno longer reports systemd templates as down.docs/guides/remote-access.mdx, reference pages, changelog.Why this shape
Proven by a live spike on Embark (2026-10-06): claude.ai connected through Cloudflare Access Managed OAuth and answered from a real brain. The tenant wall stays physical: every process that opens a vault opens exactly one, and a routing mistake is refused (
wrong_person), never served.Verification
ruffclean. Docs site builds.tests/test_remote_e2e.pyruns the real router, two vault servers, a capture and a cycle drain in one process, including a deliberately wrong route.brain mcp-router/brain mcp --httpexit 2 namingbrainkit[remote].Not in this PR
Fleet provisioning (hostnames, Access app, units, UI) is a separate plan in the fleet repo and needs brainkit 0.9.0. The release PR comes after merge. Deferred: HTTP status in request log lines.
https://claude.ai/code/session_0145uCzuUjLpe6rbH4WTf43Z