Skip to main content
TOSE
VIEN

Roadmap

Roadmap and availability

What you can use on TOSE today and what is still coming. A label follows what customers can do in production, not what has been merged into the code: if a feature is built but switched off, it says Coming soon.

How to read the labels

  • Available: open to customers in production, with the limits listed.
  • Beta: open to customers with the limits listed; behaviour may still change.
  • Coming soon: not open to customers. There is no sign-up for it; the card says what has to happen first.

Inventory last checked against production on (15).

Apps and infrastructure

  • Deploy from GitHub or a Dockerfile

    Available

    Connect a repository; TOSE builds from your Dockerfile or generates one for common runtimes, then runs it on Kubernetes with a domain and SSL.

    Limits:
    linux/amd64 builds, 2 GB memory, 45-minute limit. A new deploy is refused (HTTP 402) when the wallet is empty.
    Checked on:
    Read more

  • Persistent disks

    Available

    Attach disks to projects, templates and databases; data stays when the workload is stopped.

    Limits:
    Provisioned size is billed per GiB-month even while the workload is stopped.
    Checked on:
    Read more

  • 1-click templates (GoClaw, Dewee)

    Coming soon

    GoClaw and Dewee are two ready-made templates. The deploy button appears only when the release API reports verified with a version.

    Limits:
    The release-status endpoint reported unavailable for both on 2026-11-03; none is verified yet.
    Release gate:
    A real staging run and the public release flag (tose-app#313).
    Checked on:

  • Public template directory

    Coming soon

    A discovery page for templates from many publishers, with filters and a Deploy on TOSE button.

    Limits:
    There is no /templates page yet; only GoClaw and Dewee are shown, by their real release status.
    Release gate:
    The public registry tose-app#138 and the template security gate.
    Checked on:

Agents and agent tooling

  • TOSE CLI for people and agents

    Available

    Deploy and operate from a terminal or a coding agent: --json output, --non-interactive, --dry-run, --wait, doctor and capabilities.

    Limits:
    Only commands in the published npm package. The API key is read from TOSE_API_KEY.
    Checked on:
    Read more

  • API, OpenAPI and public Skills catalogue

    Available

    An OpenAPI 3.1 description and a Skills list (JSON) readable without signing in. Public documents, not an MCP server.

    Limits:
    Read-only documents. Calling the API needs an API key in the X-API-Key header, never in a URL.
    Checked on:
    Read more

  • Scoped API keys

    Beta

    The API can create a key limited to listed scopes; a request outside them fails with insufficient_scope.

    Limits:
    The dashboard form and the CLI cannot set scopes yet; a key without scopes keeps full workspace access.
    Release gate:
    A dashboard form and a CLI command to set scopes.
    Checked on:
    Read more

  • MCP connector and OAuth for agents

    Available

    Remote MCP server at https://app.tose.sh/mcp (Streamable HTTP). Sign in to TOSE and approve the scopes with OAuth 2.1 + PKCE; no API key needed.

    Limits:
    8 tools: 6 read-only (projects, deployments, logs, incidents) and 2 mutating (deploy_project, rollback_deployment) that need write scopes. Skills are not served to MCP clients.
    Checked on:
    Read more

  • WebMCP on the website

    Coming soon

    Tools a web page offers to an agent in the browser, mostly for reading and navigation; none writes to a workspace. Different from the MCP connector and from the Skills catalogue.

    Limits:
    Needs an experimental browser flag and is switched off on this site; it exposes no workspace writes.
    Release gate:
    Enable TOSE_WEBMCP after each tool is reviewed.
    Checked on:
    MCP status

  • Cloud Desktop

    Coming soon

    A persistent Ubuntu desktop that sleeps when idle and keeps its disk, shared between a person and an agent.

    Limits:
    Switched off in production while hardening is finished. The desktop commands exist in the CLI but the service is not open.
    Release gate:
    Finish hardening (tose-app#37), then enable DESKTOP_ENABLED.
    Checked on:
    Follow the changelog

  • Managed Agent Runtime

    Coming soon

    A TOSE-managed runtime for running agents on demand, on a schedule or from hooks, with usage metered per run.

    Limits:
    Not open to customers. Not the same as Cloud Harness, a separate service that can be deployed on TOSE.
    Release gate:
    Backend epic tose-app#172 and its security checks.
    Checked on:

  • CI Harness

    Coming soon

    Isolated CI runners for agents: tests, failure diagnosis and evidence of outcomes.

    Limits:
    Not open. No speed or cost figure is published before it is measured.
    Release gate:
    Backend epic tose-app#173, benchmarks and a security sign-off.
    Checked on:

  • Browser Engine

    Coming soon

    Browser sessions, profiles and workflow replay for agents. Not the same as Cloud Desktop.

    Limits:
    Not open. No coverage or reliability claim without a reproducible benchmark.
    Release gate:
    Backend epic tose-app#145 and a verified beta.
    Checked on:

Teams and operations

  • Workspaces, permissions and a prepaid wallet

    Available

    Each workspace has its own wallet; costs are hourly for vCPU and RAM plus disk, topped up in VND or USD.

    Limits:
    No signup credit. An empty wallet suspends compute and keeps disks.
    Checked on:
    Read more

  • Automated operations

    Coming soon

    Agents that watch and handle incidents within granted permissions, with human approval.

    Limits:
    Not open. TOSE promises no self-healing or uptime until there is evidence.
    Release gate:
    Backend epic tose-app#101 and durable background loops (tose-app#146).
    Checked on:

Sources and evidence

Each entry records how it was checked. The full table of claims and their sources is kept in the site repository (docs/claims.md), and release history is in the changelog. Documentation.