Changelog

Leaner codebase and sandbox lifecycle fixes

An Alpha release focused on repository simplification and sandbox operations.

Improvements and fixes

• Remove dead code, retired Pet/Cattle and App Deployment paths, per-turn budget residue, duplicate validation, and unmeasured caches and retries. Product and engineering documentation is consolidated.
• Bound container lifetime and capacity failures, and extend operational monitoring to every sandbox container application.
• Public Thread API v1/v2 wire contracts remain unchanged. This release adds no D1 migration or database DDL; the production schema remains at migration 0018.

CLI compatibility

The internal console GraphQL schema removes operations and fields selected by older CLI builds, including startAgentRun, sessionMessages, controlPlaneOverview, organizationBillingCostCard, and createEnvironmentFork. CLI builds consuming these fields require a regenerated contract and matching release. The versioned public Thread API is unaffected.

Release verification

The release notes record a production deployment at dadfb757b2, with API and Web Workers redeployed, all five sandbox images rebuilt, and the maintenance cron verified. Targeted staging acceptance covered the OpenAI, OpenCode, Pi, and DeepSeek paths, direct v2 Sessions, usage, idempotency, cancellation, and model-availability admission.

Version numbering

The preceding Host release was corrected from v0.6.0 to v0.5.1, while its original Git tag was retained. This explains the gap in the published release list; v0.6.0 is not a missing intermediate feature release.

Full notes: v0.7.0 on GitHub.

Provider-aware model protocols

A patch release that adds explicit provider protocols across Pi and the other harness runtimes.

Improvements

• Pi can use catalog models and custom OpenAI Chat Completions, OpenAI Responses, Anthropic Messages, and Google Gemini endpoints.
• OpenCode selects the matching provider adapter. Codex remains Responses-only; Claude SDK retains its Anthropic model allowlist.
• The console and CLI expose an explicit protocol for custom credentials. Incompatible provider, model, and runtime combinations are rejected before a Run; new Sessions freeze their protocol for continuation.
• Existing credentials without a selected protocol retain their legacy behavior. Companion CLI v0.6.0 includes the matching contract and --input-model-protocol option.

Compatibility and verification

• D1 migration 0018 adds a nullable column. The Driver and runtime images are unchanged. Preserve the column on rollback; Sessions using an explicit new protocol must not return to the old Chat-only Pi implementation.
• Staging acceptance covered real tools and file round trips through OpenRouter for Pi/OpenCode Chat, Responses, and Messages, Codex Responses, and Claude SDK Messages. Pi preserved native context and files after Driver restart and full cold-container recreation. Google-native support has deterministic local protocol/tool coverage, not hosted native-provider certification.

Version numbering

This Host release was initially published as v0.6.0 and corrected to v0.5.1. The original v0.6.0 Git tag remains at the same source commit for traceability; it does not represent an additional Host release. CLI v0.6.0 retains its independent version number.

Full notes: v0.5.1 on GitHub.

Pi runtime for durable Sessions

Pi joins the selectable runtimes for durable Project Sessions, with a companion Mosoo CLI v0.5.0 release.

Highlights

• Select Pi in the Agent editor with a custom model, or use harness: "pi" and provider: "openai-compatible" in an inline execution configuration. Custom providers continue to default to OpenCode until Pi is explicitly selected.
• Native Pi RPC execution supports streamed text, thinking and tool events, cancellation, usage reporting, workspace files, Skills, and the remote MCP proxy. Native Session state is checkpointed with the workspace for continuation.
• Completed tool arguments and tool-to-message associations are preserved, including for commands with no output. Missing or mismatched continuation state fails explicitly.
• Provider keys stay in the control plane; Pi receives a model-scoped proxy grant. Mosoo Health includes Pi and reports Unknown when no production sample has been observed.

Fixes and compatibility

• Development login is restricted to loopback origins. MCP OAuth endpoints require HTTPS and reject embedded credentials and fragments.
• This release starts with custom HTTPS endpoints supporting Chat Completions streaming and tool calls. Input is text; files are available through the Session workspace. Execution has full access within its sandbox; per-tool restrictions and interactive approvals are not supported.
• The matched Driver includes Pi 0.99.2 and retains protocol 6. The API adds the SandboxPi binding and an additive Durable Object migration; no new D1 SQL migration is added since v0.4.0.
• At release, production uses the union image, with the dedicated Pi image deployed and ready. Upgrade and rollback must preserve compatible Session state, sandbox bindings, and a matched Driver.

Staging acceptance verified real tools, file round trips, and continuation after Driver restart with a DeepSeek custom endpoint. See the Pi runtime guide and the production runbook.

Full notes: v0.5.0 on GitHub.

Direct, durable Project Sessions

