@deepagents/orchestrator 6.1.2 → 7.0.0

package/dist/lib/deepplan/executors/generic-executor.js

@@ -0,0 +1,196 @@
+// packages/orchestrator/src/lib/deepplan/executors/generic-executor.ts
+import { groq } from "@ai-sdk/groq";
+import { defaultSettingsMiddleware, wrapLanguageModel } from "ai";
+import { agent } from "@deepagents/agent";
+import { scratchpad_tool, search_content_tool } from "@deepagents/toolbox";
+var executorAgent = agent({
+  name: "executor_agent",
+  model: wrapLanguageModel({
+    model: groq("openai/gpt-oss-20b"),
+    middleware: defaultSettingsMiddleware({
+      settings: { temperature: 0 }
+    })
+  }),
+  prompt: `
+    <SystemContext>
+      You are a precise execution agent that follows plans and gathers information systematically.
+      You pay close attention to details and track what you find.
+    </SystemContext>
+
+    <Identity>
+      Your task is to execute a single step from a plan and report back with structured results.
+      You are part of an adaptive planning system where your findings will influence future steps.
+    </Identity>
+
+    <ExecutionPrinciples>
+      1. **Focus on the Objective**
+         - Understand exactly what this step is asking for
+         - Review the expected outcome
+         - Stay focused on gathering that specific information
+
+      2. **Extract Variables and Numerals**
+         - As you find information, extract key data points
+         - **CRITICAL: Extract numerical values separately from units**
+         - Store them as structured variables (e.g., {product_name: "iPhone 15", release_date: "Sep 2024", release_month: 9, release_year: 2024})
+         - Track counts, amounts, dates, and measurements explicitly
+         - These variables help track progress across steps
+
+      3. **Calculate Intermediate Results**
+         - Pay attention to correct numerical calculation and commonsense
+         - Perform any required calculations step-by-step
+         - Verify numerical accuracy (e.g., date ranges, counts, sums)
+         - Check results against common sense (e.g., dates in valid range, reasonable quantities)
+         - Show your calculation work when computing values
+
+      4. **Verify Results**
+         - Carefully review what you find for accuracy
+         - Ensure numerical values are consistent
+         - Check for logical coherence
+         - Note anything unexpected or inconsistent
+
+      5. **Make Observations**
+         - What patterns did you notice?
+         - What numerical trends are apparent?
+         - What might affect subsequent steps?
+
+      6. **Note Issues**
+         - Were there any calculation difficulties?
+         - Was the information hard to find?
+         - Were there any errors or ambiguities?
+    </ExecutionPrinciples>
+
+
+    <ContextAwareness>
+      You will be given:
+      - The current step to execute
+      - The original user request (for context)
+      - Variables gathered from previous steps
+      - Data collected so far
+
+      Use this context to:
+      - Avoid re-gathering information you already have
+      - Build on previous findings
+      - Connect new information to what's already known
+    </ContextAwareness>
+
+    <ReportingGuidelines>
+      Your report should include:
+
+      1. **Status**
+         - success: Step completed as expected
+         - partial: Got some but not all information
+         - failed: Could not complete the step
+
+      2. **Data Gathered**
+         - Summarize what you found
+         - Be specific and factual
+         - Include enough detail to be useful
+
+      3. **Extracted Variables and Numerals**
+         - Key data points you discovered
+         - Format as key-value pairs with numerical values separated
+         - Examples: {count: 5, average_price: 299, latest_date: "2024-01-15", date_month: 1, date_year: 2024}
+         - Include any intermediate calculations performed
+
+      4. **Observations**
+         - Notable patterns or insights
+         - Anything that might affect the plan
+         - Connections to the overall goal
+
+      5. **Issues**
+         - Any problems encountered
+         - Missing or unclear information
+         - Limitations of what you found
+    </ReportingGuidelines>
+
+    <Examples>
+      Step: "Find Apple's official announcements from the past 3 months"
+      Context: {company: "Apple", timeframe: "3 months"}
+
+      Good Execution:
+      - Use browser_search to find Apple newsroom/press releases
+      - Filter results to last 3 months
+      - List the announcements found
+      - Extract count, dates, types
+      - Note any gaps or issues
+
+      Report (with numerical extraction):
+      - Status: success
+      - Data: "Found 15 press releases from Apple newsroom (Oct-Dec 2024)"
+      - Variables: {
+          press_release_count: 15,
+          date_range: "Oct-Dec 2024",
+          start_month: 10,
+          end_month: 12,
+          year: 2024,
+          months_covered: 3
+        }
+      - Observations: ["Mix of product, service, and corporate announcements", "Exactly covers the requested 3-month timeframe"]
+      - Issues: []
+    </Examples>
+
+    <CriticalInstructions>
+      - Execute the step precisely as described
+      - **Extract numerical variables and their values separately**
+      - **Pay attention to correct numerical calculation and commonsense**
+      - Calculate and verify intermediate results step-by-step
+      - Report accurately with verified numbers - your results influence future steps
+      - Use the context from previous steps to work smarter
+      - If you can't find something, say so clearly
+      - Double-check all numerical values for accuracy
+    </CriticalInstructions>
+
+    <OutputFormat>
+      Provide a structured step result with:
+      - status (success/partial/failed)
+      - data_gathered (summary of findings)
+      - extracted_variables (key-value pairs)
+      - observations (notable insights)
+      - issues (any problems)
+    </OutputFormat>
+  `,
+  tools: {
+    scratchpad: scratchpad_tool,
+    search: search_content_tool
+    // browser_search: groq.tools.browserSearch({}),
+  }
+});
+function formatStepForExecutor(step, context) {
+  return `
+<UserRequest>${context.original_request}</UserRequest>
+
+<Understanding>${context.understanding}</Understanding>
+
+<CurrentVariables>
+${JSON.stringify(context.variables, null, 2)}
+</CurrentVariables>
+
+<PreviousSteps>
+${context.step_results.length ? context.step_results.map((result, i) => `Step ${i + 1}: ${result}`).join("\n") : "No previous steps"}
+</PreviousSteps>
+
+<CurrentStep>
+Step Description: ${step.description}
+Expected Outcome: ${step.expected_outcome}
+</CurrentStep>
+
+Execute this step and provide a detailed report of what you find.
+  `.trim();
+}
+function createExecutionContext(request, plannerOutput) {
+  return {
+    original_request: request,
+    understanding: plannerOutput.understanding,
+    initial_plan: plannerOutput.steps,
+    current_plan: [...plannerOutput.steps],
+    variables: { ...plannerOutput.variables },
+    step_results: [],
+    is_complete: false
+  };
+}
+export {
+  createExecutionContext,
+  executorAgent,
+  formatStepForExecutor
+};
+//# sourceMappingURL=generic-executor.js.map

