# Release roadmap

> What works today, what comes next, and how we know it is ready.

## Available in the beta

Orbit gives your agent workflows a shared home for structured context. Each account includes three workspaces and up to 20 active agents, with no paid plans or invitation flow.

- Separate workspaces for different businesses, with workspace-specific records, tags, custom fields and relationships.
- Email registration, verification and recovery, plus GitHub, Google and Microsoft sign-in when available.
- OAuth connections for ChatGPT and Claude, with workspace approval, PKCE and refreshing credentials. Live client acceptance remains pending.
- Agent tokens with selected, current or future workspace access and reader or contributor permissions.
- Contacts, organisations, projects, affiliations and project participants.
- Name, email and phone search, reusable tags, typed custom-field values and structured briefs.
- Sourced activity, linked tasks, assignments, expiring claims and outcome-backed completion.
- Revision checks, safe mutation retries, attribution and archive/restore.
- A read-only record directory with JSON and Markdown views and authenticated record endpoints.
- Account settings, linked sign-in providers, browser-session controls, workspace exports and deletion requests.

The public documentation, Markdown guides and LLM exports use the same source. The homepage’s interactive examples are fictional illustrations, not live customer data or prebuilt automations.

## Current limitations

Custom-field definitions and exceptional activity redaction require the service operator. Agents can discover and use existing fields, but self-service field definition management is not available yet.

Record editing happens through MCP. The browser interface is for viewing records and managing your account and connections. Workspace member invitations, automatic export import, Orbit-managed MFA are not implemented. Browser social sign-in is separate from agent authentication.

Account deletion disables access immediately; the service operator completes removal. See [Your data & exports](/docs/administration).

## What still needs validation

The implementation has automated coverage for permissions, workspace isolation, record operations and concurrent task claims. End-to-end journeys with real agents, multi-agent handoffs, sustained shared use and production recovery still need live acceptance verification. Automated tests alone do not establish production readiness.

## What Orbit does not run

Orbit stores context and coordinates task claims. It does not run an LLM or workflow engine, wake agents when tasks become due, send email, make calls or provide native calendar integrations. Your agent and automation platform perform those actions under their own permissions.

Billing, paid plans and a full CRM editing dashboard are outside the current beta. Future additions will be documented here as they become available.