phoenix-cli
Debug LLM applications using the Phoenix CLI (`px`, from @arizeai/phoenix-cli). Fetch traces, spans, and sessions, annotate them, analyze errors, measure how often a failure or pattern occurs across traces, inspect datasets, review experiments, query annotation configs, and use the GraphQL API. Use whenever the user works with a Phoenix instance from the terminal, or wants to measure or investigate something in Phoenix with the CLI.
Install
With your agent
Install OMGSkills skill "arize-ai/phoenix:phoenix-cli" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Arize-ai/phoenix /tmp/phoenix && ln -s /tmp/phoenix/.agents/skills/phoenix-cli ~/.claude/skills/phoenix-cliFrom README
Phoenix CLI Invocation The CLI uses singular resource commands with subcommands like list and get: Every delete above is gated: it requires PHOENIXCLIDANGEROUSLYENABLEDELETES=true in the environment and prompts for confirmation unless -y/--yes is passed (px profile delete is local-only and takes --yes without the env gate). Without the env var the command exits without deleting anything. PHOENIXENDPOINT is the base URL for API access. It usually holds the same URL as PHOENIXCOLLECTORENDPOINT; when only the collector variable is set, the CLI uses it for API access too. For interactive local use, px auth login stores an OAuth session in the selected profile; the session acts with the permissions of the user who logged in. API keys take precedence over OAuth tokens when both are configured. OAuth access tokens are refreshed automatically for REST, GraphQL, and PXI requests, and rotated tokens are persisted to the selected profile. Always use --format raw --no-progress when piping to jq.