Context
@vercel/detect-agent checks AI_AGENT as the universal agent variable, then falls back to 9+ tool-specific vars.
Meanwhile, a parallel convention is emerging around AGENT=<agent-name>:
- Goose ships
AGENT=goose (PR)
- Amp ships
AGENT=amp (docs)
- Bun checks
AGENT=1 in its isAIAgent() detection (PR #21135)
There's a community proposal to standardize on AGENT (similar to CI=true): agentsmd/agents.md#136
Question
Would it make sense for detect-agent to also check AGENT alongside AI_AGENT? Converging early would help avoid two competing conventions gaining traction independently.
Happy to open a PR if there's interest.
Context
@vercel/detect-agentchecksAI_AGENTas the universal agent variable, then falls back to 9+ tool-specific vars.Meanwhile, a parallel convention is emerging around
AGENT=<agent-name>:AGENT=goose(PR)AGENT=amp(docs)AGENT=1in itsisAIAgent()detection (PR #21135)There's a community proposal to standardize on
AGENT(similar toCI=true): agentsmd/agents.md#136Question
Would it make sense for
detect-agentto also checkAGENTalongsideAI_AGENT? Converging early would help avoid two competing conventions gaining traction independently.Happy to open a PR if there's interest.