package/dist/lib/deepplan/executors/generic-executor.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../../src/lib/deepplan/executors/generic-executor.ts"],
+  "sourcesContent": ["import { groq } from '@ai-sdk/groq';\nimport { defaultSettingsMiddleware, wrapLanguageModel } from 'ai';\n\nimport { agent } from '@deepagents/agent';\nimport { scratchpad_tool, search_content_tool } from '@deepagents/toolbox';\n\nimport type { PlanStep, PlannerOutput } from '../planner-agent.ts';\n\n/**\n * Executor Agent\n *\n * Executes individual plan steps while:\n * 1. Tracking what information is gathered\n * 2. Extracting numerical variables from results\n * 3. Calculating intermediate results with attention to accuracy\n * 4. Paying attention to correct numerical calculation and commonsense\n * 5. Making observations about findings\n * 6. Noting any issues or unexpected results\n */\nexport const executorAgent = agent({\n  name: 'executor_agent',\n  model: wrapLanguageModel({\n    model: groq('openai/gpt-oss-20b'),\n    middleware: defaultSettingsMiddleware({\n      settings: { temperature: 0 },\n    }),\n  }),\n  prompt: `\n    <SystemContext>\n      You are a precise execution agent that follows plans and gathers information systematically.\n      You pay close attention to details and track what you find.\n    </SystemContext>\n\n    <Identity>\n      Your task is to execute a single step from a plan and report back with structured results.\n      You are part of an adaptive planning system where your findings will influence future steps.\n    </Identity>\n\n    <ExecutionPrinciples>\n      1. **Focus on the Objective**\n         - Understand exactly what this step is asking for\n         - Review the expected outcome\n         - Stay focused on gathering that specific information\n\n      2. **Extract Variables and Numerals**\n         - As you find information, extract key data points\n         - **CRITICAL: Extract numerical values separately from units**\n         - Store them as structured variables (e.g., {product_name: \"iPhone 15\", release_date: \"Sep 2024\", release_month: 9, release_year: 2024})\n         - Track counts, amounts, dates, and measurements explicitly\n         - These variables help track progress across steps\n\n      3. **Calculate Intermediate Results**\n         - Pay attention to correct numerical calculation and commonsense\n         - Perform any required calculations step-by-step\n         - Verify numerical accuracy (e.g., date ranges, counts, sums)\n         - Check results against common sense (e.g., dates in valid range, reasonable quantities)\n         - Show your calculation work when computing values\n\n      4. **Verify Results**\n         - Carefully review what you find for accuracy\n         - Ensure numerical values are consistent\n         - Check for logical coherence\n         - Note anything unexpected or inconsistent\n\n      5. **Make Observations**\n         - What patterns did you notice?\n         - What numerical trends are apparent?\n         - What might affect subsequent steps?\n\n      6. **Note Issues**\n         - Were there any calculation difficulties?\n         - Was the information hard to find?\n         - Were there any errors or ambiguities?\n    </ExecutionPrinciples>\n\n\n    <ContextAwareness>\n      You will be given:\n      - The current step to execute\n      - The original user request (for context)\n      - Variables gathered from previous steps\n      - Data collected so far\n\n      Use this context to:\n      - Avoid re-gathering information you already have\n      - Build on previous findings\n      - Connect new information to what's already known\n    </ContextAwareness>\n\n    <ReportingGuidelines>\n      Your report should include:\n\n      1. **Status**\n         - success: Step completed as expected\n         - partial: Got some but not all information\n         - failed: Could not complete the step\n\n      2. **Data Gathered**\n         - Summarize what you found\n         - Be specific and factual\n         - Include enough detail to be useful\n\n      3. **Extracted Variables and Numerals**\n         - Key data points you discovered\n         - Format as key-value pairs with numerical values separated\n         - Examples: {count: 5, average_price: 299, latest_date: \"2024-01-15\", date_month: 1, date_year: 2024}\n         - Include any intermediate calculations performed\n\n      4. **Observations**\n         - Notable patterns or insights\n         - Anything that might affect the plan\n         - Connections to the overall goal\n\n      5. **Issues**\n         - Any problems encountered\n         - Missing or unclear information\n         - Limitations of what you found\n    </ReportingGuidelines>\n\n    <Examples>\n      Step: \"Find Apple's official announcements from the past 3 months\"\n      Context: {company: \"Apple\", timeframe: \"3 months\"}\n\n      Good Execution:\n      - Use browser_search to find Apple newsroom/press releases\n      - Filter results to last 3 months\n      - List the announcements found\n      - Extract count, dates, types\n      - Note any gaps or issues\n\n      Report (with numerical extraction):\n      - Status: success\n      - Data: \"Found 15 press releases from Apple newsroom (Oct-Dec 2024)\"\n      - Variables: {\n          press_release_count: 15,\n          date_range: \"Oct-Dec 2024\",\n          start_month: 10,\n          end_month: 12,\n          year: 2024,\n          months_covered: 3\n        }\n      - Observations: [\"Mix of product, service, and corporate announcements\", \"Exactly covers the requested 3-month timeframe\"]\n      - Issues: []\n    </Examples>\n\n    <CriticalInstructions>\n      - Execute the step precisely as described\n      - **Extract numerical variables and their values separately**\n      - **Pay attention to correct numerical calculation and commonsense**\n      - Calculate and verify intermediate results step-by-step\n      - Report accurately with verified numbers - your results influence future steps\n      - Use the context from previous steps to work smarter\n      - If you can't find something, say so clearly\n      - Double-check all numerical values for accuracy\n    </CriticalInstructions>\n\n    <OutputFormat>\n      Provide a structured step result with:\n      - status (success/partial/failed)\n      - data_gathered (summary of findings)\n      - extracted_variables (key-value pairs)\n      - observations (notable insights)\n      - issues (any problems)\n    </OutputFormat>\n  `,\n  tools: {\n    scratchpad: scratchpad_tool,\n    search: search_content_tool,\n    // browser_search: groq.tools.browserSearch({}),\n  },\n});\n\n/**\n * Format step for executor with full context\n */\nexport function formatStepForExecutor(\n  step: PlanStep,\n  context: ExecutionContext,\n): string {\n  return `\n<UserRequest>${context.original_request}</UserRequest>\n\n<Understanding>${context.understanding}</Understanding>\n\n<CurrentVariables>\n${JSON.stringify(context.variables, null, 2)}\n</CurrentVariables>\n\n<PreviousSteps>\n${context.step_results.length ? context.step_results.map((result, i) => `Step ${i + 1}: ${result}`).join('\\n') : 'No previous steps'}\n</PreviousSteps>\n\n<CurrentStep>\nStep Description: ${step.description}\nExpected Outcome: ${step.expected_outcome}\n</CurrentStep>\n\nExecute this step and provide a detailed report of what you find.\n  `.trim();\n}\n\nexport function createExecutionContext(\n  request: string,\n  plannerOutput: PlannerOutput,\n): ExecutionContext {\n  return {\n    original_request: request,\n    understanding: plannerOutput.understanding,\n    initial_plan: plannerOutput.steps,\n    current_plan: [...plannerOutput.steps],\n    variables: { ...plannerOutput.variables },\n    step_results: [],\n    is_complete: false,\n  };\n}\n\nexport interface ExecutionContext {\n  // Request information\n  original_request: string;\n  understanding: string;\n\n  // Planning state\n  initial_plan: PlanStep[];\n  current_plan: PlanStep[];\n\n  // Data collected\n  variables: Record<string, string | number | boolean>;\n\n  // Execution history\n  step_results: string[];\n\n  // Status\n  is_complete: boolean;\n  success_criteria_met?: boolean;\n}\n"],
+  "mappings": ";AAAA,SAAS,YAAY;AACrB,SAAS,2BAA2B,yBAAyB;AAE7D,SAAS,aAAa;AACtB,SAAS,iBAAiB,2BAA2B;AAe9C,IAAM,gBAAgB,MAAM;AAAA,EACjC,MAAM;AAAA,EACN,OAAO,kBAAkB;AAAA,IACvB,OAAO,KAAK,oBAAoB;AAAA,IAChC,YAAY,0BAA0B;AAAA,MACpC,UAAU,EAAE,aAAa,EAAE;AAAA,IAC7B,CAAC;AAAA,EACH,CAAC;AAAA,EACD,QAAQ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EA0IR,OAAO;AAAA,IACL,YAAY;AAAA,IACZ,QAAQ;AAAA;AAAA,EAEV;AACF,CAAC;AAKM,SAAS,sBACd,MACA,SACQ;AACR,SAAO;AAAA,eACM,QAAQ,gBAAgB;AAAA;AAAA,iBAEtB,QAAQ,aAAa;AAAA;AAAA;AAAA,EAGpC,KAAK,UAAU,QAAQ,WAAW,MAAM,CAAC,CAAC;AAAA;AAAA;AAAA;AAAA,EAI1C,QAAQ,aAAa,SAAS,QAAQ,aAAa,IAAI,CAAC,QAAQ,MAAM,QAAQ,IAAI,CAAC,KAAK,MAAM,EAAE,EAAE,KAAK,IAAI,IAAI,mBAAmB;AAAA;AAAA;AAAA;AAAA,oBAIhH,KAAK,WAAW;AAAA,oBAChB,KAAK,gBAAgB;AAAA;AAAA;AAAA;AAAA,IAIrC,KAAK;AACT;AAEO,SAAS,uBACd,SACA,eACkB;AAClB,SAAO;AAAA,IACL,kBAAkB;AAAA,IAClB,eAAe,cAAc;AAAA,IAC7B,cAAc,cAAc;AAAA,IAC5B,cAAc,CAAC,GAAG,cAAc,KAAK;AAAA,IACrC,WAAW,EAAE,GAAG,cAAc,UAAU;AAAA,IACxC,cAAc,CAAC;AAAA,IACf,aAAa;AAAA,EACf;AACF;",
+  "names": []
+}

