Read API activity history

Selected requests sent through the computer API. This does not identify an agent or show all guest work. A hosted agent run (POST /computers/{id}/agent, POST /chat/completions or the dashboard agent) adds one summary row with channel managed-agent and action agent, carrying funded and cost_usd. It stays pending while the run lasts, for at most about two hours. Each input or bash command the run sends to the desktop is also recorded as its own row with channel managed-agent, so one run can add many rows; its screenshots are not recorded. Requests from an API key carry channel api, and the dashboard’s own carry session-api. History retains up to 7 days, 10000 rows per computer and 100000 per account, including pending rows. Each safe metadata row is at most 1024 bytes; pages contain at most 50 rows. Expired rows are excluded immediately; bounded periodic physical cleanup can lag with backlog or downtime. Pages are newest first with a fixed insertion watermark. Cursor tokens are opaque and bound to account, computer, current workspace and credential scope. Use changes=1 with changes_cursor to receive inserts and final updates, including old rows finishing. Follow next_cursor to drain a bounded change page. Send next_cursor back with the same changes value it came with: a history cursor without changes, a change cursor with changes=1. A history cursor that is invalid, expired, minted for another computer or credential scope, or a change cursor sent without changes=1, answers 400; it never restarts at the first page. In changes mode, any cursor that cannot continue (expired, invalid, or a history cursor) answers gap:true instead. A gap requires refreshing history; reads never replay an action. Member or owner access and fresh computer scope are required for every read. Reads work while stopped or suspended without waking the guest. Unavailable scope or storage answers 503 with incomplete:true, never an empty success. Capture is best effort. Unknown outcomes are never resolved by reading output; an accepted background request is not completion. No command, output, input text or arbitrary error prose is retained. Any other query parameter, or either one sent twice, is a 400.

Requires the member role or higher.