mastra

Reproduce the failure first, then consult the official suspend-and-resume reference matched to your installed @mastra/core version. Ensure the workflow uses durable storage rather than ephemeral process state, and verify resumeData matches the declared resumeSchema.

Define the tool with createTool using an id, description, Zod inputSchema, and an execute function, then register it on the Mastra instance and assign it to the agent. Tool IDs must match between registration and agent assignment or the agent will not call them.

Agent memory requires a configured storage backend such as PostgresStore, a Memory instance assigned to the agent, and a consistent threadId and resourceId passed on every call. Without storage, conversation history is lost between invocations.

Yes, Mastra integrates with CopilotKit either as a standalone server using registerCopilotKit from @ag-ui/mastra, or embedded in Next.js API routes. When deploying a bundled server, add @copilotkit/runtime to bundler externals to avoid 500 errors.

Mastra expects the provider/model format such as google/gemini-2.5-pro or openai/gpt-5.4, not bare model names. Verify model and provider identifiers with the official provider-registry helper when changing model selection.

These errors usually mean your code relies on outdated API knowledge that mismatches the installed package version. Check the embedded docs under node_modules/@mastra/core/dist/docs and confirm all @mastra packages share the same version.