docs: Add Mastra integration guide#447
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Greptile SummaryThis PR adds a new guide for building agents with Mastra and Tigris, covering workspace provisioning, dataset forks, checkpoints, and coordination. The guide is well-structured with clear step-by-step examples, appropriate callouts for pre-1.0 stability and TTL safety, and a matching Excalidraw architecture diagram. Confidence Score: 4/5Safe to merge; two minor P2 style findings with no functional impact. Only P2 style-rule findings: one redundant diagram caption and one inline warning that should be a callout. No logic errors, broken links, or incorrect code examples found. docs/agents/agent-mastra.mdx — caption and inline-warning callout style issues. Important Files Changed
Reviews (1): Last reviewed commit: "add guide" | Re-trigger Greptile |
1dc7d40 to
ac6128e
Compare
PREVIEW
Adds a new docs page at docs/agents/agent-mastra.mdx walking developers through using @tigrisdata/agent-kit with Mastra, the TypeScript agent framework.
The guide uses the orchestrator pattern end-to-end: your code calls Agent Kit to provision a workspace (or fork a dataset), hands the resulting bucket and scoped credentials to the agent through Mastra's RequestContext, runs the agent, and tears storage down — even if the run throws. This keeps the LLM out of infrastructure decisions and keeps credentials out of the prompt context.
Eight steps cover install through cleanup, including a single-agent workspace example, a multi-agent eval pattern that forks a dataset 5× for parallel runs, and an optional coordination section that fires a webhook when an agent writes to a watched prefix.