Agent Tree vs Navige

Agent 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 with one command and no sign-up (20). 60 in all.

Navige 35

No machine payment protocol (0). The pricing page publishes Watchtower at $0 and paid use at the greater of $9 a month or 20 per cent of measured savings, without a login. The Terms still list exact prices, payment terms, taxes and refunds as TBD (15 of 20). Watchtower is free with no card and no time limit, per the pricing page and the Terms (20). A person signs up in a browser and confirms an email, and the Terms forbid creating accounts by automation (0).

Agent Tree 63

MIT, an OSI licence (30). PRIVACY.md is the manifest's privacy page and matches the code. Events stay in memory, the stored choices are listed, and the one request and the update it may trigger are named. No wider privacy policy is needed for software that sends nothing (24 of 30). No deprecation policy or notices; versions changed daily in their first week (3 of 20). No telemetry in the source. The update check is disclosed in the README and PRIVACY.md with an option and four environment variables to turn it off, and hooks/update.ts reads the same switches. It was added and documented on 28 October 2026, a minute apart (20). 77 in all.

Navige 50

A closed service with MIT SDKs. The Terms (version 1.0, 13 October 2026) leave prices, liability, warranties, service levels, notice periods and governing law marked TBD (5 of 30). DPA 1.2 (14 October 2026) is specific and corrects version 1.1 in public, stating that no automatic deletion runs, that prompt text through the proxy is not stored and that production data is in the United States. The privacy policy (6 October 2026) contradicts it with per-plan retention of 7 days to 1 year on plans the DPA says no longer exist, and speaks of storing masked prompts (12 of 30). No deprecation policy. The SDK 3.0.0 README lists what was removed, and the DPA promises 30 days' notice of material changes and new deletion schedules, while the Terms leave notice periods TBD (4 of 20). DPA Schedule 2 names Railway (United States), Resend, Stripe and Framer (Netherlands), with transfer safeguards. Google, whose analytics tag the website loads, isn't listed, and locations aren't given for Resend or Stripe (14 of 20).

Agent Tree 60

v0.5.4 tagged on 29 October 2026 and a commit on 31 October (30). 19 tags from v0.2.2 (24 October) to v0.5.4 (29 October), far more than three in 90 days (20). Issue and pull-request replies couldn't be read, as github.com was unreachable (5 of 25). Not in Claude's official plugin directory; claude.com/plugins/agent-tree answered 404 (0). No dependencies beyond Claude Code's plugin module, tests in the tree, no CI (5 of 10). 60 in all.

Navige 51

No dated changelog. The latest release found is navige 3.0.0 on npm on 7 September 2026, 40 days before this check (20). navige 2.0.0 (26 July), 2.0.1 (12 August) and 3.0.0 (7 September) fall within 90 days, as do three releases of n8n-nodes-navige (20). A closed service with no public changelog. Support is hello@navige.ai, with a note on each docs page that a person reads reports. The SDK repository's issues weren't readable through the GitHub API from this session (3 of 15). Not in the official MCP registry under either name. The npm SDK covers intercept() and approval status only, with 15 methods that now throw, and the Python SDK couldn't be checked (5 of 15). The SDK has no dependencies, and its repository has no CI or tests (3 of 10).

Agent Tree 50

Framework reading, docs a model can follow, as superpowers was read. types/index.d.ts types the pane's state, and plugin.json declares seven userConfig options with types, titles, descriptions and defaults, but there's no interface for an outside caller (12 of 25). README in English and German, a nine-step GUIDE.md and PRIVACY.md, all Markdown in the repository; no llms.txt (10). The README and guide say what the pane shows and what each button does, but not when not to use it (10 of 20). Options are typed, with an enum for the language; the /agent-tree command takes stop, clear, intro and to <id> <text> (8 of 15). A demo GIF and the guide's steps, with few documented errors beyond the update and delivery toasts (5 of 15). Semver tags but no changelog or release notes read (5 of 15). 50 in all.

Navige 42

No OpenAPI or other machine-readable contract. /openapi.json and /openapi return 404 and the docs link none. The MCP endpoint forwards tools from servers the customer registers and defines none of its own (0). No llms.txt on navige.ai or app.navige.ai and no Markdown versions of the docs (0). The docs say what each route does and does not do, for example that /usage gates nothing, that Watchtower changes no traffic and that error is not deny (15 of 20). /enforce and /usage have field tables with types, a required tool, a classification enum and 200-character bounds that reject rather than truncate. arguments is a free-form object (10 of 15). curl, Python and TypeScript examples on every route, the seven decision shapes, an HTTP status table, five degraded-decision cause codes and a troubleshooting table (14 of 15). No changelog, and /enforce, /usage and /mcp are unversioned paths beside /v1/transactions (3 of 15).

Agent Tree 67

Framework reading, how much a coding agent has to carry. The plugin adds no tools, skills or prompt text to the model's context. Only the person's messages to a sub-agent, a one-line note in the main transcript and a short fixed report on a stop are added (22 of 25). Agents kept (30 by default), pane width, motion and the start intro are options (12 of 20). Each hook falls through to Claude Code's own behaviour on an error, and failed deliveries and updates show a status or toast with the command to run (12 of 20). Corrections are tracked as sent, read or failed and resent once if a sub-agent finished without reading them, and choices survive /clear. A stop can't be undone (13 of 20). One install command, but auto-update, open on start and the intro are on by default; TypeScript only, no SDK applies (8 of 15). 67 in all.

Navige 61

The proxy returns the provider's response unmodified, decision responses are a few fields, and result capping, tool scoping and context trimming exist to shrink what reaches the agent's context, though all are off by default and paid only (15 of 25). The public API has no list endpoints, since logs and rules moved to the dashboard, and the output ceiling and result caps are the only size controls (8 of 20). Errors are distinct and recoverable, with four 401 reasons, 403 for an inactive or expired agent or the kill switch, 404 for an unknown provider, 429 for a budget and unavailable: true on outages (18 of 20). x-navige-transaction makes retried model calls count once and wait: false avoids a five-minute hold, but /enforce and /usage take no idempotency key. Navige adds no MCP tools of its own to annotate (10 of 20). One base URL and one header, with only tool required on /enforce. One official SDK, for Node.js, and the Python SDK named on the security page couldn't be checked (10 of 15).

Agent Tree 33

Local-package reading, as for superpowers and tokeneconomizer. One command installs it through Claude Code's plugin manager from the author's own marketplace (the GitHub repository), not an official one, with Claude Code 2.1.292 or later stated and 2.1.316 tested (15 of 20). No .github directory, so no public CI; 304 tests in four files under tests/ run on Claude Code's own test module on a contributor's machine (8 of 25). Issues couldn't be read, as github.com was unreachable from this session (5 of 25, unchecked). 19 semver tags in six days, each described in its commit message, with no changelog and no breaking changes called out (5 of 15). Version 0.5.4 (0). 33 in all.

Navige 28

Graded as a hosted service. A public Better Stack page at status.navige.ai exists, but its one monitor is api.trustloop.live/health, the host of the product's former name, and not api.navige.ai (5 of 20). That monitor shows downtime every day from 26 July to 17 October 2026 (7.221 per cent uptime) under a header saying all services are online, so there is no readable history for the current API (5). No rate-limit numbers in the docs, onboarding guide or terms (0). The docs separate a 503 outage from a 400 bug, state fail-open and fail-closed defaults per action class, return 429 for a blocking budget, pass provider errors through for the client's own retry logic, and make retries count once under x-navige-transaction. No Retry-After or backoff guidance (8 of 15). The Terms leave service levels as TBD (0). No beta or preview label on the gateway (10).