agents-tree vs Pydantic Logfire

agents-tree 63

1.2.0 on PyPI on 8 October 2026, 24 days before the check, and a commit on main on 11 October (30). Five PyPI releases between 7 and 8 October 2026 (20). Issue and pull-request replies couldn't be read, as github.com was unreachable. The bare clone shows two Dependabot branches of 28 October unmerged (5 of 25). Not an MCP server and in no official directory; herdr's plugin marketplace couldn't be read (0). No runtime dependencies, a lock file, CI on five Python versions and Dependabot for the workflow actions, with its two updates unmerged (8 of 10). 63 in all.

Pydantic Logfire 90

The product changelog's newest entry is dated 7 October 2026 and the Python SDK's newest tag, 6.0.0b7, 25 September (30). Seven product changelog entries and ten SDK releases since 20 August (20). The SDK repository shows 208 open issues and pull requests. Pull requests opened in the past fortnight have comments, while several issues from the same period have none yet. Support is by Slack, email and GitHub (17). Current official SDKs, Python 5.1.0 on 11 September and @pydantic/logfire-node 0.18.27. The official MCP registry did not answer our lookup (15). CI, coverage and dependency test workflows and a lock file in the repository. We did not confirm the pass state (8).

agents-tree 60

Local-package reading, as for agent-tree, superpowers and tokeneconomizer. Installs from PyPI with uv tool install agents-tree or pipx, with Python 3.10 or later and POSIX stated in pyproject.toml and Linux and macOS in the herdr manifest (20). .github/workflows/test.yaml runs pylint, pyright, 173 pytest tests, a test run and a package build on Python 3.10 to 3.14 on every push and pull request. Whether the runs pass wasn't checked, as github.com couldn't be read (15 of 25). Issues couldn't be read for the same reason (5 of 25, unchecked). Semver tags and Conventional Commit messages, but no changelog, and the README's caveat that transcript formats may change is the only note on breakage; the switch to reading every provider by default came with 1.0.0 (5 of 15). Version 1.2.0 (15). 60 in all.

Pydantic Logfire 34

Graded as a hosted service (Logfire Cloud). No public status page was found on pydantic.dev, in the Logfire docs or in the files published for agents, so the status page and the incident record both score nothing (0 + 0). Query limits are documented per query source, but as Low, Standard and High levels per plan. The numbers found are a daily query API count on the pricing page (500 requests on Personal and Team, 5,000 on Growth), a 10,000-row maximum and the ingest limits (9). A refused query returns 429 with Retry-After, the docs give a retry example, and 89 of 106 public API operations declare the 429. No idempotency keys for writes were found (12). The pricing page lists an SLA for Enterprise plans with no published terms, and the Terms of Service give no warranty of availability (5). The MCP server, query API and public API carry no beta label, though the public API document is version 0.1.0 and the MCP access policy is marked experimental (8).

agents-tree 60

Self-hosted rule. No payment protocol (0). Free under MIT with nothing to buy (20). No card or account (20). A person installs it from PyPI with one command and no sign-up (20). 60 in all.

Pydantic Logfire 40

No x402, MPP or L402 (0). Per-unit pricing is public without a login, at $2 per million records beyond the included 10 million, with Team at $49 a month and Growth at $249 (20). The Personal plan is free with no card (20). A person signs up in a browser and approves OAuth or creates the first key. Client registration is unauthenticated but grants nothing until a user consents, and the CLI's login opens a browser (0).

agents-tree 64

Framework reading, docs a model can follow, as agent-tree was read. --json writes one document with schema_version 1 and a fixed set of session, agent and detail fields, and model.py types them as dataclasses, but no JSON Schema or field reference is published (14 of 25). README, AGENTS.md and docs/demo are Markdown in the repository; no llms.txt (10). The README says what it shows and reads, has a caveats section per provider (context window inference, internal formats, how running sessions are found), and the command's help says not to run it inside an agent (15 of 20). argparse with choices for --provider and --color, positive-number checks for --window and --interval, and --json refused with --watch (10 of 15). Usage examples for every flag, key and column tables, and errors as messages on stderr with exit code 1, with few error outputs documented (10 of 15). Semver tags and a schema version, no changelog (5 of 15). 64 in all.

