Changelog
View as MarkdownAll 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.
0.4.1 (2026-11-18): security patch
Section titled “0.4.1 (2026-11-18): security patch”- 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 onuseDeviceApprovalmust render the warning and an input wired toconfirmation.setTyped; passsource: 'typed'only for a code typed on your page. - Push notifications (medium):
expoPushNotifiersends generic text with no session or approval titles unlessincludeContent: 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/clientand@uncage/reactrun in Expo / React Native (async bearer headers, native file uploads,reconnect(), storage-adapter persistence,useDeviceApproval). Authenticate apps, push notifications withonAttention+expoPushNotifier. - Browser extensions: the hub’s
trustedOrigins. - One-click connect:
uncage://links,uncage connectwith a native confirmation and site identity checks,uncage dashboard, a QR code inuncage setup. - Breaking for custom implementations:
UncageClientrequiresreconnect,lookupDevice,decideDevice;UncageStorerequiresclient; 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.
0.3.1 (2026-11-09)
Section titled “0.3.1 (2026-11-09)”@uncage/hub: importing it from a Next.js page, route handler or Server Action no longer fails with “Can’t resolve ‘ioredis’” (orpg) when those optional packages are not installed.
0.3.0 (2026-11-09): the hub runs anywhere
Section titled “0.3.0 (2026-11-09): the hub runs anywhere”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,pgliteHubStorefrom@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/hubroot 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:
createHubrequiresstore;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 carryRetry-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, nosudoor admin rights. - Browser:
<ConnectMachine>with OS tabs,<AgentOutdatedNotice>, runtime icons. - Examples:
connected-demoon Vercel or any container; newconnected-cloudflare.
0.2.0 (2026-11-08): Connected Mode
Section titled “0.2.0 (2026-11-08): Connected Mode”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 withpostgresHubStoreandredisCluster, andattachmentRetentionDays(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/corein~/Uncage/<site>/<session>, bridges tool calls, serves fenced file pulls, replicates events with backfill, enforceslocalPolicy, keeps a redacted activity log.@uncage/cli:uncage setup <url>,uncage agent(uninstall),uncage sites(remove),uncage activity, andUNCAGE_HOMEfor development.@uncage/client,@uncage/react,@uncage/react-ui:machines(),installInfo(),revokeMachine(),createSession({ machineId });useMachines();<ConnectMachine>,<ApproveDevice>,<MachineStatus>;<AgentChat>switches to Connected Mode by itself.UncageClientgains 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 anddisableSkillShellExecutionis set, so a website can never run shell through a skill). Runtimes without site tools (Codex) get skills only, with asite_tools_unsupportedwarning.@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.
0.1.1 (2026-11-07)
Section titled “0.1.1 (2026-11-07)”- Docs only: npm-first quick start in the README; every package README is self-contained.
0.1.0 (2026-11-07)
Section titled “0.1.0 (2026-11-07)”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 andallowedHosts. - 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.