build(deps): bump @mastra/memory from 1.26.2 to 1.27.0

[dependabot]

Bumps @mastra/memory from 1.26.2 to 1.27.0.

Release notes

Sourced from @​mastra/memory's releases.

April 23, 2026

Highlights

CLI-Driven Browser Automation + Screencasts

@mastra/core and the new @mastra/browser-viewer package add end-to-end browser automation for CLI-based agent workflows. BrowserViewer launches Chrome via Playwright with remote debugging, and a new BrowserCliHandler automatically detects browser CLIs (agent-browser, browser-use, browse) and injects the CDP URL into commands — no manual wiring needed. Browser sessions are thread-isolated with automatic lifecycle management, and live screencasts stream directly to Studio. External CDP endpoints (e.g. browser-use cloud) are also supported: the system detects them, skips injection, and connects for screencast.

S3 “Prefix Mounts” Across Workspace Providers

Workspace packages (@mastra/s3, @mastra/daytona, @mastra/e2b, and @mastra/blaxel) now support mounting an S3 subdirectory via a prefix option, so sandboxes can expose only a folder within a bucket instead of the entire bucket.

More Robust Workflow Resumes for Parallel foreach

Fixes a workflow snapshot/resume bug where parallel foreach iterations could lose their suspendPayload when a sibling iteration resumed—important for HITL/tool-approval flows that rely on preserved per-iteration stream state.

Observational Memory Improvements (Temporal Markers + Correctness Fixes)

Adds opt-in temporal-gap markers (observationalMemory.temporalMarkers: true) to inject persisted <system-reminder type="temporal-gap"> when users return after 10+ minutes, and fixes duplication/conflicts by force-disabling savePerStep when observational memory is enabled.

New Package: @mastra/tavily

New integration package wrapping @tavily/core as first-class Mastra tools — createTavilySearchTool, createTavilyExtractTool, createTavilyCrawlTool, and createTavilyMapTool — with full Zod input/output schemas, lazy client initialization, and a convenience createTavilyTools() that returns all four with shared config. API key resolves from config or TAVILY_API_KEY env var.

Breaking Changes

• None noted in this changelog.

Changelog

@​mastra/core@1.27.0

Minor Changes

• Added support for CLI-driven browser automation with screencast support in @mastra/core, including automatic CDP injection for browser CLIs. (#15415)

  Fixed local process spawning so workspace-relative cwd values no longer get duplicated.

Patch Changes

• Update provider registry and model documentation with latest models and providers (f112db1)

• Fixed foreach parallel iterations losing their suspendPayload when a sibling iteration was resumed. Previously, every result entry written back to the workflow snapshot had its suspendPayload cleared, so iterations that were still suspended (e.g. parallel tool-call approvals each carrying an agent's __streamState) lost the context they needed to resume correctly. Suspended iterations now retain their suspendPayload across resume cycles; completed iterations still have it cleared to keep snapshots small. (#15551)

  const approvalWorkflow = createWorkflow({ id: "approve" }).foreach(approveToolStep, { concurrency: 5 }).commit();
  // Before: resuming the first approval wiped streamState on the others,
  //         so subsequent resumes lost conversation context.
  // After:  each suspended iteration keeps its suspendPayload (including
  //         streamState) until it is individually resumed.

... (truncated)

Changelog

Sourced from @​mastra/memory's changelog.

1.27.0

Minor Changes

• Added continuationHints to observational memory configuration, so an agent that drives its (#20665) own control flow can stop memory from proposing what it says next.

  <current-task> and <suggested-response> were always requested and there was no way to turn them off. A <suggested-response> is injected into the agent's context and the continuation reminder tells the agent to follow it, which makes memory a second controller competing with the agent's own. Pass false to disable both sections, or an object to disable them individually — keeping <current-task> while dropping <suggested-response> is the common case.

  import { Memory } from '@mastra/memory';
  const memory = new Memory({
  options: {
  observationalMemory: {
  observation: { continuationHints: { suggestedResponse: false } },
  reflection: { continuationHints: false },
  },
  },
  });

  Disabling a section removes it fully: the Observer and Reflector no longer describe or reference it, and a previously stored hint stops being injected into the agent's context once both observation and reflection disable it.

  Defaults are unchanged — existing configurations keep both sections enabled.

• Added foundational support for an upcoming experimental memory capability across storage, runtime, and developer tooling. (#19538)

Patch Changes

• Added settled() to the base memory class. Memory implementations can do work in the background after an agent run returns, and this gives callers a way to wait for it before closing a storage connection they own. The default implementation does nothing; @mastra/memory overrides it. (#21708)

• Added memory.settled(), which waits for background memory work to finish. Observational memory runs observation and reflection cycles in the background after an agent run returns, and those cycles kept writing to the database after callers had closed their storage connection. Await memory.settled() before closing a store you own. Fixed the observational memory reflector repeating compression attempts that could not succeed: it now stops as soon as an attempt returns the same result as the previous one, instead of always working through the full retry ladder. This cuts the model calls and database statements a single reflection produces. Fixes #21617 (#21708)

• Restored the Studio memory bar token counts after a reload by reading them from the stored observational memory record. (#21604)

• Log discarded degenerate observer/reflector output so failures are diagnosable. When observational memory's degenerate-repetition detector trips, the raw model output was previously thrown away — the error "Observer produced degenerate output after retry" gave no way to tell a real repetition loop apart from a detector false-positive on legitimately repetitive content. Detection sites now log bounded diagnostics (length, duplicate-window ratio, most-repeated window, head/tail snippets) to the OM debug log, and the thrown observer errors include a compact version of the same diagnostics. (#21807)

• Fixed schema-based working memory so that null consistently deletes a field. Previously, a null only removed a field that already existed: on the very first write, or inside a nested object created for the first time, the null was stored literally. This mattered because strict-mode model providers pad every field they are not updating with null, so a first write could be saved as { "role": null }. Working memory updates are also no longer stored by reference to the object passed in. (#21687)

• Fixed MockMemory so its working memory merge keeps parity with @mastra/memory: a null now deletes a field on the first write and inside newly created nested objects, instead of being stored literally. (#21687)

• Fixed observational memory removing Markdown link labels from the observation (#20665)

... (truncated)

Commits

• c23d445 chore: version - exit prerelease mode
• 694bd68 fix(memory): log discarded degenerate observer output for diagnosis (#21807)
• d9484ad chore: version packages (alpha) (#21791)
• 2ef2f23 feat(memory): surface scoped Subconscious activity (#19538)
• 4004902 feat(memory): capture scoped knowledge with Subconscious OM (#19537)
• e2a8b34 chore: version packages
• b0a2a07 Wait for background memory work with memory.settled(), and stop the reflector...
• 9f62669 chore: version packages (alpha) (#21597)
• 7f78585 Cover cross-thread message loading for resource-scoped observational memory (...
• f2a4afd Fix working memory storing literal null placeholders on the first write (#21687)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1104.