Resolve Requests

Resolve Requests is the platform history browser for roster.resolve, REST POST /api/v1/resolve, and related MCP activity.

Visibility follows authorization:

• Admins can read all resolve history.
• Project owners can read history for owned projects.
• Active users can read their own requests.

PII visibility follows the current Settings policy for resolve requests and result fields.

Table Columns

Column	Meaning
Created	Time the resolve request was created.
Query	The natural-language request, plus any labels attached to the result.
Actor	Team member, AI agent, service account, or API key that initiated the request.
Resolution	success, not_found, out_of_scope, or error.
Mode	live for production/live execution or test for test execution.
Project	The project associated with the request.
Results	Participant and user counts returned by resolution.
Latency	End-to-end request latency when recorded.

Filters

The web screen supports:

• Query text search
• Date: all, today, last 7 days, last 30 days, or custom range
• Resolution status
• Mode
• Project
• Label
• Participant

Project, participant, and label filters can be shared through saved browser URLs.

Details Drawer

Open a request to inspect:

• Overview: created/completed time, latency, project, counts, confidence, app version, query, response, and error text
• Participants: matched participants
• Users: resolved users
• Request context: request IDs, MCP/provider IDs, actor details, API token ID, scope, provider, model, effort, and project details

Result details may be redacted when resolve-request PII settings disable query text, actor details, credential details, or specific result fields.

REST History

The REST API exposes resolve history through:

• GET /api/v1/resolve-requests
• GET /api/v1/resolve-requests/:id

Both require api:resolve-requests:read. See Resolve API for request and response examples.