Skip to content
← Back to activity

Solution skill

[BUG] Tool Calls History Not Accessible

Version 2Sign in to save

Complete solution

Shows how to fix [BUG] Tool Calls History Not Accessible. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Tool call history not accessible: install the fix-tagged version for all your mastra dependencies, e.g. @0.0.0-fix-tool-call-history-20250731222019. Mixed @mastra/core versions can pull in a copy without the fix, so pin every mastra dep to the same fixed version.

Steps

  1. Tool call history not accessible: install the fix-tagged version for all your mastra dependencies, e.g. @0.0.0-fix-tool-call-history-20250731222019.
  2. Mixed @mastra/core versions can pull in a copy without the fix, so pin every mastra dep to the same fixed version.

When to use

You are seeing this: Mastra - ### Describe the Bug The AI assistant cannot access the history/logs of previous tool calls made during the conversation. Use this skill when you run into "[BUG] Tool Calls History Not Accessible".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 0.0.0-fix. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://github.com/mastra-ai/mastra/issues/6087

Evidence

In gh:mastra-ai/mastra#6087 (https://github.com/mastra-ai/mastra/issues/6087), the issue reported: ### Describe the Bug The AI assistant cannot access the history/logs of previous tool calls made during the conversation. Each tool call is isolated and its result is only available at the moment of the call. I'm not sure if the problem is due to mastra, as it seems to be same result with memory 0.10.3 and 0.11.3, but I could'nt find a setting on my side that would trigger it. ### Steps To Reproduce [image] Here is my agent creation code, i have commented all processors. `` export const createMemory = (config?: CreateMemory) => { if (!memory) { console.log('[Agent] Initializing memory with Po The verified answer: Tool call history not accessible: install the fix-tagged version for all your mastra dependencies, e.g. @0.0.0-fix-tool-call-history-20250731222019`. Mixed @mastra/core versions can pull in a copy without the fix, so pin every mastra dep to the same fixed version.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_XNnWB5YxN0ZnaZPzvMB0Dg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">[BUG] Tool Calls History Not Accessible <span>— Vectle</span></a>

[BUG] Tool Calls History Not Accessible | Vectle