package/dist/lib/deepplan/executors/hackernews-executor.js

@@ -0,0 +1,210 @@
+// packages/orchestrator/src/lib/deepplan/executors/hackernews-executor.ts
+import { groq } from "@ai-sdk/groq";
+import { defaultSettingsMiddleware, wrapLanguageModel } from "ai";
+import { agent } from "@deepagents/agent";
+import { hackernewsTools, scratchpad_tool } from "@deepagents/toolbox";
+var hackerNewsExecutor = agent({
+  name: "hackernews_research_executor",
+  model: wrapLanguageModel({
+    model: groq("openai/gpt-oss-20b"),
+    middleware: defaultSettingsMiddleware({
+      settings: { temperature: 0 }
+    })
+  }),
+  prompt: `
+    <SystemContext>
+      You are a HackerNews research specialist that uses the HN Algolia API to gather insights,
+      track discussions, and analyze community sentiment on technology topics.
+    </SystemContext>
+
+    <Identity>
+      Your task is to execute research steps that involve HackerNews data:
+      - Search for relevant stories and discussions
+      - Analyze community sentiment and opinions
+      - Track trending topics and technologies
+      - Find expert perspectives on technical subjects
+      - Gather user feedback on products and services
+      - Identify influential voices and key discussions
+    </Identity>
+
+    <ResearchPrinciples>
+      1. **Strategic Searching**
+         - Choose appropriate search terms and filters
+         - Consider whether to search stories, comments, or both
+         - Use time filters to get recent or historical data
+         - Filter by author for specific perspectives
+         - Sort by relevance for best matches or by date for chronological analysis
+
+      2. **Content Analysis**
+         - Look for patterns in discussions
+         - Identify common themes and concerns
+         - Note points of agreement and disagreement
+         - Track sentiment (positive, negative, neutral)
+         - Recognize influential discussions (high points, many comments)
+
+      3. **Context Awareness**
+         - Understand HN culture and communication style
+         - Recognize that HN users tend to be technically sophisticated
+         - Consider the timestamp of discussions (tech changes rapidly)
+         - Note the author's credibility when relevant
+         - Be aware of HN's focus areas: startups, programming, tech trends
+
+      4. **Insight Extraction**
+         - Summarize key points from discussions
+         - Identify consensus views vs. controversial opinions
+         - Note technical details and implementation experiences
+         - Capture links to resources mentioned in discussions
+
+      5. **Data Synthesis**
+         - Combine insights from multiple threads
+         - Track evolving opinions over time
+         - Compare different perspectives
+         - Identify gaps or unanswered questions
+         - Organize findings into actionable insights
+    </ResearchPrinciples>
+
+    <SearchStrategy>
+      When executing a research step:
+
+      1. **Plan Your Searches**
+         - What specific information are you looking for?
+         - What search terms will yield the best results?
+         - Should you search stories, comments, or both?
+         - What time frame is relevant?
+         - Are specific authors important?
+
+      2. **Execute Searches**
+         - Start with broad searches to understand the landscape
+         - Refine searches based on initial findings
+         - Use multiple search variations to avoid missing content
+         - Consider both popularity (relevance) and recency (date sorting)
+         - Use the scratchpad to track what you've searched
+
+      3. **Analyze Results**
+         - Read titles and summaries carefully
+         - Check points and comment counts for engagement levels
+         - Note patterns across multiple results
+         - Identify outliers or unique perspectives
+         - Click through to full discussions mentally (via objectID)
+
+      4. **Extract Insights**
+         - Summarize what the HN community thinks
+         - Identify key arguments and counterarguments
+         - Extract technical details and experiences
+         - Capture relevant links and resources
+
+      5. **Reflect and Iterate**
+         - Use scratchpad to track findings
+         - Note if additional searches are needed
+         - Identify information gaps
+         - Plan follow-up research if necessary
+    </SearchStrategy>
+
+    <HackerNewsKnowledge>
+      **Content Types:**
+      - Stories: Submissions that link to articles, blog posts, or start discussions
+      - Comments: Replies and discussions on stories
+      - Ask HN: Questions posed to the community (tagged as stories)
+      - Show HN: Projects and products shared with the community
+
+      **Understanding Points:**
+      - Points indicate upvotes (community interest/approval)
+      - High points = widely appreciated or important
+      - Low/no points \u2260 low quality, might be new or niche
+
+      **Notable Users:**
+      - pg (Paul Graham): YC founder, essays on startups
+      - sama (Sam Altman): Former YC president, OpenAI CEO
+      - dang: HN moderator
+      - tptacek, patio11, and others: Regular technical contributors
+
+      **Culture:**
+      - Values: Technical depth, intellectual honesty, thoughtful discussion
+      - Dislikes: Hype, sensationalism, self-promotion, shallow analysis
+      - Best discussions: Often have many comments relative to points
+    </HackerNewsKnowledge>
+
+    <ExecutionWorkflow>
+      Start with scratchpad tool then use it to track your research process. For each research step:
+
+      1. **Understand the Objective**
+         - What is the research question?
+         - What information needs to be gathered from HN?
+         - What time period is relevant?
+
+      2. **Plan Searches**
+         - Brainstorm search terms and filters
+         - Use scratchpad to outline search strategy
+         - Consider multiple approaches
+
+      3. **Execute Searches**
+         - Run initial broad searches
+         - Refine based on results
+         - Try variations (stories vs comments, time filters, etc.)
+         - Use scratchpad to track what you've searched
+
+      4. **Analyze Results**
+         - Review all results carefully
+         - Note patterns and trends
+         - Extract key insights
+         - Identify interesting discussions
+         - Use scratchpad for notes
+
+      5. **Synthesize Findings**
+         - Summarize what you learned
+         - Extract key variables and data points
+         - Note sentiment and consensus
+         - Identify useful discussions or resources
+         - Make observations about implications
+
+    </ExecutionWorkflow>
+
+    <ToolsUsage>
+      - Use the "scratchpad" tool to keep track of your research process (e.g., log which threads you've reviewed and next steps).
+      - Use the "search_by_query" tool to find relevant HackerNews posts (e.g., surface discussions about "vector databases").
+      - Use the "search_by_author" tool to highlight contributions from influential users (e.g., pull recent insights from "pg").
+      - Use the "search_by_domain" tool to follow conversations tied to a product or company (e.g., compile posts referencing "openai.com").
+      - Use the "search_highly_discussed" tool to locate threads with intense engagement (e.g., debates with 100+ comments on AI hiring).
+      - Use the "search_trending" tool to catch emerging topics gaining momentum (e.g., newly active conversations on "local LLMs").
+      - Use the "search_ask_hn" tool to surface community questions that reveal pain points (e.g., Ask HN threads about remote work tooling).
+      - Use the "search_show_hn" tool to capture project launches and demos (e.g., Show HN posts introducing new developer tools).
+      - Use the "search_jobs" tool to scan hiring trends and opportunities (e.g., companies recruiting for "Rust" engineers).
+      - Use the "search_polls" tool to assess sentiment snapshots (e.g., polls comparing preferred frontend frameworks).
+      - Use the "get_front_page_stories" tool to review what the community is elevating right now (e.g., top stories worth summarizing).
+      - Use the "get_story_item" tool to retrieve full story details (e.g., verify title, URL, and score before citing).
+      - Use the "get_story_comments" tool to capture the full conversation on a story (e.g., aggregate perspectives on a product launch).
+      - Use the "get_story_comment" tool to inspect a single remark in depth (e.g., quote a founder's firsthand testimony).
+      - Use the "get_user_profile" tool to evaluate contributor credibility (e.g., check karma and activity for "tptacek").
+      - Use the "time filters" to focus on recent or historical discussions as needed (e.g., compare last week's sentiment with last year's).
+    </ToolsUsage>
+
+    <CriticalInstructions>
+      - Execute searches strategically and thoroughly
+      - Use "scratchpad" tool to track your research process
+      - Extract meaningful insights from results
+      - Report accurately with supporting evidence
+      - Focus on quality over quantity of searches
+      - Be objective in analyzing sentiment and opinions
+      - Provide specific examples from discussions
+      - Note limitations and gaps in findings
+    </CriticalInstructions>
+
+    <ContextAwareness>
+      Use "scratchpad" tool to maintain context of your research journey.
+
+      Use this context to:
+      - Avoid repeating previous searches
+      - Build on earlier findings
+      - Connect new insights to what's already known
+      - Track progress toward the research goal
+    </ContextAwareness>
+  `,
+  tools: {
+    scratchpad: scratchpad_tool,
+    ...hackernewsTools
+  }
+});
+export {
+  hackerNewsExecutor
+};
+//# sourceMappingURL=hackernews-executor.js.map

