## What - **template-browsing-agent**: add the `## Demo` section (in the standard position, right after "Why we built this") pointing at the existing Cloudinary demo video. The video was already registered for this template on the website but the README had no Demo section, so it never appeared for people cloning the template. - **template-chat-with-pdf** and **template-deep-search**: remove the top-of-README intro image (``) and delete the `assets/header.png` files. These two were the only templates carrying a header image, which is inconsistent with every other template and added multi-MB binaries to the repo. ## Why Template Demo sections are the convention across the templates directory; browsing-agent was the sole template with a registered video but no section to show it. The two header images were one-off inconsistencies and heavy binaries. ## Test plan - Confirmed browsing-agent's embedded video URL matches the registered `videoUrl`. - Verified the two READMEs now start cleanly with their `# Title` heading and the `assets/` directories are gone. - No package/code changes — template README + asset content only, so no changeset required. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## ELI5 This PR adds a demo video to one template and removes header images from two others. It makes the template documentation more consistent without changing application code. ## Changes - Added a `## Demo` section to `template-browsing-agent/README.md`. - Linked the Cloudinary-hosted demo video. - Removed header image references and related `assets/header.png` files from: - `template-chat-with-pdf` - `template-deep-search` - No package or code changes are included. - No changeset is required. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: mastracode <284800079+mastra-platform[bot]@users.noreply.github.com> |
History
|
|
|---|---|---|
| .. | ||
| src | ||
| .env.example | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Browser Agent
A powerful integration that combines the capabilities of Browserbase's Stagehand with Mastra for advanced web automation, scraping, and AI-powered web interactions.
Why we built this
This project enables AI agents to interact with web pages through the Mastra framework using Stagehand's browser automation capabilities. It provides tools for web navigation, element observation, data extraction, and action execution, all orchestrated through Mastra's agent system.
Demo
This demo runs in Mastra Studio, but you can connect this agent to your React, Next.js, or Vue app using the Mastra Client SDK or agentic UI libraries like AI SDK UI, CopilotKit, or Assistant UI.
Features
- Web Navigation: Navigate to websites programmatically
- Element Observation: Identify and locate elements on web pages
- Action Execution: Perform actions like clicking buttons or filling forms
- Data Extraction: Extract structured data from web pages
- Session Management: Smart session handling with automatic timeouts and reconnection
- AI-Powered Interactions: Leverage OpenAI models for intelligent web interactions
Prerequisites
- OpenAI API key — used by default, but you can swap in any model
- Browserbase API key — for page scraping
Quickstart 🚀
- Clone the template
- Run
npx create-mastra@latest --template browsing-agentto scaffold the project locally.
- Run
- Add your API keys
- Copy
.env.exampleto.envand fill in your keys.
- Copy
- Start the dev server
- Run
npm run devand open localhost:4111 to try it out.
- Run
Making it yours
Open Studio and select the "Web Assistant" agent.
About Mastra templates
Mastra templates are ready-to-use projects that show off what you can build — clone one, poke around, and make it yours. They live in the Mastra monorepo and are automatically synced to standalone repositories for easier cloning.
Want to contribute? See CONTRIBUTING.md.