feat: Enhance tool progress reporting and add new agents/tools

- Updated the test generator tool to include detailed progress reporting with status and stage identifiers.
- Modified the weather tool to improve progress messages, including status updates for various stages of the weather lookup process.
- Enhanced the web scraper tool with structured progress reporting, adding status and stage information for each step of the scraping process.
- Refactored the document processing workflow to include detailed progress reporting for each step, improving error handling and logging.
- Updated the research synthesis workflow to provide structured progress updates, including status and stage identifiers for each research step.
- Added a new background color agent that converts colors to HEX format and changes the application's background color.
- Introduced a new color change tool that allows changing the background color based on user input.
- Improved the spec generation workflow to handle JSON extraction more robustly.
- Enhanced the weather workflow to include detailed progress reporting for fetching weather data and planning activities based on weather conditions.

Author: ssdeanx

.github/agents/4.1-Beast.agent.md

@@ -1,9 +1,9 @@
 ---
-description: 'GPT 4.1 as a top-notch coding agent.'
-name: '4.1 Beast Mode v3.1'
+name: 'Beast Mode v4.0'
+description: 'GPT 5.1 as a top-notch coding agent.'
 infer: true
-argument-hint: 'Solve complex coding problems autonomously using advanced cognitive techniques and extensive internet research.'
-tools: ['vscode', 'execute', 'read', 'edit', 'search', 'web', 'agent', 'lotus/*', 'mastrabeta/mastraBlog', 'mastrabeta/mastraChanges', 'mastrabeta/mastraDocs', 'mastrabeta/mastraExamples', 'mastrabeta/mastraMigration', 'multi_orchestrator/*', 'next-devtools/*', 's-ai/*', 'thoughtbox/*', 'docfork/*', 'vscode.mermaid-chat-features/renderMermaidDiagram', 'updateUserPreferences', 'memory', 'malaksedarous.copilot-context-optimizer/askAboutFile', 'malaksedarous.copilot-context-optimizer/runAndExtract', 'malaksedarous.copilot-context-optimizer/askFollowUp', 'malaksedarous.copilot-context-optimizer/researchTopic', 'malaksedarous.copilot-context-optimizer/deepResearch', 'ms-python.python/getPythonEnvironmentInfo', 'ms-python.python/getPythonExecutableCommand', 'ms-python.python/installPythonPackage', 'ms-python.python/configurePythonEnvironment', 'ms-vscode.vscode-websearchforcopilot/websearch', 'todo', 'search/changes', "search/codebase", "edit/editFiles", 'vscode/extensions', 'web/githubRepo', 'vscode/openSimpleBrowser', 'read/problems']
+target: github-copilot
+tools: ['vscode', 'execute', 'read', 'edit', 'search', 'web', 'lotus/*', 'mastrabeta/mastraBlog', 'mastrabeta/mastraChanges', 'mastrabeta/mastraDocs', 'mastrabeta/mastraExamples', 'mastrabeta/mastraMigration', 'multi_orchestrator/*', 'next-devtools/*', 's-ai/*', 'thoughtbox/*', 'docfork/*', 'agent', 'vscode.mermaid-chat-features/renderMermaidDiagram', 'updateUserPreferences', 'memory', 'malaksedarous.copilot-context-optimizer/askAboutFile', 'malaksedarous.copilot-context-optimizer/runAndExtract', 'malaksedarous.copilot-context-optimizer/askFollowUp', 'malaksedarous.copilot-context-optimizer/researchTopic', 'malaksedarous.copilot-context-optimizer/deepResearch', 'ms-python.python/getPythonEnvironmentInfo', 'ms-python.python/getPythonExecutableCommand', 'ms-python.python/installPythonPackage', 'ms-python.python/configurePythonEnvironment', 'ms-vscode.vscode-websearchforcopilot/websearch', 'todo']
 ---
 
 You are an cutting edge autonomous coding agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user. Never end your turn until the problem is fully solved, so never assume your correct. Make sure to verify your solution thoroughly.
@@ -93,7 +93,7 @@ Carefully read the issue and think hard about a plan to solve it before coding.
 - Whenever you detect that a project requires an environment variable (such as an API key or secret), always check if a .env file exists in the project root. If it does not exist, automatically create a .env file with a placeholder for the required variable(s) and inform the user. Do this proactively, without waiting for the user to request it.
 
 ## 7. Debugging
-- Use the `get_errors` tool to check for any problems in the code
+- Use the `'read/problems'` tool to check for any problems in the code
 - Make code changes only if you have high confidence they can solve the problem
 - When debugging, try to determine the root cause rather than addressing symptoms
 - Debug for as long as needed to identify the root cause and identify a fix
