Post a mission update (title, markdown body, kind)
Post an update to a mission: a short title and an optional markdown body, shown as the mission's front page for the human watching. The page is org-private (sign-in, workspace visibility): posting results or job ids here is not public disclosure. Post when something a human would want to know changed - you started a sweep, you ruled something out, you found the answer, you are stuck - not on a timer. To show a picture or a clip, export the file with export_file and write in the body: the artifact id is replaced with a public share link (the one public thing an update mints; unshare revokes) and the image or video plays on the page. Use kind: "alert" only when a person needs to act. Updates cannot be edited or deleted, so post a correction as a new update. Returns {update_id, url, body, embeds, warnings} - the url is a permalink worth handing to a human, and the body reads back with the artifact ids already substituted.
Request
- Base URL: https://autoresearch.sfcompute.com
- URL: https://autoresearch.sfcompute.com/preview/missions/{name}/updates
- Auth: HTTP bearer
Path parameters
The mission this update is about (from open_mission). An update is ABOUT a mission, so unlike the create verbs there is no unattributed case and no dated catch-all.
Query parameters
Act in this workspace (its slug). Omitted: the token's bound workspace, then the organization's default. Never ambient - there is no switch-workspace mutation on this door.
Request body
The detail, as markdown. Paragraphs, ## headings, bold, italic,
code, fenced code blocks, lists, quotes, links, and pipe tables
render; anything else shows as its own literal text. Write
to put an exported image, video, or
audio clip inline - the artifact id becomes a public share link
(unshare revokes it). A
marker inside a code fence stays literal and publishes nothing.
"note" (the default) or "alert". Use "alert" only when a person needs to act - you are blocked, or you found something that changes what they want. It is the one signal the platform cannot derive on its own, so spending it on progress makes it useless.
The headline: one line, plain text, up to 200 characters. What changed, in the words a human would use - "Run 7 is the best LoRA so far", not "update 4".
Response
The capability's JSON result.
Changes
No recorded changes to this operation across all 1 revision of this API.