An Alpha minor release centered on direct, durable Project Sessions.

Highlights

• The v2 API accepts a Project key and inline runtime, provider, model, and instructions, or an optional saved Agent preset. Upload files, start work, and continue through one stable Session ID without first publishing an Agent. Existing v1 routes retain their published-Agent and end-user identity contract.
• Each new Session owns an isolated environment and freezes its admitted configuration and native identity. Formal/API Sessions have no recurring inactivity deadline; explicitly enrolled Cloud debug Previews use a separate 30-day policy. Active Pet/Cattle choices and the shared Agent terminal are retired.
• Successful Runs require committed checkpoints. Recovery preserves checkpoints, retries accepted receipts and Driver finalization, and repairs terminal events. Provider capability rejections, ACP content refusals, and Run failures have clearer diagnostics.
• Runtime-specific images and bounded cold-start recovery are available. Preview reconnects no longer wake idle execution merely to observe it.
• Skill snapshots use bounded statements within one atomic batch, fixing startup failures with 25 Skills. Unsupported built-in tool restrictions are rejected before admission.

Compatibility and upgrade notes

• Removed Pet/Cattle fields and the shared Agent terminal require integration updates. The v1 adapter retains historical Session labels.
• Driver protocol 6 requires a matched API and Driver rollout with an admission barrier and drained existing connections.
• D1 migrations 0015–0017 are appended. Migration 0017 rewrites association columns and rebuilds the derived daily usage rollup; it requires explicit production approval, a verified backup/restore, and a compatible rollback plan.
• Existing shared Sessions require the documented conversion procedure. Preserve Session identity, history, files, frozen configuration, native continuation, and sandbox namespace bindings. An Agent-required build is not a valid rollback target after admitting direct Sessions.

Follow the production runbook and Session isolation transition before upgrading. Publishing this source release did not itself deploy production or apply migrations.

Full notes: v0.4.0 on GitHub.

Console review pass and two-family typography

A patch release focused on the web console. There are no API, runtime, Driver, or database changes.

Improvements

• The sidebar opens with one identity row: the brand tile, the active Project name, and a chevron on the header line. In the icon rail the tile alone switches Projects. The account card at the foot is the sidebar's one bordered surface, group labels are sentence case, and the divider above the persistent zone is gone.
• The console ships two font families, Geist and Geist Mono, instead of five. Each page now fetches 100 KB of fonts in two files instead of 457 KB in four, a metric-matched local fallback prevents reflow during the swap, and CJK text uses the platform sans.
• Surface tokens follow the owner's rules: a 6 / 4 / 2 px radius ladder, flat resting surfaces, 24 px information cards, text tones as alphas of the ink with AA contrast in both themes, and tracking that scales with size. The Overview moves onto the shared page header.
• Gates for all of the above: a boundary test that fails on a third font family, a resting shadow in a shared recipe, a radius past 6 px, or tracked-capital group labels, plus browser cases that measure the sidebar, the design contract, and the fonts each page fetches.

Fixes

• The Agents list drops the per-row ID chip and reads "Published" / "Draft" in every locale instead of a raw translation key.
• The Files toolbar sits on one row, and its Agent and Thread filters are only disabled when their options fail to load.
• Skills and Providers state their status in words instead of coloured lights.

Full notes: v0.3.1 on GitHub.

Projects replace Apps, project-scoped API keys, and a refreshed console

A minor release that moves the product boundary from Apps to Projects, introduces project-scoped application API keys, and refreshes the console experience.

Highlights

• Projects are the primary organizational boundary, with project-scoped application API keys and Run key attribution.
• The console gains a clearer sidebar hierarchy, a black "Create agent" call to action, an original glyph family for the resource rows, and the console design contract with its shared recipes.
• Runtime fixes address stranded pets after Driver loss, OpenCode provider and model routing, and transient Driver acknowledgement timeouts.

Breaking changes and upgrade notes

• App terminology and related API and schema boundaries are renamed to Project. Review integrations that use the previous App boundary before upgrading.
• Application API key management is now project-scoped. Review key provisioning and project access in existing integrations.
• The former App Deployment functionality and the Channels subsystem are removed.
• D1 migrations 0012 through 0014 are added: App-to-Project renames and index updates, project API key association, and Run key attribution. The rename migration retains retired channel tables rather than dropping them.
• Apply migrations only through the documented deployment process, with backup and recovery planning. Schema renames mean that rolling back application code alone must not be assumed safe.

Full notes: v0.3.0 on GitHub.

Durable Thread continuation and Driver protocol v2

A patch release focused on durable Task Agent Thread continuation, Driver protocol v2 compatibility, and runtime performance and reliability.

Improvements

