# Full Web Control Center > **Opt-in 1.8.4a2 preview.** Install `connectonion==1.8.4a2` explicitly. > Stable remains 1.8.3. Final 1.8.4 and production hosting acceptance are pending. > The paired React SDK is published as `@connectonion/react@0.4.4-rc.2`. A Control Center is a complete static app beside Chat. HTML, CSS, JavaScript, framework chunks and assets travel as one immutable revision. The 1.8.4 candidate coordinates Core, the React SDK, O Chat and a separate static hosting service. Deploying that service and its wildcard TLS domain is an operator step; the CLI does not invent a working production URL. ## Start and configure `co create` copies `.co/control-center/` once. It contains `index.html`, `control-center.js`, the browser SDK `sdk.js` with its version/hash and license, and `CONTROL_CENTER.md`. The directory belongs to the author and is never overwritten by later initialization. Default `co init` initializes global credentials only. The starter includes Agent identity, a message form, published skill actions, Diagnostics and a live Recent Chat view. It uses the same browser SDK as framework apps. A plain static-server preview renders the document but has no Agent authority. Add this configuration to the Host's `.co/host.yaml` after provisioning the hosting API and a wildcard domain on a separate registrable domain from O Chat and identity services. The names below are placeholders, not available production endpoints. ```yaml control_center: app_id: home build: .co/control-center entry: index.html serving_domain: control-apps.example.net capabilities: [clipboard-write, fullscreen] updates: enabled: false every_seconds: 3600 tz: UTC events: [] ``` The upload API follows the shared backend resolver and ambient credentials; `api_url` can explicitly select another HTTPS API. Runtime state defaults to the global config directory under `runtime/control-centers/`. It must remain outside the authored project and outside the author tools' filesystem authority. This is not an operating-system sandbox for an Agent with unrestricted native tools. ## Review, activation and rollback An administrator chooses **Update app**, or asks the Agent to edit the build and call `update_control_center`. All update paths share the same operation: 1. Capture every regular build file and derive a canonical manifest/revision. 2. Run the packaged `control-center-review` skill in a fresh reviewer process. 3. Check that the source still matches, upload frozen bytes, then check again. 4. Record approval and activate only the reviewed revision on its HTTPS origin. Each account/app/revision receives its own origin, shaped like `https://r-.control-apps.example.net/index.html`. The authenticated upload API and public static ASGI app are separate services. No identity cookies or API routes belong on the serving origin. Bundle limits are 256 files, 8 MiB per file and 20 MiB total; executable review source is limited to 512 KiB. Production framework bundles must fit these bounds and the serving CSP. Review runs once with no author tools/history, a 90-second process deadline and 4,096 output-token bound. The default follows Core's current default model; `review_model` explicitly overrides it. Runtime-owned provenance binds model, execution, policy, time, cost and findings to the revision. A reported review cost above $0.25 blocks activation. These guards cannot undo provider charges. A blocked, failed or changed build keeps the previous approved app visible. O Chat shows findings, **Fix with AI**, Code/Preview, retained source/diffs and revision history. Rollback requires retained approval under the current policy and a reachable artifact. Historical source is checked against its reviewed size/hash before display. The private history retains up to 100 attempts within 4 MiB while preserving the active approval and newest attempt. Source and diff displays are separately bounded. ## Conversation and browser behavior The iframe connects through a verified window/origin/revision handshake and fresh load epoch. Its private MessagePort carries ordered normalized ChatItems, connection state, skills and current session. Gaps request a fresh snapshot. The parent bounds recent history and reports truncation. The iframe never opens an Agent socket or receives identity keys. `sendMessage` and `runSkill` create visibly attributed conversation turns. Current conversation is the default; the landing page promotes its draft on the first action. Only `conversation: 'new'` creates another Chat. Current-chat app actions must start while the Agent is idle and await completion; cancellation reaches only their pending turn. New-chat actions acknowledge the handoff. After a timeout, inspect Chat before retrying an uncertain action. Focus and fullscreen preserve the iframe. **New tab** opens an O Chat session shell, which restores the same conversation and connects its approved revision. A pinned revision mismatch is explicit. Reload creates a fresh port; stale ports cannot act. The app has native per-origin storage, fetch/XHR, WebSocket/SSE, workers, canvas, SVG, WebGL and WASM. The serving CSP allows bundled code and normal data APIs while blocking external scripts and string evaluation. Declared camera/microphone/location/ clipboard/fullscreen capabilities become iframe permissions and still require browser grants. Public assets must never contain credentials. ## Automatic updates Updates are disabled by default. Configure an interval of 60–604800 seconds or a daily HH:MM with IANA timezone, and optionally completed Agent turns, explicit skill turns or source-change events. The existing Host minute scheduler applies the same rules through direct, Relay-only and local Host configurations. Events deduplicate for seven days (up to 1,024 IDs), coalesce and debounce up to five minutes. The updater excludes its own turns and already-active source. A durable claim and OS locks allow one writer; downtime produces one due update rather than a replay burst. An interrupted process remains paused until manual retry. Ordinary failures wait for the next configured occurrence or manual action. Defaults allow 24 attempts/day (configurable 1–96) and $2 reported daily cost. Author turns have eight iterations and a five-minute/$0.50 between-call guard; an in-flight provider call can finish after the guard. Settings/status expose last attempt, success, error, next run and revision. This does not schedule mail or provider messages. See [candidate acceptance](https://github.com/openonion/connectonion/issues/1445), [DD071](https://github.com/openonion/connectonion/issues/1445), and [the legacy dashboard](https://github.com/openonion/connectonion/issues/1445). ## Published SDK candidate Install the exact `@connectonion/react@0.4.4-rc.2` dependency through the normal package manager. Its protected CI artifact and npm registry tarball have the same SHA-256: `f608a913528beeda6c3ac32072b281ad38cb4d5eadd615824fb1270e2b0d07b2`. The SDK is a prerelease for coordinated 1.8.4 acceptance; it does not mean the Core release or production hosting is available.