Updated 21 October 2026
Available with the right setup
| Area | Current boundary |
|---|---|
| Teams and tasks | Roles, dependencies, chat, steering, manager summaries, budgets, saved questions and answer-and-resume. Work does not continue indefinitely outside its limits. |
| Model providers | Live OpenRouter execution is verified. Other provider adapters and model combinations require configuration and compatibility testing. |
| Memory | PostgreSQL keyword retrieval and optional pgvector semantic retrieval over permitted source-linked history. No automatic customer backfill or perfect recall. |
| Knowledge handoffs | Agents can find prior contributors, request knowledge and wait for a cited answer. Direct history-tool behavior is covered by deterministic tests; the hosted model has not demonstrated every available tool. |
| Reusable skills | Exact-version owner approval, scoped reuse and manual import/export. A skill does not authorize an account, source or external action. |
| SSH work | Approved POSIX/OpenSSH discovery, bounded UTF-8 files and exact configured procedures. Encrypted credentials, pinned host identity and scoped grants. Actual transport tested on an isolated server; a customer server still needs its own approved connection and verification. |
| Coding and browser work | Configured isolated tools, filesystem operations, terminal/Git/test procedures and browser automation. Availability depends on the installed execution environment and allowed tools. |
| Schedules | Durable background jobs, bounded runs and saved waits. A schedule does not prove an external action was delivered. |
| App and social connections | Connection setup and Composio account APIs exist. Facebook, Instagram, WhatsApp, TikTok and YouTube workflows still require account-specific consent, supported tools and verified delivery. Do not assume universal automatic publishing. |
Owner review remains part of the work.
Account consent, SSH permissions, external-action approval, result acceptance and reusable-skill approval are different decisions. A model cannot approve its own access. Read sources and outputs carefully, especially before a public post, production change or high-impact decision.
Memory has a lifecycle.
Forgetting or narrowing a source blocks direct retrieval and active continuations that retain its citations. Already completed derived summaries, notes and results are separate materialized records with their own scopes; remove or revoke those separately when needed. Forgetting a knowledge item is not a promise to erase every audit or backup copy.
Budgets and failures are visible.
Model and tool calls can fail, cost money or have an unknown external outcome. A saved question may need an owner answer, renewed permission or reconciliation. Unknown mutations should not be repeated blindly.
Early-access scope
We have not established production-scale capacity, universal integration coverage, enterprise certifications or a guaranteed service level. Pricing and general availability are not announced. Ask about your intended workflow before relying on it.