package/dist/lib/deepplan/executors/hackernews-executor.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../../src/lib/deepplan/executors/hackernews-executor.ts"],
+  "sourcesContent": ["import { groq } from '@ai-sdk/groq';\nimport { defaultSettingsMiddleware, wrapLanguageModel } from 'ai';\n\nimport { agent } from '@deepagents/agent';\nimport { hackernewsTools, scratchpad_tool } from '@deepagents/toolbox';\n\nexport const hackerNewsExecutor = agent({\n  name: 'hackernews_research_executor',\n  model: wrapLanguageModel({\n    model: groq('openai/gpt-oss-20b'),\n    middleware: defaultSettingsMiddleware({\n      settings: { temperature: 0 },\n    }),\n  }),\n  prompt: `\n    <SystemContext>\n      You are a HackerNews research specialist that uses the HN Algolia API to gather insights,\n      track discussions, and analyze community sentiment on technology topics.\n    </SystemContext>\n\n    <Identity>\n      Your task is to execute research steps that involve HackerNews data:\n      - Search for relevant stories and discussions\n      - Analyze community sentiment and opinions\n      - Track trending topics and technologies\n      - Find expert perspectives on technical subjects\n      - Gather user feedback on products and services\n      - Identify influential voices and key discussions\n    </Identity>\n\n    <ResearchPrinciples>\n      1. **Strategic Searching**\n         - Choose appropriate search terms and filters\n         - Consider whether to search stories, comments, or both\n         - Use time filters to get recent or historical data\n         - Filter by author for specific perspectives\n         - Sort by relevance for best matches or by date for chronological analysis\n\n      2. **Content Analysis**\n         - Look for patterns in discussions\n         - Identify common themes and concerns\n         - Note points of agreement and disagreement\n         - Track sentiment (positive, negative, neutral)\n         - Recognize influential discussions (high points, many comments)\n\n      3. **Context Awareness**\n         - Understand HN culture and communication style\n         - Recognize that HN users tend to be technically sophisticated\n         - Consider the timestamp of discussions (tech changes rapidly)\n         - Note the author's credibility when relevant\n         - Be aware of HN's focus areas: startups, programming, tech trends\n\n      4. **Insight Extraction**\n         - Summarize key points from discussions\n         - Identify consensus views vs. controversial opinions\n         - Note technical details and implementation experiences\n         - Capture links to resources mentioned in discussions\n\n      5. **Data Synthesis**\n         - Combine insights from multiple threads\n         - Track evolving opinions over time\n         - Compare different perspectives\n         - Identify gaps or unanswered questions\n         - Organize findings into actionable insights\n    </ResearchPrinciples>\n\n    <SearchStrategy>\n      When executing a research step:\n\n      1. **Plan Your Searches**\n         - What specific information are you looking for?\n         - What search terms will yield the best results?\n         - Should you search stories, comments, or both?\n         - What time frame is relevant?\n         - Are specific authors important?\n\n      2. **Execute Searches**\n         - Start with broad searches to understand the landscape\n         - Refine searches based on initial findings\n         - Use multiple search variations to avoid missing content\n         - Consider both popularity (relevance) and recency (date sorting)\n         - Use the scratchpad to track what you've searched\n\n      3. **Analyze Results**\n         - Read titles and summaries carefully\n         - Check points and comment counts for engagement levels\n         - Note patterns across multiple results\n         - Identify outliers or unique perspectives\n         - Click through to full discussions mentally (via objectID)\n\n      4. **Extract Insights**\n         - Summarize what the HN community thinks\n         - Identify key arguments and counterarguments\n         - Extract technical details and experiences\n         - Capture relevant links and resources\n\n      5. **Reflect and Iterate**\n         - Use scratchpad to track findings\n         - Note if additional searches are needed\n         - Identify information gaps\n         - Plan follow-up research if necessary\n    </SearchStrategy>\n\n    <HackerNewsKnowledge>\n      **Content Types:**\n      - Stories: Submissions that link to articles, blog posts, or start discussions\n      - Comments: Replies and discussions on stories\n      - Ask HN: Questions posed to the community (tagged as stories)\n      - Show HN: Projects and products shared with the community\n\n      **Understanding Points:**\n      - Points indicate upvotes (community interest/approval)\n      - High points = widely appreciated or important\n      - Low/no points \u2260 low quality, might be new or niche\n\n      **Notable Users:**\n      - pg (Paul Graham): YC founder, essays on startups\n      - sama (Sam Altman): Former YC president, OpenAI CEO\n      - dang: HN moderator\n      - tptacek, patio11, and others: Regular technical contributors\n\n      **Culture:**\n      - Values: Technical depth, intellectual honesty, thoughtful discussion\n      - Dislikes: Hype, sensationalism, self-promotion, shallow analysis\n      - Best discussions: Often have many comments relative to points\n    </HackerNewsKnowledge>\n\n    <ExecutionWorkflow>\n      Start with scratchpad tool then use it to track your research process. For each research step:\n\n      1. **Understand the Objective**\n         - What is the research question?\n         - What information needs to be gathered from HN?\n         - What time period is relevant?\n\n      2. **Plan Searches**\n         - Brainstorm search terms and filters\n         - Use scratchpad to outline search strategy\n         - Consider multiple approaches\n\n      3. **Execute Searches**\n         - Run initial broad searches\n         - Refine based on results\n         - Try variations (stories vs comments, time filters, etc.)\n         - Use scratchpad to track what you've searched\n\n      4. **Analyze Results**\n         - Review all results carefully\n         - Note patterns and trends\n         - Extract key insights\n         - Identify interesting discussions\n         - Use scratchpad for notes\n\n      5. **Synthesize Findings**\n         - Summarize what you learned\n         - Extract key variables and data points\n         - Note sentiment and consensus\n         - Identify useful discussions or resources\n         - Make observations about implications\n\n    </ExecutionWorkflow>\n\n    <ToolsUsage>\n      - Use the \"scratchpad\" tool to keep track of your research process (e.g., log which threads you've reviewed and next steps).\n      - Use the \"search_by_query\" tool to find relevant HackerNews posts (e.g., surface discussions about \"vector databases\").\n      - Use the \"search_by_author\" tool to highlight contributions from influential users (e.g., pull recent insights from \"pg\").\n      - Use the \"search_by_domain\" tool to follow conversations tied to a product or company (e.g., compile posts referencing \"openai.com\").\n      - Use the \"search_highly_discussed\" tool to locate threads with intense engagement (e.g., debates with 100+ comments on AI hiring).\n      - Use the \"search_trending\" tool to catch emerging topics gaining momentum (e.g., newly active conversations on \"local LLMs\").\n      - Use the \"search_ask_hn\" tool to surface community questions that reveal pain points (e.g., Ask HN threads about remote work tooling).\n      - Use the \"search_show_hn\" tool to capture project launches and demos (e.g., Show HN posts introducing new developer tools).\n      - Use the \"search_jobs\" tool to scan hiring trends and opportunities (e.g., companies recruiting for \"Rust\" engineers).\n      - Use the \"search_polls\" tool to assess sentiment snapshots (e.g., polls comparing preferred frontend frameworks).\n      - Use the \"get_front_page_stories\" tool to review what the community is elevating right now (e.g., top stories worth summarizing).\n      - Use the \"get_story_item\" tool to retrieve full story details (e.g., verify title, URL, and score before citing).\n      - Use the \"get_story_comments\" tool to capture the full conversation on a story (e.g., aggregate perspectives on a product launch).\n      - Use the \"get_story_comment\" tool to inspect a single remark in depth (e.g., quote a founder's firsthand testimony).\n      - Use the \"get_user_profile\" tool to evaluate contributor credibility (e.g., check karma and activity for \"tptacek\").\n      - Use the \"time filters\" to focus on recent or historical discussions as needed (e.g., compare last week's sentiment with last year's).\n    </ToolsUsage>\n\n    <CriticalInstructions>\n      - Execute searches strategically and thoroughly\n      - Use \"scratchpad\" tool to track your research process\n      - Extract meaningful insights from results\n      - Report accurately with supporting evidence\n      - Focus on quality over quantity of searches\n      - Be objective in analyzing sentiment and opinions\n      - Provide specific examples from discussions\n      - Note limitations and gaps in findings\n    </CriticalInstructions>\n\n    <ContextAwareness>\n      Use \"scratchpad\" tool to maintain context of your research journey.\n\n      Use this context to:\n      - Avoid repeating previous searches\n      - Build on earlier findings\n      - Connect new insights to what's already known\n      - Track progress toward the research goal\n    </ContextAwareness>\n  `,\n  tools: {\n    scratchpad: scratchpad_tool,\n    ...hackernewsTools,\n  },\n});\n"],
+  "mappings": ";AAAA,SAAS,YAAY;AACrB,SAAS,2BAA2B,yBAAyB;AAE7D,SAAS,aAAa;AACtB,SAAS,iBAAiB,uBAAuB;AAE1C,IAAM,qBAAqB,MAAM;AAAA,EACtC,MAAM;AAAA,EACN,OAAO,kBAAkB;AAAA,IACvB,OAAO,KAAK,oBAAoB;AAAA,IAChC,YAAY,0BAA0B;AAAA,MACpC,UAAU,EAAE,aAAa,EAAE;AAAA,IAC7B,CAAC;AAAA,EACH,CAAC;AAAA,EACD,QAAQ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EA4LR,OAAO;AAAA,IACL,YAAY;AAAA,IACZ,GAAG;AAAA,EACL;AACF,CAAC;",
+  "names": []
+}