• Task Agent cold continuation preserves the complete Thread workspace checkpoint, restoring continuation artifacts and history. Follow-ups may return a retryable 409 while checkpointing is pending.
• Driver protocol v2 is adopted across the API and Driver compatibility paths, switched atomically at deploy time, with V2 OpenAI and attachment compatibility updates in the Driver.
• Session event virtualization is faster, session attachment validation is batched, thread lookups by id and runtime catalog lookups are indexed, and idle gaps are excluded from process durations.
• Long-running containers raise an operations alert, and the deployment-scoped identity replaces App Secrets.

Fixes

• The agent list scrolls inside the app shell, the MCP disable / enable menu item has its icon, and single-brace i18n placeholders are guarded by a test.
• Terminal event reconciliation lookups are indexed.

Compatibility notes

• Append-only D1 migrations 0009 through 0011 are added. No established migration is modified, and there is no destructive or data-rewrite migration.

Full notes: v0.2.3 on GitHub.

Public Thread API contract safety and runtime recovery

A patch release focused on Public Thread API contract safety and production runtime reliability. It contains no D1 migration and no data rewrite.

Fixes

• Public Thread API v1 stays backward compatible: the generated OpenAPI artifact and the release gate now enforce that contract, and the contract check fetches main before comparing.
• Cattle sessions are reclaimed after remote cleanup errors.
• Activation attribution in analytics is corrected.
• The deploy workflow matches Cloudflare's HTTPS redirect status.

Full notes: v0.2.2 on GitHub.

Console localization, durable tool identity, and sandbox limits

A patch release focused on runtime reliability, Public API event identity, console localization, and deployment safety.

Improvements

• The web console is localized, with English, Japanese, Simplified Chinese, and Traditional Chinese.
• Public API events expose durable tool call identity, and streamed tool identity is stable across reconnects.
• The console publishes OAuth protected resource metadata and personal access token agent auth metadata, with a declared PAT scope model.
• Sandbox usage metrics are tracked, pet checkpoint metadata is batched, and Environment package writes support npm and pip.
• App secrets persist across redeploys, and MCP sidecars round-trip through agent packages.

Fixes

• Terminal Run projections are repaired atomically, legacy pet idle deadlines are re-armed, and the login load's critical path is shorter.
• Concurrent sandboxes are capped per account, and the free-tier sandbox quota no longer hard-rejects work.
• Thread translation variables interpolate correctly.

Compatibility notes

• Public Thread creation requires a non-empty userId.
• Legacy Environment package manager values remain readable but must be migrated before revision writes.
• Append-only D1 migrations 0005 through 0008 are added, with no destructive or data-rewrite migration.

Full notes: v0.2.1 on GitHub.

Files, Skills, Environments, and a hardened runtime

The second alpha release of the open-source agent runtime and control plane for coding agents. Mosoo is now centred on the coding-agent runtime and the Agent API.

Highlights

• Files and Skills: Agent and Thread filtering, in-console file previews, linked output artifact previews, local Skill folder upload, and skills.sh catalog installation make generated work easier to inspect and reuse.
• Environments and providers: pinned npm and PyPI packages can be prepared as reusable Environment artifacts, and custom OpenAI-compatible Responses providers run through the OpenAI Runtime.
• Sessions: live reasoning, optimistic sends, paced streaming, stable user messages, complete final snapshots, and clearer failure details make long-running Agent work easier to follow.
• Runtime and API reliability: bound Agent calls are idempotent, Run provenance is recorded, Run admission is atomic, and the queue, resume, and terminal recovery paths are more robust.
• Security: Limited Task sandboxes use deny-by-default egress controls, while managed provider credentials stay outside containers.
• Usage integrity: usage records are persisted atomically, retained when token counts are unavailable, and protected against duplicate detail rollups.
• Operations: session prewarming, larger production Sandbox instances, deep health probes, a runtime canary policy, and the cloud.mosoo.ai console domain.

Compatibility notes

• Four new append-only migration files, including one idempotent Sandbox status data migration.
• The Docker self-hosting deployment explored during this cycle was reverted before release and is not part of v0.2.0.

Full notes: v0.2.0 on GitHub.

The first alpha of Mosoo

The first alpha release of the open-source, cloud-native platform for turning AI app ideas into live agent apps.

Highlights

• Build, run, and publish agents through the web console, the public API, and a coding-agent-friendly CLI.
• Run Codex, Claude Code, OpenCode, and other agent harnesses inside isolated sandboxes.
• Manage providers, models, skills, MCP servers, files, runs, and usage costs from one place.
• A refreshed runtime catalog with GPT-5.6 preview and Claude 5 series models, model-aware advanced settings, and pricing metadata.
• Operates on Cloudflare Workers, D1, and R2 with guarded production migration and deployment paths.

Full notes: v0.1.0 on GitHub.