Skip to content

marcusschiesser/agentpond

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

123 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

AgentPond — private trace storage and local analytics for AI agents

Store agent traces remotely. Analyze them locally. Keep control of the data.

CI status npm version npm downloads MIT license Node.js version

AgentPond is a lightweight trace backend and CLI for AI applications. It keeps raw traces in object storage you control and syncs them into a local DuckDB cache for fast analysis by developers and coding agents. Use it with Firebase Storage, Supabase Storage, Amazon S3, Google Cloud Storage, Vercel Blob, or custom infrastructure. Firebase, Supabase, and Vercel include automated setup; other deployments use the manual setup path.

How it works

AgentPond data flow from agent traces through object storage and local CLI analysis

Object storage is the durable source of truth. The local DuckDB database is a rebuildable analytical cache, so production traces stay in your infrastructure without requiring an always-on analytics database.

Getting started

Start with the Manual deployment setup to choose a write path, configure object storage, instrument the application, and sync its traces into AgentPond.

For Firebase, Supabase, and Vercel, AgentPond also provides automated quick starts:

All require Node.js 22 or newer for the CLI. From the provider project, run:

npx agentpond init

The command detects the platform, installs AgentPond's instrumentation and analytics skills, and prints a prompt for your coding agent. The agent inspects the trusted Node.js application, proposes the provider-specific setup, implements it after confirmation, and verifies a real trace.

Once the application has emitted a trace:

npx agentpond sync
npx agentpond traces list --limit 10

Analyze traces

Use focused commands for individual traces and sessions:

npx agentpond traces get <trace-id>
npx agentpond observations list --traceId <trace-id>
npx agentpond sessions get <session-id>
npx agentpond scores list --traceId <trace-id>

Use DuckDB SQL for aggregation, joins, time windows, or cost analysis:

npx agentpond sql "select id, name, session_id, total_cost from traces order by start_time desc limit 10"

Features

  • Direct OpenTelemetry export to Firebase Storage, Supabase Storage, S3, GCS, and Vercel Blob
  • Langfuse-compatible and OTLP HTTP ingestion adapters
  • Incremental object-store synchronization
  • Local DuckDB projections for traces, observations, sessions, and scores
  • Focused CLI commands plus arbitrary SQL
  • Human annotations represented as scores
  • Agent skills for instrumentation and trace investigation

Intentional non-goals

AgentPond does not provide a web UI, hosted trace storage, prompt management, datasets, or always-on Postgres, ClickHouse, Redis, and worker infrastructure. Use a full observability platform when shared dashboards or non-technical workflows are required.

Documentation

Development

pnpm install
pnpm cli --help
pnpm test

About

Store agent traces remotely. Analyze them locally. Keep control of the data.

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages