Trace every agent session on your machine — Claude Code, Codex, Cursor, Copilot — into one history you and your agents can manage, search, and evaluate.
Thirdeye persists each session as a durable, append-only local event history. Prompts, responses, tool calls, subagents, usage, and session metadata remain available after the original agent process exits, giving both people and agents a consistent record to inspect. Connect thirdeye to Pydantic Logfire to make full use of that tracing data: explore complete execution trees, investigate individual turns, and analyze behavior across sessions.
Visit third3y3.com for guides and the full command reference.
Installation
Homebrew is the simplest option on macOS and Linux. On Windows, use pipx
or uv.
brew install duncankmckinnon/tap/thirdeye
Alternatively, install with pipx:
pipx install thrdi
Or use uv or pip:
uv tool install thrdi
pip install thrdi
Setup
Run the guided setup after installation:
thirdeye setup
The setup flow:
- Selects the agent integrations you want to trace.
- Installs the required hooks or agent configuration.
- Offers to install thirdeye's bundled skills in the matching agent directories.
- Optionally connects Pydantic Logfire and saves the write token used for export.
You can rerun setup whenever you add an agent or change your Logfire configuration.
Logfire
Pydantic Logfire is where thirdeye's captured data becomes a full observability experience. Once connected during setup, each session appears as an OpenTelemetry trace containing agent turns, model calls, tool executions, subagents, and available token usage and attributed costs. Use Logfire to navigate the complete execution flow, query across sessions, compare agent behavior, and investigate where time and tokens were spent.
Export happens outside the agent hook, so network latency does not interrupt the agent session.
See third3y3.com for Logfire configuration and export details.
Skills
Thirdeye includes focused skills that let coding agents work directly with the history it captures:
use-thirdeye— inspect sessions, search events, debug tool calls, and analyze captured usage.thirdeye-evals— create evaluation rubrics, run evaluators, and interpret per-turn findings.thirdeye-review— audit agent behavior for inefficiencies and recommend concrete invocation or skill improvements.thirdeye-filter— translate natural-language questions from the UI into structured session and turn filters.thirdeye-logfire— configure, verify, and troubleshoot thirdeye's Logfire integration.
The setup flow can install these for you. To add them later, run
thirdeye skills add; use thirdeye skills list to see what is available.
Contributing
Contributions are welcome. See CONTRIBUTING.md for local development, validation, and pull-request guidance.
1 maintainer
Metadata
1 maintainer
Release files for thrdi 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| thrdi-0.2.4.tar.gz | 4.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| thrdi-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.5 MB
Release files / thrdi-0.2.4.tar.gz
| Download URL | thrdi-0.2.4.tar.gz |
|---|---|
| Size | 4.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
037ca57ea66737af6dde304a1c645ab109f0cbddaf850a8775dea898f32c6200
|
|
BLAKE2b-256 checksum How to use checksums |
faa24ecccc90796419e66745c883377207ed591b086a57ea430deed2f1d5f718
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logRelease files / thrdi-0.2.4-py3-none-any.whl
| Download URL | thrdi-0.2.4-py3-none-any.whl |
|---|---|
| Size | 499.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
800508e7ac40a2078e0c7af507d97f223c26438c194a9c5a46ce4dd0f57cd1e3
|
|
BLAKE2b-256 checksum How to use checksums |
ec33614db133516c45cdbcf4fab68d82beab1c59c3d08313673df7a18aa1ba9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency log
