2026-11-01: search, automate, share and subscribe
Joined the list:search (it keeps its name), automate, share and subscribe. Their REST twins answer in the verb shape only: GET /v1/search, /v1/automations (a run is POST /v1/automations/{id}/runs), POST /v1/shares and POST /v1/webhooks.
search takes q, types, limit and cursor, and answers {hits: [{uri, type, title, snippet}], next_cursor}; get a hit’s uri for the whole object. A call that still sends query is read as q. offset is gone: page with next_cursor.
Left the list, and still answer by name:
The six automation names now answer
automate’s shape, {automation, automations, status}, and send its {spec} body; their arguments are read as before, except tools, which no automation takes any more. run_automation reaches POST /v1/automations/{id}/runs.
act gained two actions. lower_autonomy drops one lane (payload: {lane, steps}, no ref), applied at once with only steer; naming a level is refused, since raising is a person’s. erase deletes what the workspace holds on payload.email and keeps only its hash on the suppression list (attensira://{workspace}/contact_suppression, needs configure). configure gained kind: "brand_book" (never-say, voice and facts) and kind: "lane_budget" (the outreach lane’s paid-placement budget, always a proposal). Lowering autonomy is act’s alone: configure refuses kind: "autonomy" and names lower_autonomy.
2026-10-31: the Today card in ChatGPT
No tool joined or left the list, and no answer changed.brief now names a card in its _meta (openai/outputTemplate: ui://widget/today.html), so ChatGPT shows the brief as the Today card, with Approve and Decline on each waiting change. act is marked openai/widgetAccessible so the card can call it. Clients that do not show cards get the same text and structuredContent as before.
2026-10-27: more on act, list and configure
No tool joined or left the list.act takes resume and unmerge on a question (t_…), and approve or decline on a Today decision (attensira://{workspace}/today_ask/{thread}_{ask}), which had no MCP twin. list takes type: "goal_metric", the goal metric catalog. configure takes kind: "notifications", a proposal a person finishes; choosing a new workspace’s destination is kind: "destination".
2026-10-27: the work on other sites
No tool joined or left the list.get, list and act now reach the work agents do on other sites:
Granting consent, connecting a credential and sending a reply are not
act actions: a person does them in the app, and over REST every key and connection gets 403 forbidden. Pausing every browser run and resuming a run or a thread stay in the app.
2026-10-25: the write verbs
Joined the list:act, mission, configure, playbook and estimate. ask keeps its name and takes the new shape (message, thread), which starts or continues a thread; the older question/session shape still answers, followed by a line naming the new one. Their REST twins are POST /v1/actions, POST /v1/missions, POST /v1/config/{kind}, POST /v1/playbooks/{name}/runs, POST /v1/estimate and POST /v1/threads.
Left the list, and still answer by name:
resolve_inbox_task, set_goal and propose_plan_change stay listed: the verbs do not reach what they do yet.
2026-10-19: the read verbs
Joined the list:brief, get, list and analyze. Each one does the work of a family of older reads, so the list is shorter and each tool does more. Their REST twins are GET /v1/brief, GET /v1/objects/{type}/{id}, GET /v1/objects/{type} and GET /v1/views/{view}.
Left the list, and still answer by name:
The other tools are unchanged.
search and ask keep their names and shapes; the verbs of the same name are not listed yet. The verbs that act joined the list on 2026-10-25, above; automate, share, subscribe and plan_fixes join when the routes behind them are served in their shape.