CritiqueCode Hosted Runtime: An Early, Truthful Release
An early hosted CritiqueCode runtime with explicit configuration gates, durable branches, and a clear supported-capability boundary.
Early hosted runtime
Capabilities before promises.
critique.sh
The hosted /code experience is an early implementation, not a production launch claim. It gives a CritiqueCode author session an E2B sandbox, Git branch, ordered history, and pull-request path only when the deployment reports the required capabilities as available.
The browser controls a hosted session. It does not connect to your personal computer. The server reports which model providers, attachment storage, sandbox policy, and native review features can actually run, and the interface only offers those operations.
What works in the early runtime
| Capability | Current contract | |
|---|---|---|
| Bootstrap | Idempotent request | One recorded branch and sandbox operation, with partial-failure compensation |
| Authoring | Prompt and inspect | Ordered activity, bounded replay, files, diffs, and reconnect state |
| Publish | Checkpoint, PR, merge | Expected-head protection and explicit GitHub operations |
| Attachments | Validated images | Available only with configured private object storage |
Provider secrets stay in the control plane. The sandbox uses a session-scoped model gateway capability. Production session creation fails closed when the required egress policy is missing; image attachments stay disabled until private storage is configured.
What is not available yet
The terminal is an early hosted PTY. Its output and input are ordered and reconnect-aware, but we do not describe it as a direct browser-to-sandbox terminal until the full connection, flow-control, and recovery contract is verified in production.
Session history is durable within documented retention and replay bounds. An in-flight operation may be reconciled or safely failed according to its operation contract. Arbitrary side effects are not promised to resume after a process dies.
Configuration is part of the product
A model in a static catalog is not an available model. An upload button is not private storage. A green status is not a healthy worker. If E2B, a usable model route, or the production sandbox policy is missing, the page explains the exact missing capability and does not start a session. Missing private storage disables images without blocking text-only work.
One session, one branch, one sandbox
The control plane resolves the base commit, records an idempotent bootstrap operation, creates the session branch, and starts the pinned sandbox template. GitHub is the durable code boundary. The session store is the ordered control record. E2B is the isolated execution boundary. Readiness comes from the worker.
Flow
1. Sign in to Critique
2. Open /code
3. Check deployment capabilities
4. Choose a repository and base branch
5. Describe the changeThe capability notice tells you whether this deployment can start a truthful session.