openinference
OpenTelemetry Instrumentation for AI Observability
- 1.3k stars
- 366 forks
- 289 open issues
- Language: Python
- License: Apache-2.0
- updated
Install
git clone https://github.com/Arize-ai/openinference && cp openinference/*.md ~/.claude/agents/- Clone the repository and copy the agent .md definitions into ~/.claude/agents (or .claude/agents inside a project).
- Start a new Claude Code session to load the agents.
- Delegate work to them with the Task/Agent tool or by name.
7 items in this repository
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Run, interpret, and iterate on the OpenInference GenAI conformance MVP at python/openinference-instrumentation/scripts/conformance/. Use when the user mentions GenAI conformance, OTel GenAI semantic conventions, Weaver registry live-check, the dual-write conversion (`_genai_conversion.py`, `enable_genai_semconv`), `gen_ai.*` attribute coverage, or asks to add new providers / scenarios to the conformance harness.
Debug LLM applications using the Phoenix CLI. Fetch traces, analyze errors, structure trace review with open coding and axial coding, inspect datasets, review experiments, query annotation configs, and use the GraphQL API. Use whenever the user is analyzing traces or spans, investigating LLM/agent failures, deciding what to do after instrumenting an app, building failure taxonomies, choosing what evals to write, or asking "what's going wrong", "what kinds of mistakes", or "where do I focus" — even without naming a technique.
Investigate and propose fixes for Python canary cron failures in the openinference repo. Use when the user mentions Python canary failures, Python cron failures, or when the auto-fix CI job reports Python instrumentation canary issues.
Subagents overview
What people ask about openinference
What is Arize-ai/openinference?
Arize-ai/openinference is subagents for the Claude AI ecosystem. OpenTelemetry Instrumentation for AI Observability It has 1.3k GitHub stars and its last recorded update is dated 2026-10-23.
How do I install openinference?
You can install openinference by cloning the repository (https://github.com/Arize-ai/openinference) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.
Is Arize-ai/openinference safe to use?
Our security agent has analyzed Arize-ai/openinference and assigned a Trust Score of 100/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.
Who maintains Arize-ai/openinference?
Arize-ai/openinference is maintained by Arize-ai. The last recorded GitHub activity is dated 2026-10-23, with 289 open issues.
Are there alternatives to openinference?
Yes. On ClaudeWave you can browse similar subagents at /categories/agents, sorted by popularity or recent activity.