Feature availability
Understand Alpha, preview, hidden, and provider-dependent surfaces.
These guides describe the current customer surfaces. A route, API schema, or older link can remain present even when its product entry point is hidden or a feature is paused. Check the state below before building a workflow around it.
| Surface | Current boundary |
|---|---|
| Tasks | Alpha; delivery status and automation follow the workspace workflow |
| Routines | Engineering execution is supported; schedules, manual runs, and GitHub triggers are available |
| Product Specs | Visible workflow for drafts, revisions, approval, and linked work |
| Product Briefs, QA, Release | Separate sidebar sections are hidden; existing record links can remain reachable |
| Loops | Customer UI is hidden; backend capabilities do not establish a supported visible tutorial |
| Repository wiki | Paused; do not depend on wiki indexing for Code Intelligence reports |
| Configured-agent sidebar | Hidden; agent settings and tabs can still be available |
| Session timeline | Depends on the serving configuration; use the available progress and activity views |
| Desktop and Android views | Depend on provider, environment, session, and device availability |
| Uno Chief in Slack | Separate connection shown only for eligible workspaces |
| Machine profile | Customer card is read-only; supported size changes are applied through Uno support |
Process settings are a UI preview
The Process pages for planning, specs, verification, testing, review, and pull requests currently preview settings in the interface. Their values are not persisted as workspace execution policy and reset on refresh.
Changing these controls does not enforce testing, review, merge, or other run behavior. Put actual requirements in the task, repository rules, and your source-control review process until persisted behavior is available.
Connection and role limits still apply
An available feature can require repository access, an enabled model, a provider connection, funding, or a particular workspace role. A connected provider does not enable every model. A preview link does not prove the app server is healthy.
Concept videos in these docs illustrate relationships and transitions. They are not recordings of verified live product behavior or evidence that a proposed feature shipped.
For an unavailable action, use connection troubleshooting, members and roles, or the feature's own guide. When reporting a mismatch, include the page and app surface so the documentation can be checked against the serving release.