Cluster444 · chickymonkeys · Oct 15, 2025 · Oct 15, 2025 · Oct 15, 2025 · Oct 15, 2025
diff --git a/README.md b/README.md
@@ -62,6 +62,16 @@ cd ~/projects/my-app
 agentic pull
 ```
 
+### Enable Web Research (Optional)
+
+For external web research capabilities with the `web-search-researcher` agent:
+
+1. Get a Perplexity API key from [https://www.perplexity.ai/settings/api](https://www.perplexity.ai/settings/api)
+2. Set environment variable: `export PERPLEXITY_API_KEY="pplx-your-key"`
+3. Install tool dependencies: `cd .opencode && bun install`
+
+Web research results are cached in `thoughts/docs/` to avoid duplicate API calls.
+
 ### Development Workflow
 
 1. Use the **ticket** command to work with the agent to build out ticket details

diff --git a/agent/codebase-analyzer.md b/agent/codebase-analyzer.md
@@ -15,6 +15,8 @@ tools:
   todoread: false
   todowrite: false
   webfetch: false
+  query-complexity-analysis: false
+  perplexity-search: false
 ---
 
 You are a specialist at understanding HOW code works. Your job is to analyze implementation details, trace data flow, and explain technical workings with precise file:line references.

diff --git a/agent/codebase-locator.md b/agent/codebase-locator.md
@@ -15,6 +15,8 @@ tools:
   todoread: false
   todowrite: false
   webfetch: false
+  query-complexity-analysis: false
+  perplexity-search: false
 ---
 
 You are a specialist at finding WHERE code lives in a codebase. Your job is to locate relevant files and organize them by purpose, NOT to analyze their contents.

diff --git a/agent/codebase-pattern-finder.md b/agent/codebase-pattern-finder.md
@@ -15,6 +15,8 @@ tools:
   todoread: false
   todowrite: false
   webfetch: false
+  query-complexity-analysis: false
+  perplexity-search: false
 ---
 
 You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.

diff --git a/agent/thoughts-analyzer.md b/agent/thoughts-analyzer.md
@@ -15,6 +15,8 @@ tools:
   todoread: false
   todowrite: false
   webfetch: false
+  query-complexity-analysis: false
+  perplexity-search: false
 ---
 
 You are a specialist at extracting HIGH-VALUE insights from thoughts documents. Your job is to deeply analyze documents and return only the most relevant, actionable information while filtering out noise.
@@ -26,6 +28,8 @@ You are a specialist at extracting HIGH-VALUE insights from thoughts documents.
    - Find actionable recommendations
    - Note important constraints or requirements
    - Capture critical technical details
+   - Extract provenance and authoritative claims when analyzing cached external docs (thoughts/docs)
+   - If analyzing cached external docs (thoughts/docs), extract provenance (URL/DOI/version/license) and authoritative claims
 
 2. **Filter Aggressively**
    - Skip tangential mentions

diff --git a/agent/thoughts-locator.md b/agent/thoughts-locator.md
@@ -15,6 +15,8 @@ tools:
   todoread: false
   todowrite: false
   webfetch: false
+  query-complexity-analysis: false
+  perplexity-search: false
 ---
 
 You are a specialist at finding documents in the thoughts/ directory. Your job is to locate relevant thought documents and categorize them, NOT to analyze their contents in depth.
@@ -26,13 +28,15 @@ You are a specialist at finding documents in the thoughts/ directory. Your job i
    - Check thoughts/research/ for previous research
    - Check thoughts/plans/ for previous ipmlentation plans
    - Check thoughts/tickets/ for current tickets that are unstarted or in progress
+   - Check thoughts/docs/ for cached external research (web-search-researcher outputs)
 
 2. **Categorize findings by type**
    - Architecture in architecture/
    - Tickets in tickets/
    - Research in research/
    - Implementation in plans/
    - Reviews in reviews/
+   - Web Search and External Sources in docs/
 
 3. **Return organized results**
    - Group by document type
@@ -49,6 +53,7 @@ thoughts/tickets/      # Ticket documentation
 thoughts/research/     # Research documents
 thoughts/plans/        # Implementation plans
 thoughts/reviews/      # Code Reviews
+thoughts/docs/         # Cached external research and web findings
 
 ### Search Patterns
 - Use grep for content searching
@@ -69,7 +74,7 @@ Structure your findings like this:
 - `thoughts/tickets/eng_1234.md` - Implement rate limiting for API
 
 ### Research
-- `thoughtsresearch/2024-01-15_rate_limiting_approaches.md` - Research on different rate limiting strategies
+- `thoughts/research/2024-01-15_rate_limiting_approaches.md` - Research on different rate limiting strategies
 - `thoughts/shared/research/api_performance.md` - Contains section on rate limiting impact
 
 ### Implementation Plans
@@ -82,7 +87,10 @@ Structure your findings like this:
 ### PR Descriptions
 - `thoughts/shared/prs/pr_456_rate_limiting.md` - PR that implemented basic rate limiting
 
-Total: 8 relevant documents found
+### Web Search and External Sources
+- `thoughts/docs/2023-02-14_ai_coding_assistants_apis.md` - Web search on handling APIs in AI coding assistants
+
+Total: 9 relevant documents found
 ```
 
 ## Search Tips
@@ -101,6 +109,7 @@ Total: 8 relevant documents found
    - Ticket files often named `eng_XXXX.md`
    - Research files often dated `YYYY-MM-DD_topic.md`
    - Plan files often named `feature-name.md`
+   - Web searches often named `YYYY-MM-DD_topic.md`
 
 ## Important Guidelines