feat: add Grok Build account surface for v0.0.16

[robotlearning123]

Draft / do not merge

This is a partial stacked feature PR for the v0.0.16 Grok dual-account release. It depends on PR #30 and the predecessor v0.0.12-v0.0.15 release sequence. It deliberately contains no version bump and must not merge in its current state.

The website surface is not complete. Both reviewed Chrome profiles currently render grok.com signed out, so the private website contract for ordinary chat, continuation, Heavy reconnect, history, deletion, and upload could not be captured without fabricating routes. That work remains blocked until an authenticated grok.com composer is available.

Problem and user impact

The Grok subscription has two independent capability and authentication surfaces: the official Grok Build CLI for repository agent work, and the private grok.com session for website chat features. Treating them as one token would blur security boundaries, make failures ambiguous, and prevent MCP agents from using the already-available official Build subscription safely.

This stack exposes the verified Build lane now while retaining strict separation from ChatGPT auth and from the unfinished website lane. It also establishes the shared security primitives needed by the final dual-surface release.

Implemented in this partial stack

• Closed Grok error codes, route/identifier redaction, and owner-private bounded JSON reads.
• Provider-neutral bounded subprocess execution with timeout/output caps and descendant cleanup.
• Configured-root Grok Build client using the official CLI, account catalog/status discovery, bounded plan/apply agent execution, sanitized results, and no API-key fallback.
• Three explicit MCP tools: grok_build_agent, grok_build_models, and grok_build_status.
• Probe-free server startup and provider-separated ChatGPT/Grok tool manifests.
• Secure gpt2agent grok-setup website-auth storage/import boundary, without claiming live website compatibility.
• Route-independent, descriptor-safe upload policy and process-local attachment registry; no speculative upload HTTP route or MCP tool is exposed.
• Opt-in Grok Build live gate with one minimal plan-mode call and a sanitized receipt.
• Count-independent package checks and truthful Build-only configuration, security, troubleshooting, and bundled agent guidance.

Security boundaries

• ChatGPT auth, Grok Build OAuth, and the future grok.com cookie session never fall back to one another.
• Build subprocesses are constrained to configured roots and bounded by time/output limits.
• XAI_API_KEY and GROK_CODE_XAI_API_KEY are removed from the child environment.
• grok_build_agent defaults to plan/read-only behavior; apply is an explicit destructive choice and the MCP annotation remains conservative.
• Upload file opens are descriptor-relative with no-follow checks, regular-file/size/stability validation, closed error tracebacks, and caller-owned success descriptors.
• No credential values, live session IDs, raw model output, or website response bodies are committed.

Verification

• Full offline suite: 1965 passed, 11 skipped.
• Focused Build MCP/docs gate: 166 passed.
• Upload security gate: 76 passed; related Grok boundary gate: 52 passed.
• Ruff and git diff --check: passed.
• Isolated wheel and sdist builds plus package smoke: passed; installed/source manifests match exactly.
• Authorized Build live gate: CLI 0.2.101, two account models, exact sentinel true, session ID present, changed-files empty, one plan-mode dispatch.
• Independent task reviews: Build MCP, Build live gate, upload core, and Build docs all reached spec PASS and quality/security approval after fixes.

Remaining work before replacement/final PR

1. Authenticate a reviewed Chrome profile on grok.com and capture only value-free live protocol evidence.
2. Implement and independently review bounded website transport, models/modes, ordinary chat/history, Heavy reconnect, and upload integration.
3. Register the remaining website MCP tools and run separate opt-in website/Heavy gates with sanitized receipts.
4. Complete full two-stage correctness/security review.
5. After v0.0.15 is verified, replay the exact Grok commit range onto that tag, open the replacement PR to main, update coordinated metadata to v0.0.16, merge, tag, publish, and verify a clean install.

Website integration will use a private unsupported grok.com contract. Heavy evidence is quota-bearing and must be retained only as a sanitized local receipt.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: a4faf668-5814-4301-8858-e6aa36b12429

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/grok-dual-account-v0.0.16

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}