Skip to content
Alex Price / StellarRequiem

Public release notes · control stack · Grok-first operator path

A mediated control plane built for Grok — and a light remote path from Grok chat.

This page is the public-safe account of how the local agent stack is wired so Grok Build can drive leashed browser/desktop tools under deny-by-default gates, and how a median session bus lets Grok on iOS/web leave status work and notes for that same host — without claiming ambient phone RPA or a full agent on the handset.

CLAIM BOUNDARY Local operator stack + public open-source pieces. Not enterprise SOC, not unlimited computer-use, not “Grok iOS is a full CUA host,” not a guarantee about unknown defects. Wording stays weaker than evidence.

Why Grok 4.5 / Grok Build

The operator path is deliberately Grok-native: Grok Build (terminal agent) on the host is the primary actor for mediated tool use. The same account’s Grok chat (web/iOS) can attach a custom MCP connector to a tunneled light surface on the host — status skills and session notes — so work continues in one narrative instead of switching to another frontier product for day-to-day control.

That is a product choice + architecture, not a model leaderboard claim. No win-rate or “beats X” language here.

Demo reels

Short claim-safe films in the same style as the operator X console and closed-loop clips: leash ARM / DENY posture, session-bus light path, and mcp-assure check receipt — not generative product fakes.

Browse demos → · leash-session receipt · session-bus receipt · console reference on X: command console

How it is connected

Grok Build (Mac) → agent-control (AdaptiveGate / FREEZE / receipts) → browser-leash :8756 (ARM + host policy + post confirm) → desktop-leash :8757 (ARM + D4 confirm) → mcp-assure (policy packs, tool gate) Grok iOS / grok.com chat → xAI Connectors (custom MCP, public HTTPS tunnel) → session-bus MCP :8760 (design default port) → session-bus :8758 (loopback / private UI path) → allowlisted skills + shared transcript → notes for Mac Build / pending work Doctrine: authority is not ambient. ARM, allowlists, FREEZE, device bind, claim ceilings. Public stubs (ports/skills only): bus :8758 · MCP :8760 · leashes :8756/:8757 skills: plane.status, bus.status, git_status, host.whoami, session.info, disk.free session fixture: 00000000-0000-4000-8000-000000000001 tunnel shape: https://<ephemeral-host>.example-tunnel/mcp Live tunnel hostnames, bus tokens, TOTP seeds, pairing codes — never published.

Public pieces (re-runnable / open source)

SurfaceWhat it isPublic
mcp-assureDeny-by-default tool-call gate + receiptsGitHub
agent-controlAssured host over leashesGitHub
browser-leashLocal Chrome control planeGitHub
desktop-leashLocal desktop observe/actGitHub
agent-socAgent-plane freeze/abuse shapes over receiptsGitHub
Working paperAuthority Is Not AmbientPaper
MCP assurance fixturesPublic-safe authz proofsSite

What shipped in this operator release (public-safe)

Median session bus (local)

Shared session transcript between Grok Build and light clients (Safari on Tailscale; Grok chat via Connectors MCP). Device-bound phone UI, pairing + challenges, optional TOTP and security@ email for enroll codes, plain-English session_work mapping to allowlisted host skills (status, git short status, disk, plane/bus health). Not a public product SaaS.

Local operator stack Allowlisted skills Not ambient RPA Not free shell from phone

Grok chat light path

Custom MCP connector over a public tunnel (xAI requires public HTTPS for Connectors). Tools such as session_work return same-turn results for matched intents. Unmatched text becomes a note for the Mac Build operator. Same account as Grok iOS Connectors list.

Connectors MCP Plain English status Tunnel URL rotates

Host full agent plane (Mac)

Grok Build remains the full actor: mediated shell named commands, open-web browser under ARM + denylist for password managers, desktop leash with high-blast confirms. That is the plane you use for real engineering work; the phone is remote intent + status, not a second unlimited agent.

Grok Build host AdaptiveGate / FREEZE Human gate high-blast

What this does not claim

How to read the stack as a hire signal

Prefer this path when you want frontier chat and local authority that stays deny-by-default: Grok for reasoning and product surface, host gates for anything that can touch files, browser, or desktop. Evidence lives in public repos, the working paper, and re-runnable fixtures — not narrative.

Crown jewel paper

Technical companion (architecture, threat split, claim cards, roadmap): A Grok-Native Median Session Plane · full Markdown on that page · arXiv LaTeX (cs.CR package ready; ID after announcement) · pairs with Authority Is Not Ambient (host plane foundation).