agents-tree vs LangSmith API + MCP

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.

LangSmith API + MCP 86

Public OpenAPI 3.1 at api.smith.langchain.com/openapi.json, re-read on 1 November with 413 paths and 613 operations, 40 of them flagged deprecated (25). llms.txt and Markdown docs (10). MCP tool docstrings are long and practical. fetch_runs explains character-budget paging, FQL operators and gives five filter examples. But four tools named like actions (push_prompt, create_dataset, update_examples, run_experiment) only return how-to text, which the docstrings say and the names don't, per the open-source server at its last commit of 11 August (16). Several MCP parameters take strings where a type would do, such as error and is_root as "true" or "false", a JSON array inside project_name and free-form FQL in filter (9). Examples throughout the docs and docstrings. Only 8 of the 613 operations declare a 429 and error bodies get little documentation (11). Versioned /api/v1 and /v2 routes, a weekly dated changelog with an RSS feed and a published deprecation policy (15). 25+10+16+9+11+15 = 86.

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.

LangSmith API + MCP 85

The SDKs moved on 16 October from langsmith-sdk (now archived) to langsmith-python and langsmith-javascript, with the same PyPI and npm packages. Python 0.14.16 on 29 October and JavaScript 0.11.6 dated 31 October in its changelog (30). 31 Python SDK tags in the 90 days to 1 November, 0.10.16 (5 August) to 0.14.16 across the old and new repositories, and JavaScript releases to 0.11.6 (20). Both new repositories take commits daily and auto-label new issues. We didn't load reply times (12). Python and TypeScript SDKs both current (15). CI, release and benchmark workflows run in public in both repositories. Pass state not checked (8). 30+20+12+15+8 = 85.

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.

LangSmith API + MCP 81

incident.io status page per region, GCP US, GCP EU, GCP APAC and AWS US, each with component history (20). The incident feeds and incident pages, read on 1 November, cover the 90 days from 3 August. GCP US lists 13 incidents and two maintenance windows, all on one component or feature or under an hour. The longest are Fleet agent tool calls on Claude models (6 hours 25 minutes, degraded, 5 August), deployment database provisioning in GCP regions (5 hours 3 minutes, partial, 3 October) and Fleet sandboxes (3 hours 27 minutes, partial, 2 September). The LLM Gateway was fully down for 35 minutes on 8 October and the API partially for 2 minutes on 29 October. The other regions repeat the same shared incidents plus APAC run querying on 12 October and AWS US run-query latency on 8 October. Minor only (20). Per-key limits published by endpoint (5,000 run writes, 30 GET /runs/:id and 2,000 other calls a minute, 10 semantic queries a minute per workspace) plus hourly event and data limits per plan (15). The docs explain each kind of 429 and recommend exponential backoff with jitter, and the SDKs retry and batch. Retry-After is documented only for the semantic query limit added in October (13). Enterprise has a support SLA. We found no uptime SLA (3). API and remote MCP are GA (10). 20+20+15+13+3+10 = 81.

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.

LangSmith API + MCP 40

No x402 or other machine payment (0). Per-trace pricing is public, a base trace at 0.005 LSU and the extended-retention upgrade at 0.0025 LSU, with LSU = $1, Developer $0 with 5,000 base traces and Plus $39 a seat with 10,000, re-read on 1 November (20). Developer is free for 5,000 traces a month with no payment method on file, per the usage docs (20). A person signs up in a browser to create a key (0). 0+20+20+0 = 40.

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.

LangSmith API + MCP 78

Closed platform. The SDKs and the open-source MCP server are MIT (18). Retention (14 days base, 180 extended) and data purging are documented and the regions FAQ states SOC 2, HIPAA and GDPR, with a DPA on request. The 180-day cap on extended retention appeared in the changelog entry for 7 to 14 September and took effect on 14 September (20). Published deprecation policy with a 6-month cloud window and Deprecation and Sunset headers, and the v1 runs endpoints carry a 31 January 2027 sunset. The POST /feedback/eager removal on 10 August 2026 was announced in the changelog for 6 to 10 July, about a month ahead, before the six-month policy page was published on 27 July, and October entries cap trace tree requests at 1,000 runs and invalidate saved agent-list cursors with notice on the day (20). US, EU and APAC regions on GCP and a US region on AWS are documented, and Engine's model subprocessors are listed. We couldn't read a full subprocessor list (12). 18+20+20+12 = 70.

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.

LangSmith API + MCP 79

Personal access tokens inherit the user's permissions. Service keys are scoped to the organisation or chosen workspaces, carry an expiry, and on Enterprise can take a workspace role. Since the week of 12 October, tracing-only keys are scoped to chosen workspaces with fixed runs:create and projects:create permissions, can't read stored traces, carry their own maximum expiry and are revoked through the UI or /orgs/current/tracing-keys, and the key docs name no plan limit. The remote MCP uses OAuth 2.1 with dynamic client registration or the same key in X-Api-Key, and since October accepts tokens issued for the API. Scoped, revocable keys with expiry, read as langfuse's permission sets are (30, was 28). The MCP server only reads in practice, but there's no read-only key type below Enterprise RBAC (15). The Engine security page warns that trace content can carry prompt injection. The MCP page says nothing about it (6). Audit logs on Enterprise, queryable by API (10). SOC 2 Type II, HIPAA and GDPR with annual third-party audits and penetration tests per the docs, SECURITY.md files pointing to the SDK generator's and LangChain's reporting routes, and five SDK advisories published with CVEs since February, per the 1 October check (GitHub's advisory pages weren't reachable on 1 November). www.langchain.com answers "Invalid .well-known request" for security.txt, so none (18). 30+15+6+10+18 = 79.