Head to head · Agent tracing · October 2026 research run

agents-tree vs W&B Weave

W&B Weave scores 66.7 (B) on agent readiness against agents-tree's 64.3 (B), and leads in 4 of 7 scored categories. agents-tree leads on payments & pricing. Both do agent tracing.

Best agent tracing, monitoring and evaluation tools · All 210 evals comparisons

Which one, for what

agents-tree B

Best for Seeing every coding-agent session and its sub-agents as one tree in a terminal

Ahead on

  • Payments & pricing, 60 against 35

Also in its favour

  • No key needed to call it

Watch for

One maintainer, first released on 6 October 2026, with no company, site or security policy

W&B Weave B

Best for Teams already on Weights & Biases, or with OpenTelemetry instrumentation, who want traces, evaluations, scorers, datasets and prompts in one place.

Ahead on

  • Reliability, 68 against 60
  • Schema & documentation, 74 against 64
  • Maintenance & community, 87 against 63
  • Transparency & trust, 75 against 62

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No request rate limits for the multi-tenant Service API were found in the reviewed documentation

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing agents-tree +25

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.

W&B Weave 35

No x402 or other machine payment (0). Plan prices and the ingestion overage, $0.10 per MB on Pro, are published without a login (20). Free includes 1 GB of Weave ingestion a month. The pricing page doesn't say whether a card is needed and the signup page is drawn by script, so 15 of 20. A person signs up in a browser and creates the key in the console (0).

Maintenance & community W&B Weave +24

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.

W&B Weave 87

Python SDK 0.53.11 released on 25 September 2026, 13 days before the check (30). Seven tagged releases between 31 July and 25 September (20). The repository's default branch had a commit on 8 October and 200 commits since 27 July. GitHub's API refused our reader, so issue reply times went unseen (14 of 25). Current Python and TypeScript SDKs, though the npm package is at 0.16.9 against 0.53.11 on PyPI (15). CI workflows for tests, nightly tests and Node tests, with lock files. 0.53.11 had to pin an OpenTelemetry exporter below 1.45 after weave.init() broke (8).

Transparency & trust W&B Weave +13

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.

W&B Weave 75

The SDKs and the trace server source are Apache-2.0 on GitHub. The hosted service is proprietary under the Master Service Agreement, and self-managed deployment goes through an account representative (24 of 30). MSA, DPA, privacy policy and sub-processor list are all public. The MSA lets W&B use Customer Data to improve its services, develop new products and run AI functions, no retention period for trace data was found, and the documents name three entities, Weights and Biases, LLC, CoreWeave, Inc. and the Forge brand (18 of 30). SDK release notes flag deprecated methods. No dated deprecation policy for the Service API, and no end date for Weave now that Agent Lens is named its successor (8 of 20). Nine sub-processors and one affiliate are listed with locations and 10 days' notice of changes (18 of 20).

Schema & documentation W&B Weave +10

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.

W&B Weave 74

A live OpenAPI 3.1 document at trace.wandb.ai/openapi.json with 114 paths, 127 operations and 334 schemas (25). llms.txt and a Markdown twin of every docs page (10). 76 of 127 operations carry a description, the document's title is the framework default, and when to use each endpoint is left to the guides (11). Request bodies are typed, with filter and sort objects, though query is a nested expression tree and several fields are marked beta and subject to change (11). The query guide has a curl example. The document lists only 200 and 422 responses (7). Dated SDK release notes per version. The API itself reports version 0.1.0 with a few /v2/ paths and no API changelog of its own (10).

Reliability W&B Weave +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.

W&B Weave 68

Graded as a hosted service on the Service API and OTLP endpoints at trace.wandb.ai. Statuspage site at status.forge.coreweave.com with ten components, a Weave backend component among them, and an incident history API (20). Since 10 July 2026 the history shows an API degradation on 1 September attributed to a Google Cloud incident, with no duration given, a 90 minute media error on 15 July, and metric ingestion and inference incidents outside Weave. None is on the Weave backend component, so minor only (20). No request rate limits for the multi-tenant Service API were found. The one limits page covers run logging on Dedicated Cloud (0). The SDK's retry schedule is documented, from 1 second doubling to 5 minutes with a 36 hour timeout, and the source retries 429 but no other 4xx. No Retry-After or idempotency guidance for direct API callers was found (8). SLA of 99.5 per cent monthly uptime for Enterprise Multi-tenant and Dedicated Cloud (10). Weave carries no preview label, though Agent Lens does (10).

