Skip to main content

eurysx

gh release eurysx version

Local-first usage observability for Claude Code, OpenCode, Pi, and Codex.

Eurysx reads local agent history and reports tokens, requests, turns, tool calls, estimated or recorded cost, and pricing provenance. Provider-reported organization aggregates can be imported from report files you saved yourself, shown as a separate lane that is never mixed into local cost. Eurysx makes no API calls and does not upload usage data or persist prompts, responses, file contents, tool arguments, or tool results.

Eurysx v0.2.1 is a local CLI, not a hosted service.

What the name means

Eurysx is derived from Euryphaessa, an epithet associated with broad-shining light. Its eury root suggests a wide view; s evokes stats or sight, and x marks cross-agent work. It is a compact name for seeing usage across coding harnesses without pretending that their routes, prices, or records are interchangeable.

Our philosophy

  • Local history is evidence, not telemetry: usage stays on the machine and sensitive session content is neither persisted nor reported.
  • Unknown stays unknown. Eurysx does not invent a price, provider route, or billing mode when the available records cannot support one.
  • Recorded cost wins over policy. Configurations make user intent explicit; they do not rewrite what a harness recorded.
  • One normalized view should preserve provenance. Comparable reports must still show where data and pricing came from.
  • The tool remains a small, local CLI, not a hosted analytics service or an agent-management platform.

Install

pip3 install eurysx
eurysx --help

Run

eurysx --version
eurysx
eurysx --agent codex --days 30
eurysx --agent all --month 2026-08
eurysx --agent pi --from 2026-08-01 --to 2026-08-15
eurysx --agent all --days 30 --output reports/usage.json
eurysx --agent all --days 30 --format html
eurysx --agent all --days 30 --output reports/august-usage --format html
eurysx --refresh-pricing
eurysx collect --agent codex
eurysx report --agent codex --days 30
eurysx doctor

reports/ is ignored by Git. eurysx collects current local metadata and then reports it. collect stores metadata only; report reads the local store without collecting. doctor is terminal-only and reports local harness, source, pricing-cache, and configuration health without parsing history, refreshing prices, or deleting retained data.

Period selectors are mutually exclusive: --days N, --weeks N, --from YYYY-MM-DD [--to YYYY-MM-DD], --month YYYY-MM, --quarter YYYY-QN, --year YYYY, and --ytd. Rolling periods include today. Filter selectors --model, --provider, and --billing-mode combine with agent and period selectors.

Documentation

The User manual is the authoritative command, output, configuration, pricing, and diagnostics reference.

Current limits

  • Claude Code's stats cache is aggregate-only; selected date ranges exclude it and report a scope warning.
  • The supported collectors are Claude Code, OpenCode, Pi, and Codex only.
  • Pricing data is metadata only. Source pricing may be unavailable, in which case the relevant cost remains unknown.
  • Preferences use recorded route metadata or exact user rules. Eurysx does not call LiteLLM or provider APIs for route discovery and never reads credentials.
  • API-equivalent estimates are opt-in, never invoices or budget spend. All report formats distinguish them from harness-recorded cost; see the User manual for the JSON fields and N/A behavior.
  • Anthropic aggregate imports are organization-level daily totals read from report files you saved yourself: no API calls, no credential reads, and no session or project attribution. They are never added to local known cost, coverage, pacing, or period comparisons, and they exclude Bedrock, Vertex, and Foundry routes. Claude Code Analytics and Console CSV imports are not supported yet.

Development

PYTHONPATH=src python3 -m unittest -v tests/test_eurysx.py
python3 -m py_compile src/eurysx/*.py

Sanitized collector fixtures cover Claude Code, Codex, Pi, and OpenCode. The OpenCode SQL fixture builds a temporary SQLite database during the test rather than committing a binary database file.

Metadata

Release files for eurysx 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eurysx 0.2.1
File Size Uploaded Provenance Actions
eurysx-0.2.1.tar.gz 86.7 kB With provenance Details for eurysx-0.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for eurysx 0.2.1
File Interpreter ABI Platform Actions
eurysx-0.2.1-py3-none-any.whl Python 3 none any Details for eurysx-0.2.1-py3-none-any.whl

Total release size: 143.8 kB

Release files / eurysx-0.2.1.tar.gz

Download URL eurysx-0.2.1.tar.gz
Size 86.7 kB
Tags Source
SHA-256 checksum
How to use checksums
c47bf0076d17011c265e14f44876ab3d6aecdb75b98dffe00faf914c654bf22e
BLAKE2b-256 checksum
How to use checksums
76e8e6c2f4e7b78150bda40394ff4c578b5ecd34194c384c56399c6779941ceb
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 20, 2026.

Transparency log

Release files / eurysx-0.2.1-py3-none-any.whl

Download URL eurysx-0.2.1-py3-none-any.whl
Size 57.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9d4e482b003581f85d0cd759f23649a13457af65dd613f604aba78042994278d
BLAKE2b-256 checksum
How to use checksums
46089e626c26044076383d43ef4b3cb4b338fd24e44f34a88e2d15970b0eb3b2
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 20, 2026.

Transparency log

Security for eurysx 0.2.1

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for eurysx-0.2.1.tar.gz

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 20, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page