What’s new in MIOSA. Updates ship continuously; this page is a human-readable digest grouped by week.
The MIOSA SDKs will live in dedicated public repos for each language — Miosa-osa/python-sdk, Miosa-osa/typescript-sdk, etc. Mirrored from the monorepo via a CI subtree-split workflow. Direct installs remain unchanged.
May 12 – 18, 2026
MCP server for AI coding assistants
A native MCP server ships 22 computer-use tools — screenshot, click, type, scroll, drag, key chords, window management, clipboard, cursor, launch, and more — making any MCP-capable AI coding assistant a first-class driver for MIOSA Computers. See Desktop Control →
Desktop double-click, scroll fix, and faster typing
Fixed a scroll timing regression that caused scroll-up actions to stall. Added double-click as a distinct desktop action. Improved keystroke throughput for type commands. The Go SDK now ships a full Computer type with all 13 desktop actions.
Python and TypeScript Sandbox SDKs reach full parity
All Sandbox methods — create, exec, stream, snapshot, file I/O, suspend, resume — are now available in Python (sync + async) and TypeScript. The CLI routes sandbox commands through the native API rather than a secondary proxy. See Sandbox SDK reference →
Fixed: SDK import errors and agent exports
Resolved broken module imports introduced during SDK consolidation. ExecResult field names are now consistent across Python and TypeScript. Agent stub exports are correctly registered in the package index.
May 5 – 11, 2026
Sandbox architecture: snapshot restore now live
Sandbox snapshot restore is live at ~166ms p50. The platform captures snapshots automatically on suspend and restores them on resume — no cold boot penalty on warm sandboxes. See Sandboxes →
Regions and computer embedding APIs
New GET /api/v1/regions endpoint returns the current compute region list with capacity metadata. The embed API now returns a scoped, short-lived token for embedding a computer’s desktop into your own UI — no iframe proxy required. See Embedding →
Production deploy pipeline hardened
The sandbox-to-deployment pipeline (source snapshot → builder → release → runtime instance) is fully wired in production. Build logs stream in real time. Static sites land on the edge; dynamic apps boot as runtime instances. See Deploy overview →
Unified SDKs replace standalone sandbox package
The standalone sandbox SDK package is deprecated. All sandbox functionality is available under the unified language SDKs (miosa for Python, @miosa/sdk for TypeScript, and equivalents in Go, Java, Elixir). Migration is a single import change; the API surface is identical.
Removed
- The separate sandbox CLI path is removed; all CLI sandbox commands route through the main API.
- Legacy agent endpoints (
/computers/:id/cua/*,/computers/:id/agent/*) now return410 Gone. Use desktop primitives directly or the MCP server.
Apr 28 – May 4, 2026
CLI: public install via Homebrew
The MIOSA CLI is now installable via Homebrew:
brew install miosa-dev/tap/msk The CLI supports msk computers, msk sandboxes, msk deploy, and msk auth. A device-flow OAuth login ties the CLI to your workspace in one browser step. See CLI reference →
Account security pages
New security section in account settings: active sessions, passkey management, two-factor setup, and connected OAuth providers. Sessions can be revoked individually.
Admin: email campaign composer
Platform operators can now compose and send targeted email campaigns to workspace segments directly from the admin console.
Improved: AI engine token tracking
Token usage from the AI engine is now tracked per-computer and surfaced in the usage API. Metered usage accumulates in real time against the workspace’s billing period. See Usage and Billing →
Improved: frontend workspace tabs and GPU pricing
Workspace settings tabs now persist the active tab across navigation. GPU tier pricing is correctly reflected on the computer create form and the pricing page.
Improved: admin observability and intelligence gateway
Admin dashboard surfaces per-tenant active computer count, sandbox throughput, and deploy queue depth. The intelligence gateway proxy correctly handles streaming responses under load.
Apr 21 – 27, 2026
Computer tab scrolling fixed
Long-running computers with many open tabs (terminal, preview, files, etc.) now scroll the tab strip horizontally rather than overflowing off-screen.
Computer create: services panel
The computer create flow now includes a services panel for attaching data services (Postgres, Redis, object storage) at creation time. Environment variables are injected automatically.
Environment variable persistence
Environment variables set on a computer or sandbox are persisted across stop/start cycles. Variables set via API are visible in the in-computer terminal immediately.
Warm pool admin controls
Platform operators can configure warm pool size, pre-warm image targets, and drain schedules from the admin console.
Apr 14 – 20, 2026
OpenComputers resources across all five SDKs
Hosts, jobs, files, tunnels, and inference cluster resources are now available in all five SDKs (Python, TypeScript, Go, Elixir, Java). Async variants included in Python. See SDK references →
SDK surface expansion
Ten new resource namespaces added: Sandboxes, Deployments, Versions, Releases, Runtime Instances, Domains, Data Services (Postgres, Redis, Storage), Network Policy, and Credits. Coverage tables are on each SDK page.
envd: network tunnels
The in-computer daemon now supports exposing internal services as tunnels — useful for previewing dev servers running inside a computer from outside the VM boundary. See Previews →
Mar 31 – Apr 13, 2026
Deployments API
The Deployments API is in production: POST /api/v1/sandboxes/:id/deploy publishes a sandbox, GET /api/v1/deployments lists deployment history, and POST /api/v1/deployments/:id/rollback re-points the active version. All operations are available in the SDK and dashboard. See Deploy →
Sandbox, Deploy, and Intelligence dashboards
The dashboard ships three new top-level sections: Sandboxes (live usage, snapshot list), Deploy (deployment history, build logs, rollback), and Intelligence (AI engine usage, cost trends).
API drift CI gate
A new CI check compares the server’s declared API surface against all five SDK clients on every pull request. Contract mismatches — missing endpoints, changed field names, type drift — fail the build before they reach production.
Docs site launched
The MIOSA docs site launched with the unified API key format (msk_*), Mermaid diagram rendering, six-language SDK tabs, and full-text search.
Mar 2 – 29, 2026
Compute platform in production
The compute engine and platform API are deployed to production. The provisioning flow is hardened with retry logic, crash guards, and correct error propagation. OAuth state mismatch now redirects to login rather than surfacing a raw error.
Computer rename complete
“Instance” is renamed to “Computer” across the API, dashboard, SDKs, and documentation. Existing API clients using /instances/* continue to work via redirect; new code should use /computers/*. See Computers →
Computer: /enter endpoint
POST /api/v1/computers/:id/enter returns a scoped session token for direct desktop access. Used by the embed flow and the CLI msk computers enter command.
26 app templates with tier system
The computer create flow ships 26 starting templates (landing page, SaaS scaffold, data dashboard, agent workspace, and more) organized by tier: free, pro, and enterprise. The template picker is a split-panel modal with live previews.
Security hardening
Sixteen security fixes: secret redaction from configure responses, XSS prevention on user-controlled fields, timer leak fixes, provisioning crash guard, and tenant slug collision prevention. Internal auth tokens are no longer included in API responses to unprivileged callers.
Command Center
The Command Center UI is live — manage AI agent sessions across computers, track cost by session, and view real-time agent status. Backend scheduling and cost accounting routes are wired.
Feb 2 – Mar 1, 2026
Platform foundation shipped
Stripe billing, audit logging, email notifications, promo codes, and OAuth providers are in production. Redis session persistence ensures computer state survives backend restarts.
Go backend fully retired
The last Go backend service is archived. The entire stack now runs on Elixir. Dead proxy code and legacy stubs are removed.
Documentation architecture
Internal technical documentation organized across all five service packages (703 files), covering architecture decisions, API contracts, deployment procedures, and runbooks.
Jan 5 – Feb 1, 2026
Platform foundation
Auth, billing groundwork, and initial security audit complete. 81 known issues triaged; 27 legacy backend issues closed.