feat(analytics): enhance command tracking with agent identification properties

[ramya18101]

🔧 Changes

This pull request introduces a robust agent detection system to the CLI, allowing the application to identify which AI agent or client is invoking the CLI.

📚 References

DXCDT-1876

🔬 Testing

Added agent_detection_test.go

📝 Checklist

• All new/changed/fixed functionality is covered by tests (or N/A)
• I have added documentation for all new/changed functionality (or N/A)

[brth31]

Several issues to fix before merging:

1. COPILOT_AGENT doesn't exist — change to COPILOT_AGENT_SESSION_ID
Confirmed from the github/copilot-cli changelog: "Shell commands and MCP servers now receive COPILOT_AGENT_SESSION_ID as an environment variable." The current entry will never match.

// fix
{envVar: "COPILOT_AGENT_SESSION_ID", agentName: "github-copilot"},

2. OPENAI_CODEX doesn't exist — change to CODEX_THREAD_ID
Confirmed from codex-rs/protocol/src/shell_environment.rs in openai/codex — CODEX_THREAD_ID is injected into every subprocess Codex spawns. OPENAI_CODEX doesn't exist anywhere in the codebase. On macOS, Codex also sets CODEX_SANDBOX=seatbelt as a secondary signal.

// fix
{envVar: "CODEX_THREAD_ID", agentName: "codex"},
{envVar: "CODEX_SANDBOX",   agentName: "codex"},

3. GEMINI_CLI_VERSION is not an env var — remove it
In the Gemini CLI source it's a protobuf metadata key (integer 54) used for internal analytics — not set on child processes. Gemini passes env: process.env unmodified to subprocesses. This entry is dead code. Note: Gemini CLI is also being deprecated in favour of Antigravity (agy).

4. Antigravity (agy) is missing — add it
Google's Antigravity CLI (agy, Gemini's successor) injects ANTIGRAVITY_CONVERSATION_ID into every subprocess it spawns. Confirmed from the agy binary directly.

{envVar: "ANTIGRAVITY_CONVERSATION_ID", agentName: "antigravity"},

5. MCP server detection doesn't work via either path
The AUTH0_CLI_CLIENT handshake (Tier 1) requires the Auth0 MCP server to set AUTH0_CLI_CLIENT=mcp-server when shelling out to the CLI — that change doesn't exist in the MCP server repo yet. The process walk fallback (Tier 3) also doesn't work: the MCP server runs as node /path/to/auth0-mcp-server.js, so the OS process name is node, not auth0-mcp-server. There is currently no path where MCP server traffic gets identified — it will always fall through to unknown. The fix is a one-line change in the MCP server repo to set AUTH0_CLI_CLIENT=mcp-server when invoking the CLI. Please track this as a linked follow-up to DXCDT-1876 before the epic is closed.

Suggested enhancement: wildcard sweep for unknown future agents
Three naming conventions have emerged across major agent CLIs: *_CONVERSATION_ID, *_THREAD_ID, *_AGENT_SESSION_ID. A secondary sweep after the known-list catches future agents without a code change per agent:

for _, e := range os.Environ() {
    key, val, ok := strings.Cut(e, "=")
    if !ok || val == "" {
        continue
    }
    upper := strings.ToUpper(key)
    if strings.HasSuffix(upper, "_CONVERSATION_ID") ||
        strings.HasSuffix(upper, "_THREAD_ID") ||
        strings.HasSuffix(upper, "_AGENT_SESSION_ID") {
        return "unknown-agent"
    }
}

[ramya18101]

Tested and added screenshots

[ramya18101]

• Claude Code: CLAUDECODE and CLAUDE_CODE_SESSION_ID are called out in the Claude Code changelog entry about subprocess environment propagation. Claude Code changelog.

• Claude Code: AI_AGENT is called out in the Claude Code changelog entry about subprocess attribution. Claude Code changelog.

• Gemini CLI: ANTIGRAVITY_CLI_ALIAS and CURSOR_TRACE_ID are checked in Gemini’s IDE detection code. Gemini CLI detect-ide.ts.

• Gemini CLI: GEMINI_CLI_VERSION is present in Gemini’s telemetry event metadata keys. Gemini CLI event-metadata-key.ts.

[ramya18101]

• CURSOR_CONVERSATION_ID: observed in a real Cursor session and validated locally.
• ANTIGRAVITY_CONVERSATION_ID: observed in local
• CODEX_THREAD_ID: observed in real Codex runs