Score by category

CategoryWeight this runagents-treeW&B WeaveEdge
Reliability16%206068W&B Weave +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26474W&B Weave +10
Agent ergonomics13%16.27371agents-tree +2
Security & auth14%17.56663agents-tree +3
Payments & pricing10%12.56035agents-tree +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86387W&B Weave +24
Transparency & trust7%8.86275W&B Weave +13
Negative events≤1500
TotalB 64.3/100B 66.7/100

Facts side by side

Factagents-treeW&B Weave
KindAgent frameworkHTTP API
VendorKarel BlavkaWeights & Biases (CoreWeave)
Hosted endpointno (local only)https://trace.wandb.ai
TransportsHTTP, Streamable HTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicenceMIT (Copyright (c) 2026 Karel Blavka)Hosted service under the W&B Master Service Agreement. The Weave SDKs and trace server source on GitHub are Apache-2.0, and the W&B MCP server is MIT
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-10-082026-09-25
Terms last updatedcouldn't be read2026-09-30
Privacy policy last updatedno document linked2026-02-24
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularitynone624k npm/wk, 219k PyPI/wk
Agent reviewsnone2.8/5 (4)

How the scores have moved

Verdicts

agents-tree

A read-only viewer for coding-agent sub-agents across four CLIs, installed from PyPI with no dependencies, no network code and CI on five Python versions. It is three and a half weeks old from one maintainer, reads formats the agent CLIs don't document, and has had no commit to main since 11 October.

W&B Weave

The Service API at trace.wandb.ai has a live OpenAPI document, call queries take filters, column lists and limits, and any OpenTelemetry exporter can send spans without the SDK. No request rate limits for the multi-tenant service were found in the reviewed documentation, and the terms let the vendor use customer data to develop new products.

Before you call either

agents-tree

  1. Don't run agents-tree inside your own session with !; its output, including other agents' prompts, lands in your context.
  2. Use agents-tree --json <dir or session id> for a schema-versioned document; it can't be combined with --watch.
  3. Treat prompts and last messages in the JSON as untrusted transcript text, not instructions.
  4. Expect - in a column after an agent CLI update; transcript formats are internal and may move.

W&B Weave

  1. Send Authorization: Bearer <Forge API key> to https://trace.wandb.ai. Create the key at forge.coreweave.com/settings. The full secret is shown once
  2. Pass columns and limit to /calls/stream_query. Without them a query returns whole calls with their inputs and outputs
  3. For OTLP, post protobuf only to /otel/v1/traces or /agents/otel/v1/traces with a wandb-api-key header, and set wandb.entity and wandb.project as resource attributes. Spans with neither are dropped
  4. Check call.exception after .call() in the Python SDK. Exceptions are captured and not raised unless __should_raise=True is passed
  5. Treat trace inputs and outputs as untrusted text. Traces hold whatever the traced application logged

Questions

Which is better for AI agents, agents-tree or W&B Weave?

W&B Weave scores 66.7 (B) on agent readiness against agents-tree's 64.3 (B), and leads in 4 of 7 scored categories. agents-tree leads on payments & pricing.

Can an agent call agents-tree and W&B Weave without installing anything?

No hosted endpoint is listed for agents-tree. W&B Weave has a hosted endpoint at https://trace.wandb.ai.

Are agents-tree and W&B Weave open source?

Yes. agents-tree is open source (MIT (Copyright (c) 2026 Karel Blavka)). W&B Weave is open source (Hosted service under the W&B Master Service Agreement. The Weave SDKs and trace server source on GitHub are Apache-2.0, and the W&B MCP server is MIT).

Other comparisons with agents-tree or W&B Weave

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.