Skip to content

All public @uncage/* packages share one version. The authoritative record is CHANGELOG.md in the repository (and each package’s changelog on npm), written by Changesets at release time.

  • Device-approval phishing (high): a /device?code= link sent by someone else could link their computer to your account. The approve screen (<ApproveDevice>, useDeviceApproval) now warns, shows the request time and IP, and enables Approve only after the user types the code’s last 4 characters. Hub store migration 10 records the requesting IP. Custom approve screens built on useDeviceApproval must render the warning and an input wired to confirmation.setTyped; pass source: 'typed' only for a code typed on your page.
  • Push notifications (medium): expoPushNotifier sends generic text with no session or approval titles unless includeContent: true.

0.4.0 (2026-11-10): React Native, browser extensions, one agent for every site

Section titled “0.4.0 (2026-11-10): React Native, browser extensions, one agent for every site”
  • React Native apps: @uncage/client and @uncage/react run in Expo / React Native (async bearer headers, native file uploads, reconnect(), storage-adapter persistence, useDeviceApproval). Authenticate apps, push notifications with onAttention + expoPushNotifier.
  • Browser extensions: the hub’s trustedOrigins.
  • One-click connect: uncage:// links, uncage connect with a native confirmation and site identity checks, uncage dashboard, a QR code in uncage setup.
  • Breaking for custom implementations: UncageClient requires reconnect, lookupDevice, decideDevice; UncageStore requires client; session restore is asynchronous.
  • Device features (Expo Go, Android push, app links) await confirmation on a real device; iOS links and push are not verified on a device.
  • @uncage/hub: importing it from a Next.js page, route handler or Server Action no longer fails with “Can’t resolve ‘ioredis’” (or pg) when those optional packages are not installed.

Breaking changes with before/after code: Migrate from 0.2.

  • Two deployment modes (choose one): traditional mode on a long-lived Node server (toNodeHandler, attachWebSocket, pgliteHubStore from @uncage/hub/node) and FaaS mode on Vercel, Cloudflare Workers and other Fetch platforms (toNextHandlers, fetchOnce, hub.fetch) with only Postgres (postgresHubStore + postgresCluster). The @uncage/hub root entry is Web-standard.
  • Connected protocol 2: computers connect over WebSocket or HTTPS streaming (durable outbox, cursor acks, de-duplication); browser event streams rotate and resume without gaps; site tool calls survive dropped connections.
  • Breaking: createHub requires store; hub.handler → hub.fetch; hub.attach → attachWebSocket; hub.close() never closes your store; agents must be 0.3 or newer.
  • New hub options: transports, stream.maxDurationMs, polling, maintenance, bodyTimeoutMs (idle timeout), logger (console by default), toolDrainMs, installScript, rateLimits.agentAuthFailuresPerMinute; hub.maintain(). Rate limits are counted in the store (fixed windows: a burst across a boundary can reach twice the limit); 429 responses carry Retry-After.
  • @uncage/runtime-acp (new): any ACP agent, auto-detected from the official ACP registry with official icons, run only with the user’s consent.
  • One-command installer for macOS, Linux and Windows with [Y/n] prompts, Node.js 22 through the user’s own version manager, no sudo or admin rights.
  • Browser: <ConnectMachine> with OS tabs, <AgentOutdatedNotice>, runtime icons.
  • Examples: connected-demo on Vercel or any container; new connected-cloudflare.

Connected Mode arrived in 0.2:

  • @uncage/hub (new): the hub for your website’s Node backend. Device login for the CLI, machine WebSockets, the browser API (same shapes as the daemon’s /v1), site tools (defineTool, executed on the node holding the computer’s connection, as the session owner, zod-validated, 120 s timeout, audited), the file channel (ctx.files.pull / read), skills, selectManifest, sessionStorage: 'site' replication, multi-node support with postgresHubStore and redisCluster, and attachmentRetentionDays (default 30) for the hub’s attachment copies.
  • @uncage/agent (new): the daemon on the user’s computer. Dials out to one or more hubs (backoff 1 s → 30 s), runs sessions through @uncage/core in ~/Uncage/<site>/<session>, bridges tool calls, serves fenced file pulls, replicates events with backfill, enforces localPolicy, keeps a redacted activity log.
  • @uncage/cli: uncage setup <url>, uncage agent (uninstall), uncage sites (remove), uncage activity, and UNCAGE_HOME for development.
  • @uncage/client, @uncage/react, @uncage/react-ui: machines(), installInfo(), revokeMachine(), createSession({ machineId }); useMachines(); <ConnectMachine>, <ApproveDevice>, <MachineStatus>; <AgentChat> switches to Connected Mode by itself. UncageClient gains three required methods: custom client implementations must add them.
  • @uncage/runtime-claude: site tools as an in-process MCP server (mcp__site__<name>), confirmation tools that always ask, skills written to .claude/skills (inline shell in skill markdown is neutralized and disableSkillShellExecution is set, so a website can never run shell through a skill). Runtimes without site tools (Codex) get skills only, with a site_tools_unsupported warning.
  • @uncage/protocol: the connected wire protocol (version 1), Session.machineId, new error codes (machine_offline, machine_not_found, upgrade_required, tool_failed, device_code_expired, rate_limited).
  • examples/connected-demo: the reference website, tested end to end (mock, two nodes with Redis and Postgres, and live with real Claude Code).
  • Local Mode is unchanged.
  • Docs only: npm-first quick start in the README; every package README is self-contained.

First public release.

  • Local daemon (uncage serve) with sessions, runs, events and approvals over HTTP + SSE, PGlite persistence, resumable event replay, approval TTL and single-winner decisions.
  • Same-origin proxy for Next.js (createUncageHandler) with Host / Origin checks and allowedHosts.
  • Runtimes: Claude Code via the official Agent SDK (verified live); Codex App Server adapter (verified against a fake app-server only).
  • Claude Code–style composer: per-session model, reasoning effort, permission modes (bypass only when the server enables it), image and file attachments, browser voice input, running-sessions chip.
  • React: headless hooks (@uncage/react) and a default chat UI (@uncage/react-ui, en / zh-CN).
  • CLI: uncage serve, uncage doctor, event export with redaction.