Surface · Cloud envs

Dark Factory
from any browser.

claude.ai/code sandbox or a GitHub Codespace. Open the devcontainer, push, and the same multi-vendor gate fires as on a laptop. Zero local setup. Same audit posture.


claude.ai/code/your-org/your-repo
$ make df-doctor
environment: cloud-sandbox · doctor: all checks pass
critic portfolio: gemini ✓ · grok ✓ · w3-hosted ✓
local subscription critics (codex / cursor): skipped (cloud)
 
$ git push origin feat/grok-direct
darkfactory: bypassing local pre-push (cloud env)
reason: AGENT_REVIEW_BYPASS (canonical)
verdict will be issued by hosted critic via branch protection
push complete · check run pending on PR #187

Cloud + laptop parity

One gate. Two paths in.

Property
Laptop
Cloud env
Local critics (Cursor, Codex)
Subscription auth
OAuth needs browser the sandbox can't reach
Local critics (Gemini, Grok)
API key
Same API key in Codespaces secret
Hosted W3 critic
Via branch protection on push
Audit posture
Canonical AGENT_REVIEW_BYPASS
Same canonical reason; same audit log
Setup friction
CLI install + hooks
Open devcontainer. Done.

Why this matters

A laptop is no longer a prerequisite.

No laptop required

Works in any browser sandbox where Claude Code runs. New hires, contractors, on-call from a Chromebook — all covered.

Zero secret distribution

Codespaces secrets are encrypted per-user. The bootstrap script ships in the repo. No "let me email you the API token" onboarding.

Identical audit posture

Cloud pushes use the canonical AGENT_REVIEW_BYPASS reason. make df-stats greps cleanly across laptop + cloud pushes.

Get Started

Adopt the gate from anywhere.

Codespaces + claude.ai/code support means every push lands in the audited gate, regardless of where the developer is.