Mastra’s Core 1.78.0 release adds scopes for identifying an agent’s resource and conversation thread, while Sim v0.9.26 adds project-file access in chat. The updates offer two approaches: controls in application code or a shared visual workspace for building and monitoring workflows.
Mastra adds resource and thread scopes for agent calls
Mastra’s Core 1.78.0 release, published October 16 UTC, supports scopes named for a resource or thread. An application can set them on an agent or pass them for one call; memory uses them to choose the resource and conversation thread. A mismatch between a scope and memory’s configured resource or thread makes the call fail with HTTP 400 rather than silently choosing one. A resumed run keeps its original scopes. For a multi-tenant product, that makes context routing more explicit, but the release does not define an application’s authorization policy.
The release also adds a way to queue a structured signal behind an active agent run while preserving its type, tag and attributes instead of turning it into a user message. The run’s trace, its recorded sequence of execution events, shows which signal started it. A separate API groups these traces by supported fields. Developers still need to decide how those records are stored and monitored.
Sim adds project files to chat and rolls out computer use per organization
Sim v0.9.26, released October 17 UTC, adds read and write access to project files from chat. Its release notes say computer use is rolling out per organization, so access remains staged. The same release removes a client log-persistence route. The linked fix says the person who started a run could have used it to overwrite a finished run’s status, output and trace data, and to add client-supplied costs to the payer’s usage ledger. Its only caller returned 404, and maintainers say no logs were persisted, so removing the route did not change existing behavior.
Sim’s README offers a hosted option and a self-hosted setup. Running it yourself requires Node.js 20 or newer, Docker and a chat API key; its setup wizard creates a local deployment and starts the published images. The repository is Apache-2.0 licensed, but that does not set the terms or price of Sim’s hosted service or connected model providers.
Mastra embeds agents in code; Sim offers a shared visual workspace
Mastra is a code-first framework for developers embedding agents in an application. Sim is a shared workspace for teams that want to assemble and monitor workflows visually. Mastra’s repository says most code is Apache-2.0, while code in directories named ee/ needs a valid Mastra Enterprise License for production use. Both projects describe their own capabilities; these release notes are not an independent performance or security evaluation.
Neither update removes the need to test how data, credentials and tool permissions flow through a real product. Compare the exact provider fees and license terms for the features a team plans to use before choosing a deployment.
Sources
Mastra Core 1.78.0 release notes; Mastra README; Mastra LICENSE.md; Sim v0.9.26 release notes; Sim pull request #9183, log-route fix; Sim README; Sim LICENSE.
Image credit: Screenshot of the Sim platform from the project’s README at the captured repository revision; repository materials are licensed under Apache License 2.0.