Agents Mutations List
Lists retained filesystem mutations performed by the selected agent, newest first. The agent must belong to the authenticated user and Provider app. Pass next_cursor to continue. A move or rename shows the old and new locations in one mutation. When a folder is moved, renamed, or deleted, changes to its contents caused by that operation are not listed separately.
Required scope: private:agent_filesystem.agents.manage
Endpoint format: RPC
Authentication: User
This endpoint does not support apps with the app folder permission.
Authentication
OAuth 2.0 token issued to a specific user. Use Authorization: Bearer <token>.
Public clients should use the authorization code flow with PKCE (S256).
For background or offline access, send token_access_type=offline during authorization and use the returned refresh token to obtain new access tokens.
You can generate a short-lived access token from the App Console; see Testing with a generated token.
Headers
Acts on behalf of a team member for supported user-auth operations. Pass a team member ID such as dbmid:.... When used with a team token, that token must also include the team_data.member scope.
Scopes path-based operations to a namespace (root). The value is a JSON serialization of the common.PathRoot union: {".tag": "home"}, {".tag": "root", "root": "<namespace_id>"}, or {".tag": "namespace_id", "namespace_id": "<namespace_id>"}. On failure the request returns 422 with a common.PathRootError.
Request
Response headers
Response
Mutations in this page, with operation-specific metadata and timestamp_us, a Unix timestamp in microseconds. Precision can be as coarse as one second, so mutations in the same second may share a timestamp. Using it as restore_to_timestamp_us may undo the selected mutation as well as later writes.