| name | agentpond |
|---|---|
| description | Inspect and analyze AgentPond traces, observations, sessions, and scores with focused CLI commands and DuckDB SQL. Use when investigating agent behavior, querying trace data, comparing sessions, reviewing annotations, or diagnosing failures after traces have already been collected. |
Use AgentPond to inspect collected trace data.
Read these references when relevant:
- Data-access commands and environment selection: references/cli.md
- DuckDB tables and SQL examples: references/duckdb-schema.md
- Trace investigation workflow: references/error-analysis.md
First determine whether the current directory is inside a Firebase project.
For Firebase, select the project with Firebase:
firebase use <alias-or-project-id>
npx agentpond syncAgentPond follows the Firebase CLI's active project selection, including
selections stored globally when the project has no .firebaserc.
If skill installation is cancelled, init stops without printing the coding-agent prompt.
For non-Firebase storage, inspect and select an existing AgentPond environment:
npx agentpond env current
npx agentpond env list
npx agentpond env use <name>
npx agentpond syncSelect only an existing non-Firebase environment as part of an analysis request.
Start with focused commands:
npx agentpond traces list --limit 25
npx agentpond traces get <trace-id>
npx agentpond observations list --traceId <trace-id>
npx agentpond scores list --traceId <trace-id>Inspect a session when behavior spans multiple traces:
npx agentpond sessions list
npx agentpond sessions get <session-id>Use SQL for joins, aggregation, time windows, raw event inspection, or cost analysis:
npx agentpond sql "select id, name, session_id, total_cost from traces order by start_time desc limit 10"Separate confirmed observations from inference. Include the trace or session IDs inspected, commands or SQL used, the observed pattern, the likely cause, and the smallest useful code, prompt, or workflow change.