Skip to main content
Use chat to send messages to a Strix agent and get replies. You can attach repositories and files to give context. Chat requires an enterprise plan.

​
List chats

Required scope: chat:read

​
Start a chat

To attach files, send multipart/form-data instead of JSON. Use the same fields and add the file parts. Required scope: chat:write

​
Get a chat

Required scope: chat:read

​
Send a message

To stop an active agent turn before you send the message, set "cancel_current": true. message can be omitted for a control-only request when either cancel_current or stop_agent is true. cancel_current cancels the in-flight turn; stop_agent parks the target agent and its descendants:
Required scope: chat:write

​
Export workspace files

Chat artifacts live under /workspace in the running agent sandbox. List exportable files:
The listing is capped at 10,000 entries and 2 MiB before the sandbox response is parsed and normalized. An oversized listing returns 413. Download one file. The API accepts either an absolute path under /workspace or a convenient relative path such as report.md; relative paths resolve from /workspace. Traversal and absolute paths outside /workspace are rejected. An individual export is limited to 50 MiB.
Or stream the whole workspace as a ZIP:
Archive export preflights the same 2 MiB / 10,000-entry listing limit, a 50 MiB per-file limit, and 512 MiB of uncompressed content, with a 30-second archive deadline. ZIP entries must be safe relative POSIX paths. The service bounds sandbox JSON and base64 responses before parsing or decoding them, streams with response backpressure, and cancels in-flight sandbox work if the client disconnects. An empty workspace returns 404, and oversized listings or files return 413. Invalid listing, export, or file data from the sandbox returns 502; an unavailable, unready, or timed-out sandbox returns 503. A file read failure or actual-byte overflow fails the stream instead of returning a valid-looking partial ZIP. Required scope: chat:read The CLI adds safe file handling and refuses to replace an existing output unless --force is explicit:
Required scope: chat:write