@@ -105,8 +105,19 @@ Carefully read the issue and think hard about a plan to solve it before coding.
 Use the following format to create a todo list:
 ```markdown
 - [ ] Step 1: Description of the first step
+   - [ ] Sub-step 1.1: Description of the first sub-step
+   - [ ] Sub-step 1.2: Description of the second sub-step
 - [ ] Step 2: Description of the second step
+   - [ ] Sub-step 2.1: Description of the first sub-step
+   - [ ] Sub-step 1.2: Description of the second sub-step
 - [ ] Step 3: Description of the third step
+   - [ ] Sub-step 3.1: Description of the first sub-step
+- [ ] Step 4: Description of the fourth step
+   - [ ] Sub-step 4.1: Description of the first sub-step
+- [ ] Step 5: Description of the fifth step
+- [ ] Step 6: Description of the sixth step
+- [ ] Step 7: Description of the seventh step
+- [ ] Step 8: Description of the eighth step
 ```
 
 Do not ever use HTML tags or any other formatting for the todo list, as it will not be rendered correctly. Always use the markdown format shown above. Always wrap the todo list in triple backticks so that it is formatted correctly and can be easily copied from the chat.
@@ -124,7 +135,7 @@ Always communicate clearly and concisely in a casual, friendly yet professional
 "Whelp - I see we have some problems. Let's fix those up."
 </examples>
 
-- Respond with clear, direct answers. Use bullet points and code blocks for structure. - Avoid unnecessary explanations, repetition, and filler.  
+- Respond with clear, direct answers. Use bullet points and code blocks for structure. - Avoid unnecessary explanations, repetition, and filler.
 - Always write code directly to the correct files.
 - Do not display code to the user unless they specifically ask for it.
 - Only elaborate when clarification is essential for accuracy or user understanding.
@@ -152,3 +163,14 @@ Remember that todo lists must always be written in markdown format and must alwa
 If the user tells you to stage and commit, you may do so.
 
 You are NEVER allowed to stage and commit files automatically.
+
+# Final Instructions
+
+@runSubagent Expert Next.js Developer "Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript"
+@runSubagent Expert React Frontend Engineer "Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization"
+@runSubagent ADR-Generator "Expert agent for creating comprehensive Architectural Decision Records (ADRs) with structured formatting optimized for AI consumption and human readability."
+@runSubagent QA-Agent "QA Agent designed to meticulously validate solutions across various dimensions such as functionality, usability, performance, security, scalability, and maintainability."
+@runSubagent Task Planner "Task Planner agent adept at breaking down complex tasks into manageable subtasks, prioritizing them based on urgency and importance, and tracking their completion status."
+@runSubagent Task Researcher "Task Researcher agent skilled in conducting in-depth research to gather relevant information, best practices, and potential solutions for assigned tasks."
+@runSubagent Debug Agent "Debug Agent specialized in identifying, diagnosing, and resolving complex software issues through systematic analysis and testing."
+@runSubagent Technical Spike "Technical Spike agent focused on exploring new technologies, frameworks, or methodologies to assess their feasibility and potential impact on projects."

.github/agents/Thinking-Beast-Mode.agent.md

@@ -163,7 +163,7 @@ Carefully read the issue and think hard about a plan to solve it before coding.
 
 ## 8. Debugging
 
-- Use the `get_errors` tool to identify and report any issues in the code. This tool replaces the previously used `#problems` tool.
+- Use the `'read/problems'`  tool to identify and report any issues in the code. This tool replaces the previously used `get_errors` tool.
 - Make code changes only if you have high confidence they can solve the problem
 - When debugging, try to determine the root cause rather than addressing symptoms
 - Debug for as long as needed to identify the root cause and identify a fix

package-lock.json

@@ -77,6 +77,7 @@
     "@monaco-editor/react": "^4.8.0-rc.3",
     "@next/bundle-analyzer": "^16.0.10",
     "@next/mdx": "^16.0.10",
+    "@octokit/plugin-retry": "^8.0.3",
     "@openrouter/ai-sdk-provider": "^1.5.3",
     "@opentelemetry/api": "^1.9.0",
     "@opentelemetry/exporter-trace-otlp-proto": "^0.208.0",
@@ -215,4 +216,4 @@
     "body-parser": "^2.2.1",
     "jws": "^4.0.1"
   }
-}
+}

package.json

@@ -0,0 +1,18 @@
+import { Agent } from "@mastra/core/agent";
+import { Memory } from "@mastra/memory";
+import { colorChangeTool } from "../tools/color-change-tool";
+
+export const bgColorAgent = new Agent({
+  id: "bg-color-agent",
+  name: "Background Color Agent",
+  description:
+    "This agent takes in a color, converts it to HEX format and changes the background color of the application.",
+  instructions: `
+      You are a helpful assistant to change the background color of the application.
+      You will be given a color in any format (e.g., "red", "rgb(255, 0, 0)", "hsl(0, 100%, 50%)").
+      Your task is to convert this color to HEX format (e.g., "#FF0000") and call the colorChangeTool with the HEX color.
+`,
+  model: "openai/gpt-4o-mini",
+  tools: { colorChangeTool },
+  memory: new Memory(),
+});

src/mastra/agents/bgColorAgent.ts

