# Mirror CLI vs Traycer (slim)

> Mirror CLI and Traycer score within a point of each other for agent harnesses, 57.2 and 57 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/reflection-mirror-vs-traycer.md (~6,150 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/reflection-mirror-vs-traycer.json · canonical https://www.anchorterminal.com/compare/reflection-mirror-vs-traycer
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Mirror CLI and Traycer score within a point of each other on agent readiness, 57.2 (C) and 57 (C). Traycer leads on reliability, agent ergonomics and maintenance & community. Both do agent harnesses.

- Mirror CLI: C 57.2, rank #805 of 1510 · https://www.anchorterminal.com/tools/reflection-mirror.min.md
- Traycer: C 57, rank #816 of 1510 · https://www.anchorterminal.com/tools/traycer.min.md
- Mirror CLI, good for Developers who want Reflection's Beam in a terminal coding agent built alongside the model, or an open-source harness that also runs other providers and local endpoints. Ahead on Schema & documentation, 75 against 65; Security & auth, 58 against 42; Payments & pricing, 60 against 30; Transparency & trust, 66 against 60. Also Free to start without a card.
- Traycer, good for Teams who want several coding agents working together with shared context and boards. Ahead on Reliability, 65 against 40; Agent ergonomics, 65 against 58; Maintenance & community, 75 against 47. Also No key needed to call it.

| Category | Mirror CLI | Traycer |
| --- | --- | --- |
| Reliability (16%) | 40 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 65 |
| Agent ergonomics (13%) | 58 | 65 |
| Security & auth (14%) | 58 | 42 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 47 | 75 |
| Transparency & trust (7%) | 66 | 60 |

| Fact (where they differ) | Mirror CLI | Traycer |
| --- | --- | --- |
| Vendor | Reflection | Traycer AI |
| Auth | API key | None |
| Licence | Apache-2.0 | MIT |
| llms.txt | yes | no |
| Last release | 2026-10-16 | 2026-11-06 |
| Terms last updated | 2026-10-05 | no document linked |
| Privacy policy last updated | 2026-08-28 | no document linked |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Payments & pricing, Mirror CLI +30: Mirror CLI 60 (Self-hosted rule. No payment protocol (0). The CLI is free under Apache-2.0 with nothing to buy (20). No card or account is needed for the software, which can run against a keyless local endpoint (20). An agent can install and run it with no sign-up, given a model endpoint (20). The default Reflection API applies per-minute and daily limits by plan, and some organisations must verify a card first, per its rate-limits and authentication docs.); Traycer 30 (Scored on the paid option, Traycer's own inference subscription, whose price wasn't read (0 of 20). No protocol (0). Bring-your-own-agent use is free (20). Accounts for sync and teams weren't checked, half (10). 0 + 0 + 20 + 10 = 30.)
- Maintenance & community, Traycer +28: Mirror CLI 47 (0.1.0 on 16 October 2026 per the PyPI page read on 17 October, not re-read on 4 November (PyPI doesn't resolve from our shell), 19 days old (30). The 90-day line needs three dated releases. 0.1.0 (16 October) and the `mirror-agent-v0.1.8` tag on the same commit, f938033, are one release day, and 0.1.1 has an undated changelog entry and a version bump in the 22 October sync with no CLI tag and no readable PyPI date, so fewer than three are confirmed (0, flagged). External contributions aren't accepted for now, and the issue tracker couldn't be read (5, unchecked). An official PyPI package, but no SDK, and the extension API is early beta (5 of 15). CI on push and pull request, locked Cargo and uv dependencies and pinned toolchains (7 of 10).); Traycer 75 (Commits on 6 November 2026 and host 1.5.3 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current apps and CLI packages (15). CI with tests (10). 30 + 20 + 0 + 15 + 10 = 75.)
- Reliability, Traycer +25: Mirror CLI 40 (Local-package reading. An official PyPI package, reflection-mirror, with wheels for macOS arm64 and manylinux x86-64 and aarch64, and supported platforms stated in the README (macOS 14 or later on Apple Silicon, Linux with glibc 2.28 or later, Python 3.12 or later) (20). A public CI workflow runs the Python package tests (ci.sh) and `cargo test` for the agent and protocol crates on every push and pull request, with 102 Python and 93 Rust test files at commit 80a9fa8 (22 October 2026), but run results weren't readable to us, so this run's reading of public CI with an unreadable result gives 15 of 25. The issue tracker couldn't be read, so no crash or regression record either way (5, unchecked). A CHANGELOG.md now lists 0.1.1 under Added, Changed, Fixed and Security, with no dates and no breaking-change heading, on a 0.x version (0, flagged). 0.1.x, labelled early beta in the docs (0).); Traycer 65 (Local software. Builds for macOS, Linux and Windows, and package-manager publishing workflows (20). test.yml, CodeQL, OpenSSF Scorecard and secret scanning run on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Host 1.5.3 (15). 20 + 15 + 0 + 15 + 15 = 65.)
- Security & auth, Mirror CLI +16: Mirror CLI 58 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Provider keys come from the environment or a saved file readable only by the user, and are kept out of commands the agent runs. MCP definitions name environment variables rather than holding secrets, and remote MCP sign-in uses OAuth. Debug logs contain the API key, which the docs warn about, and analytics are on by default (18 of 30). Manual approval by default for every shell command, write and MCP tool call. Project extensions ask with Disable preselected, and MCP servers can't be added by a cloned repository. Auto mode, once chosen, applies in every directory (15 of 20). SECURITY.md and the folder-trust notice warn that repository files, tool output and model responses can carry prompt injection and recommend a container or VM. The microVM sandbox is opt-in and covers file and shell tools only (9 of 15). Conversations with their tool calls are kept in `~/.mirror/state.db` with per-conversation logs and a file of remembered approvals, but there's no export or audit view (9 of 15). SECURITY.md gives a private email and a report scope, but there's no security.txt, bug bounty or published advisory (7 of 20). Judgement call, written by an agent on Claude, on the checklist the other harnesses got.); Traycer 42 (Harness reading. Code is processed in memory and not used for training, but Privacy Mode is opt-in for individuals, prompts may be logged with it off, and Sentry and PostHog 'may be enabled in release builds' (10 of 30). No approval model described in the README (8 of 20). No prompt-injection guidance (5). No audit log found (5). SECURITY.md, CodeQL, Scorecard and secret scanning (14 of 20). 10 + 8 + 5 + 5 + 14 = 42.)
- Schema & documentation, Mirror CLI +10: Mirror CLI 75 (Framework reading. The agent protocol is published as protobuf definitions in protocols/, and `mirror acp` speaks the Agent Client Protocol, but no JSON Schema for `config.json` or the MCP definition files was found (15 of 25). llms.txt with a Markdown copy of every page (10). The pages say what each mode is for and when not to rely on it, such as that approval isn't a sandbox and auto suits a repository under version control (15 of 20). Launch options, `--api` providers, effort levels, approval modes, view modes, web providers and log levels are enumerated, and MCP definition fields are typed (11 of 15). Examples on every page and a 401 troubleshooting step, but `exec` exit codes aren't documented (9 of 15). Versions with a stated tag scheme (`reflection-mirror-vX.Y.Z` for the CLI, `mirror-agent-vX.Y.Z` for the agent) and a public CHANGELOG.md in the repository since 22 October 2026 (15).); Traycer 65 (Harness reading. Mintlify docs, a protocol package and a CLI (65).)
- Agent ergonomics, Traycer +7: Mirror CLI 58 (Framework reading, adapted to a harness driven by a pipeline. `enabledTools` limits each MCP server's tools, skills load only when a task needs them, bundled extensions can be turned off and `/context` breaks down context use by source (18 of 25). `--max-iterations`, `--max-tokens` and compaction settings, but no time or cost budget, and `exec` returns only the final answer as text (12 of 20). `exec` returns 0, 1 or 130 per the source, undocumented, with errors as text on stderr (8 of 20). Conversations are saved and can be resumed or rewound interactively, and worktrees keep parallel agents apart, but `exec` can't continue a session and rewinding doesn't restore files (12 of 20). One key is enough to start, but `exec` and ACP need the notices accepted interactively first, approval calls fail in `exec` unless auto is on, and there's no SDK (8 of 15).); Traycer 65 (Harness reading. Model switching within an agent, agent-to-agent loops, a CLI and cross-device sync (65).)