AgentOS vs Mastra

AgentOS 74

An agent is about five lines with the provider detected from the environment, and capability discovery selects tools by meaning, but no MCP client was found in the package source on 1 November or in the docs sitemap, which this line is read on for a framework (12). Session history is capped at about 120K tokens by default, with history.maxTokens, reseed() and maxSteps (20). Typed error classes and a fallbacksUsed field on results, with error documentation spread across pages (14). Checkpoints replay or re-run a node by its declared effect class on resume, and providers fall back in order, though the shipped checkpoint store is in memory (18). Few required options, TypeScript only (10).

Mastra 92

An MCP client in about ten lines with listTools() for static or listToolsets() for per-request tools, and ToolSearchProcessor for loading tools on demand (25). Step limits, memory windows and processors such as a token limiter control what reaches the model (20). MastraError with ids and categories, and processors can abort with a reason the caller can read (17). Workflow step retries, snapshots and durable agents for resuming (20). create-mastra scaffolds a project and the model router takes a plain string, but it's TypeScript only (10).

AgentOS 81

No analytics or telemetry code found in the source, and the privacy and security pages say the runtime sends nothing to the vendor. OpenTelemetry is off by default and the host installs the exporter (30). Approval gates on five triggers, five security tiers and a rule that composed tools chain a side-effecting step only when the host lists it. Agent-written code runs by default in an in-process node:vm context with a 5-second limit and no memory cap, off unless the host enables it. An optional QuickJS executor runs each call in its own WebAssembly instance with a memory cap. No gate is on unless configured (17). SECURITY.md names model output, tool results and retrieved content as untrusted input, and injection detection is an opt-in extension pack. The security page says that pack's default ONNX model has no prompt-injection label, so injection is scored only when that model can't load, and points to a phrase-list guard (11). OpenTelemetry spans, a usage ledger, a reasoning trace and an opt-in signed audit log (15). SECURITY.md with a private advisory form, acknowledgement in 5 business days and disclosure at 90 days, and the site's security page now gives the same times. No security.txt, no bounty and no published advisory found (8). Framework reading.

Mastra 67

The CLI sends PostHog analytics, server startup sends token counts per model and a count of registered agents, tools and MCP servers, and Studio sends browser analytics, all on by default and documented, with one opt-out, MASTRA_TELEMETRY_DISABLED=1. Since #26986 (16 October 2026) each server process also reports token use per provider and model every 15 minutes, and the telemetry reference read on 6 November says server events carry a project identifier that is a raw Platform UUID or a hash of the Git origin remote, so they "aren't anonymous" (12). requireToolApproval on agents and MCP servers, allowedHosts for MCP HTTP, a curated environment for stdio servers, and sandboxed workspaces (20). PromptInjectionDetector, PII and moderation processors, and docs that call tool results untrusted model input (15). Built-in tracing with OpenTelemetry and other exporters (15). No SECURITY.md, no security.txt and no bug bounty found. A blog post says Mastra is SOC 2 Type II audited, which isn't scored for a framework, and we found no public advisory from Mastra about the June incident (5). Framework reading. 15+20+15+15+5 = 70 on 6 October, 12+20+15+15+5 = 67 on 6 November.

AgentOS 77

Official npm package with Node 22 or newer stated in package.json on 1 November (20). A public CI workflow builds, lints, type-checks and runs the tests with coverage, and the 12 most recent runs on master on 8 October 2026 passed, per the 8 October check, not re-read on 1 November (25). 16 open issues and pull requests in total, most filed by the maintainer, with one outside suggestion from 12 September unanswered, per the 8 October check, not re-read on 1 November (20). Written release rules give a breaking change a minor version, and a workflow fails a pull request with a breaking-change marker unless a maintainer approves it, but feature commits ship as patches and breaking minors 0.11.0 and 0.12.0 (7 October), 0.13.0 (8 October), 0.14.0 (17 October) and 0.15.0 (21 October, two persona changes marked BREAKING CHANGE) landed within two weeks (12). Version 0.15.69, not declared stable (0). Local-software reading.

Mastra 87

Official npm packages, Node 22.13 or newer (20). Public CI workflows for unit, store, workspace and e2e tests; on 6 November the newest runs on main (Version Packages, Trigger Cloud Integration Tests) succeeded, while the test workflows themselves run on pull requests (22). 436 open issues and 795 open issues and pull requests on 6 November from GitHub's API, with 2,077 issues opened in the 90 days to 3 November; all 50 newest had a comment and 24 were closed, with issue-triage automation (18). A changesets CHANGELOG per package, a CI gate that needs approval for any major bump and migration guides, but no written versioning policy found, and .network() is deprecated without a removal date (12). 1.82.0 (15). 20+22+18+12+15 = 87, up from 74 on 6 October, when GitHub couldn't be read.

AgentOS 87

0.15.69 tagged on 2026-10-31 (30). 333 release tags in the 90 days to 1 November and 95 after 0.14.2, read from the repository because npm didn't resolve from the shell (20). Little outside traffic to judge by. Of 244 commits since 17 October, all but four are by the maintainer. Per the 8 October check, not re-read on 1 November, two outside issues were closed with five comments each and one outside suggestion had been open without a reply since 12 September (15). The npm package is current by its tags, though the registry couldn't be read on 1 November (15). CI and coverage run on every push, but the workflows have no npm audit step and the repository has no Dependabot configuration file. The security page says Dependabot alerts are on in the repository settings, which we can't see (7).

Mastra 96

@mastra/core 1.82.0 on 2026-11-04 (30). 27 stable releases in the 90 days to 6 November, 8 of them since 6 October (20). 436 open issues on 6 November, all 50 newest issues commented and 24 of them closed (22). Client, MCP and store packages are current, and @mastra/mcp 1.x stays supported beside 2.x (15). Renovate and CI configured, with the newest runs on main passing (9). 30+20+22+15+9 = 96.

AgentOS 92

Typed TypeScript API with a TypeDoc reference (25). llms.txt on agentos.sh and docs.agentos.sh (10). The guides say which surface to reach for, for example agency-level approval for most apps and workflow nodes for an explicit graph, and the tool-forging docs state what each executor does not isolate (16). Tools take Zod schemas (15). 22 runnable examples and a cookbook, with CLI error codes documented but no single page for the library's error classes found (11). Release notes are generated for every release and published as GitHub releases under written version rules. The CHANGELOG.md on master still stops at 0.13.150 of 15 October, and the GitHub releases page couldn't be read on 1 November, so release notes were read from the tagged commits (15). Framework reading.

Mastra 98

Typed TypeScript API with a reference section (25). llms.txt with a when-to-use list and condensed instructions for coding agents (10). The docs say when to use durable agents, and point multi-agent users from .network() to supervisor agents (20). Tools take Zod schemas (15). Examples on every page, and MastraError with ids and categories documented, though errors are spread across pages (13). Per-package changelogs and migration guides (15).