v4.81.0
The paged agent can read the logs too.
New
run402 logsand the SDK'sfunctions.logs(and the request-id fan-out) use the project's cached service key when present and otherwise the client's own credential (SIWX wallet, session, or delegate), which the gateway now authorizes withproject.readonGET /projects/v1/admin/:project_id/functions/:name/logs. The per-sample logs drill-down an error fingerprint hands out works for an organization member or teammate agent with no project key. A service key is now checked against the addressed project (cross-project reads 403).- MCP
get_function_logsforwards the gateway's verdict instead of failing locally when a project is not in the keystore.
Full changelog: v4.80.1...v4.81.0