Runs and workflows open on an overview
Schedules belong to Workflows
Recurring work now runs only as a scheduled Workflow. The standalone schedules API, along with its SDK methods, CLI commands and MCP tools, is gone, and so are the per-Workflow schedule reads under /v1/workflows/{workflowId}/schedules. A Workflow's schedules are now its schedule triggers, which you manage from the Workflow's Triggers card.
Workflow runs have a Graph view
Workflow run pages gain a Graph tab that draws the run's tasks as a dependency graph. Parent tasks frame their subtasks, nodes and edges are colored by status, and edges into a running task animate. Selecting a node shows that task's details beside the graph. Narrow screens fall back to the task list.
Mobile links open supported pages in the app
Links to pages the mobile app supports open there, while other product links open in the browser instead of landing on the mobile home screen.
Explore every settings page in the demo
The demo opens all team and factory settings pages, including members, billing, permissions, and API key editors. Each page shows sample data so you can explore settings without signing in.
Stale approvals clear automatically
Approvals left behind by an ended chat turn are now closed automatically, so Activity no longer stays stuck on work that cannot continue. Recent approvals from a normally waiting chat remain available for you to answer.
The assistant reacts to your messages in Telegram
The assistant in Telegram now adds an emoji reaction to your message when one fits, such as for thanks, good news, or a request it is starting on, alongside its reply. In iMessage it also reacts more readily.
Mark a message unread in the mobile app
Long-pressing a message in a chat now offers Mark unread, which moves your unread line back to that message so you can return to it later.
Checkbox approvals load reliably
Chats with checkbox approval requests open correctly, so you can choose options and continue the conversation.
One reply to the first message in a new group
The first message to the assistant in a new Telegram or iMessage group now gets a single reply. The "Connected" note no longer comes before the answer. It still appears when the assistant stays out of the conversation, so the group knows the assistant joined and how to get a reply.
See subscription allocation support
Connected subscriptions show whether app-specific usage limits are available. Eligible ChatGPT connections link to ChatGPT settings to manage usage, while unsupported connections explain why allocation limits are unavailable. Confirmed ChatGPT usage caps stop requests with recovery guidance, and refreshed permissions keep allocation availability accurate.
Run updates in chat arrive as one message
When you start a Run from iMessage or Telegram, the assistant now posts a single message when it finishes, with one link to the Run, instead of separate queued, started, and finished messages that each carried two links.
Trace steps show their cost
Each step in the chat sidebar trace shows its estimated cost, and the trace list and detail footer show the total.
Model logos on the usage chart and run pages
The usage chart and run pages now show each model's provider logo beside its name, so you can tell at a glance which model served your spend and runs.
Usage view keeps long names readable
The run usage view now shows long assistant goal titles without broken characters, and hovering an abbreviated title reveals the full name.
API operations, CLI commands and MCP tools share one naming scheme
Every Developer API operation now follows the same rules, and its SDK method, CLI command and MCP tool are derived from it:
- Verbs:
create,get,list,updateanddeletefor standard reads and writes, and a named action such aspublish,startorinstantiatefor everything else. updateis alwaysPATCH.deletealways targets a resource id in the path.- CLI commands and MCP tools use the same path:
<domain> [resource] <verb>. For example,projects members listis the MCP toolprojects.members.list, andprojects getisprojects.get.
Renamed operations:
| Before | After |
|---|---|
addProjectMember |
createProjectMember |
removeProjectMember |
deleteProjectMember |
changeNativeBillingSubscriptionPlan |
updateNativeBillingSubscriptionPlan |
getTeamMembers |
listTeamMembers |
getWorkflowTaskHistory |
listWorkflowTasks |
computeLifecycle |
controlComputeLifecycle |
HTTP changes:
| Operation | Before | After |
|---|---|---|
updateNativeBillingSubscriptionPlan |
PUT /v1/billing/subscription |
PATCH /v1/billing/subscription |
startWorkflow |
POST /v1/workflows/{workflowId}/control |
POST /v1/workflows/{workflowId}/start |
deleteBillingUsageAlert |
DELETE /v1/billing/alerts?id=... |
DELETE /v1/billing/alerts/{id} |
deleteBillingSpendLimit |
DELETE /v1/billing/spend-limits?id=... |
DELETE /v1/billing/spend-limits/{id} |
CLI commands no longer repeat the domain in the resource name: project get is now projects get, and health get is now system health get.
Collections use one plural noun for every verb, so projects members delete matches projects members list:
| Before | After |
|---|---|
projects member create / delete |
projects members create / delete |
projects agent-invocation get / cancel |
projects agent-invocations get / cancel |
runs attempt cancel / steer |
runs attempts cancel / steer |
billing auto-top-up upsert |
billing auto-top-ups upsert |
billing invoice get |
billing invoices get |
billing spend-limit upsert / delete |
billing spend-limits upsert / delete |
billing usage-alert upsert / delete |
billing usage-alerts upsert / delete |
workflows run get / control |
workflows runs get / control |
workflows revision publish |
workflows revisions publish |
workflows control get |
workflows controls get |
workflows prompt create |
workflows prompts create |
workflows trigger-source invoke |
workflows trigger-sources invoke |
workflows first-party-workflow-template instantiate |
workflows first-party-workflow-templates instantiate |
Single resources such as billing native-billing-subscription get and billing credit-balance get keep their singular names.
Long chats compact automatically
Long conversations now shorten older context automatically when needed, so you can keep working in the same chat instead of starting over when it approaches the selected model's limit.
Pin a Floor row to the top
Floor rows now offer a Pin to top action that moves the project to the top of your list, and an Unpin action that takes it back out.
Run pages open on an overview
Run pages are split into Overview, Activity, Execution, and Usage tabs. The Overview shows the goal and outputs beside a compact attempts list, run context, and the workflow the run belongs to. Assistant traces for the selected attempt now live on the Activity tab. A run that is part of a workflow run also gets a Workflow tab in its sidebar that lists the workflow's tasks with their status, marks the task this run executes, and links back to the workflow run.
Factory KPIs fit what the factory does
Factory settings now have a Suggest KPIs button that drafts up to three KPIs matching the factory's kind of work, such as issues triaged for an engineering factory or leads found for a sales factory, each with a target you can edit before saving. A factory created from a template starts with that template's KPIs and weekly targets, and the assistant can suggest and update a factory's KPIs when you ask in chat.
Floor rows show the whole factory name
Long factory names on the mobile Floor now wrap instead of being cut off, and the list stays smooth on teams with many factories.
Workflow pages open on an overview
Workflow pages put Run now, Pause, and Settings in the header beside a health line showing the last run and how many recent runs succeeded. Content is split into Overview, Runs, Triggers, and Permissions tabs. The Overview draws the plan as a graph colored by the latest run, and selecting a step opens that run's graph on the step. Recent runs and the latest run sit beside it, with definition details tucked into a collapsible block.
CRM agents update existing records instead of duplicating them
When an agent records something it has seen before, such as the same lead found on a later run, it now updates the matching CRM record instead of adding a second copy.
Workspace pages open faster on first load
Workspace pages, including a new team chat, no longer wait for sidebar lists, session details, or the team's model settings before showing, so they open noticeably sooner.
Runs recover from temporary connection failures
Runs resume automatically after temporary connection failures instead of immediately failing and requiring a manual retry.
List a Workflow's triggers from the API and CLI
GET /v1/workflows/{workflowId}/trigger-sources lists a Workflow's schedules, invoke hooks and integration triggers, with an optional type filter. The CLI exposes it as workflows trigger-sources list, and the API client as listWorkflowTriggerSources.
Workflow links open from project pages
Workflows and Runs open in both team and project workspaces. Overview, search, chat cards, and settings links preserve the current workspace. Missing addresses show a page-not-found screen, and error pages use the site's name and logo.
MCP adds task tools for handing off work
MCP clients, including the CLI's local MCP server, now get four task-oriented tools to start work, follow its progress, read results, and check spend. Every individual API operation stays available as a tool alongside them.
CRM entries keep their full values
Long record names in a CRM table now wrap instead of being cut off, so you can tell similar records apart without opening them. Shortened cell values stay readable in full.