Pydantic Logfire 81

A public OpenAPI 3.1 document of 68 paths and 106 operations, served without a key. The hosted MCP server is closed source and its host's robots.txt disallows the endpoint, so we did not read its tool schemas (22). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Every operation has a summary and 83 have a description. The MCP discovery card's tool descriptions say when to call a tool, for example token_info only when the user asks about identity (15). 38 enums in the document. Queries are a free SQL string by design and dashboards are Perses JSON (10). The docs carry curl, Python and TypeScript examples, 94 operations declare a 422 and 89 a 429, but the declared error schema is a single detail string and the document has few examples (11). /v1 paths, a dated product changelog and SDK release notes, with the API document itself at version 0.1.0 (13).

agents-tree 66

Harness reading of the framework checklist, as agent-tree and superpowers were read. 30 for what leaves the machine and credentials, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. No credentials, no network code and no runtime dependencies; PyPI releases are built by trusted publishing with no stored token and wait for a maintainer to approve the pypi environment. It reads every transcript of four agent CLIs, prompts included, and the herdr plugin runs the repository's bundled source rather than a PyPI release (26). Read-only by design. SQLite files are opened with mode=ro, nothing is written to an agent's files, and the only writes are a pane mark (directory 0700, file 0600, O_NOFOLLOW) and herdr's config block with a backup and check. It can't act on an agent (17). Control characters and escape sequences are stripped from every transcript field before a view, and the help warns that output run inside an agent lands in its context, but --json passes prompts and last messages unredacted with no note that they are untrusted (10). It keeps no state or log of its own. The detail view names each transcript's path, and herdr's config keeps a backup (8). No SECURITY.md, no security.txt and no advisories found; GitHub's security page couldn't be read. CI pins third-party actions to commit SHAs with Dependabot on them (5). 66 in all.

Pydantic Logfire 80

OAuth authorisation code with PKCE, S256 required for every client, dynamic client registration, pushed authorisation requests and device code, with 44 scopes. API keys carry selected scopes and can be rotated, expired and disabled through the API. No documented option sends a secret in a URL (30). Read-only scopes such as project:read, separate read and write tokens, and an organisation-wide read-only MCP policy that is Enterprise only and experimental. No server-side confirmation step for destructive tools was found (15). The MCP docs state that telemetry can hold user-controlled content and tell agents to treat results as diagnostic data, not instructions. SDK scrubbing is documented (11). The audit log API records logins and changes with user, IP address and a diff, on Enterprise only (9). A valid security.txt, SOC 2 Type II, HIPAA, and an independent penetration test at least every 12 months. No bug bounty found and no advisories published on the SDK repository (15).

agents-tree 62

MIT, an OSI licence (30). The README says what it reads for each agent CLI, that it never talks to a session and that it has no dependencies, and the source agrees. AGENTS.md forbids real session data in the repository. There is no privacy page, though the software sends nothing (22 of 30). No deprecation policy. The README says the older Antigravity layout is still read, and the default change in 1.0.0 came with a major version (5 of 20). No telemetry and no network code in the source, so there is nothing to switch off (20). 77 in all.

Pydantic Logfire 75

The platform is closed source under clear terms, with MIT SDKs and an open Helm chart (18). The Privacy Statement (22 August 2026), a public Data Processing Addendum with 72-hour incident notice, and retention stated per plan. The documents disagree in places. The terms say Personal data past the allowance is stored but hidden, where the docs say it is dropped once a buffer is used. The data regions page names GCP only, where the sub-processor list names GCP and AWS for hosting. The terms give no warranty that data is deleted promptly after retention ends (20). Twelve operations are marked deprecated in the OpenAPI document and SDK removals are listed in release notes for major versions, but no notice period or removal dates were found, and the terms allow the service to be changed or discontinued with reasonable efforts to notify (9). The sub-processor list gives each vendor's purpose and location with 14 days' notice of changes, and both hosting regions are named (20).