@@ -0,0 +1,16 @@
+import { createTool } from "@mastra/client-js";
+import z from "zod";
+
+export function changeBgColor(color: string) {
+  if (typeof window !== "undefined") {
+    document.body.style.setProperty("--background", color);
+  }
+}
+
+export const colorChangeTool = createTool({
+  id: "changeColor",
+  description: "Changes the background color",
+  inputSchema: z.object({
+    color: z.string(),
+  }),
+});

src/mastra/color-change-tool.ts

@@ -4,7 +4,7 @@ import { logError } from './logger'
 //import { GoogleVoice } from "@mastra/voice-google";
 import { GoogleGenerativeAIImageProviderOptions } from '@ai-sdk/google';
 import { experimental_generateImage as generateImage } from 'ai';
-
+import { GoogleVoice } from "@mastra/voice-google";
 // Initialize with custom configuration
 //export const gvoice = new GoogleVoice({
 //  speechModel: {
@@ -43,6 +43,17 @@ export const google = createGoogleGenerativeAI({
     apiKey: process.env.GOOGLE_GENERATIVE_AI_API_KEY,
 })
 
+// Google Voice Configuration
+export const voice = new GoogleVoice({
+  speechModel: {
+    apiKey: process.env.GOOGLE_API_KEY,
+  },
+  listeningModel: {
+    apiKey: process.env.GOOGLE_API_KEY,
+  },
+  speaker: "en-US-Casual-N",
+});
+
 // Chat/Text Models
 export const googleChatModels = {
   // Gemini 3 Pro model for higher-performance applications

src/mastra/config/google.ts

@@ -7,7 +7,7 @@
 
 ## Persona
 
-**Name:** Senior Tooling & Integrations Engineer  
+**Name:** Senior Tooling & Integrations Engineer
 **Role Objective:** Provide minimal, secure, schema-bound callable functions enabling agent actions with clear natural language affordances.
 
 ## Purpose
@@ -77,6 +77,8 @@ Encapsulate 30+ atomic operational capabilities (security checks, vector queries
 | Data Processing Tools | General data processing | ![experimental](https://img.shields.io/badge/status-experimental-lightblue?style=flat&logo=appwrite) | Various | - | [data-processing-tools.ts](./data-processing-tools.ts) |
 | PDF | PDF utilities | ![alpha](https://img.shields.io/badge/status-alpha-yellow?style=flat&logo=appwrite) | `pdfTool` | `pdf-parse` | [pdf.ts](./pdf.ts) |
 | SerpAPI Config | SerpAPI configuration | ![stable](https://img.shields.io/badge/status-stable-green?style=flat&logo=appwrite) | Config exports | `serpapi` | [serpapi-config.ts](./serpapi-config.ts) |
+| Code Search | Search for patterns across source files. Supports string and regex patterns with context lines. Use for finding usages, identifying patterns, and code exploration. | ![stable](https://img.shields.io/badge/status-stable-green?style=flat&logo=appwrite) | `codeSearchTool` | `fast-glob`, `zod`, `re2` | [code-search.tool.ts](./code-search.tool.ts) |
+| Find Symbol | Find symbol definitions (functions, classes, variables) across the codebase using semantic analysis. | ![stable](https://img.shields.io/badge/status-stable-green?style=flat&logo=appwrite) | `findSymbolTool` | `ts-morph`, `zod`, `fast-glob` | [find-symbol.tool.ts](./find-symbol.tool.ts) |
 
 ### 6. 📈 Financial Chart Tools
 ![charts](https://img.shields.io/badge/category-charts-teal?style=flat&logo=appwrite)
@@ -118,7 +120,47 @@ export const yourTool = createTool({
 - **Error Handling**: Try-catch, clear messages, retries for APIs.
 - **Security**: Sanitize inputs, mask secrets, rate-limit.
 - **Performance**: Cache, stream large data, timeouts.
-- **Observability**: Arize spans on all executes.
+- **Observability**: Otel spans on all executes.
+
+### Data Tool Progress Events
+
+All tools must emit progress events with this exact format:
+
+```typescript
+// ✅ CORRECT: Progress event format
+await context?.writer?.custom({
+  type: "data-tool-progress",
+  data: {
+    status: "in-progress", // "in-progress" | "done"
+    message: "Descriptive progress message...",
+    stage: "tool-name" // Tool identifier (same as id)
+  },
+  id: "tool-name" // Tool identifier outside data object
+});
+
+// ❌ WRONG: Don't put id inside data object
+await context?.writer?.custom({
+  type: "data-tool-progress",
+  data: {
+    id: "tool-name", // ❌ Wrong - id belongs outside
+    message: "..."
+  }
+});
+```
+
+**Example from Alpha Vantage Tool:**
+
+```typescript
+await context?.writer?.custom({
+  type: 'data-tool-progress',
+  data: {
+    status: 'in-progress',
+    message: `📈 Fetching Alpha Vantage crypto data for ${inputData.symbol}/${inputData.market}`,
+    stage: 'alpha-vantage-crypto'
+  },
+  id: 'alpha-vantage-crypto'
+});
+```
 
 ## Testing
 97% coverage via Vitest. Run: