130 lines
5.3 KiB
Markdown
130 lines
5.3 KiB
Markdown
# Phase 4: Internet Access & MCP
|
|
|
|
## Plan 4.2: Test Web Search Capabilities and Integration
|
|
|
|
### Objective
|
|
Test and verify that the OpenCode AI assistant can successfully perform web searches through the configured MCP servers.
|
|
|
|
**Purpose:** Ensure the web search functionality is working correctly and integrate it with the AI assistant's capabilities.
|
|
|
|
**Output:** Test results confirming web search functionality through MCP servers and documentation of the integration.
|
|
|
|
### Execution Context
|
|
- ~/.config/opencode/gsd/workflows/execute-phase.md
|
|
- ~/.config/opencode/gsd/templates/phase-prompt.md
|
|
- ~/.config/opencode/gsd/references/plan-format.md
|
|
- ~/.config/opencode/gsd/references/checkpoints.md
|
|
|
|
### Context
|
|
@.planning/PROJECT.md
|
|
@.planning/ROADMAP.md
|
|
@.planning/phases/04-internet-access/04-01-SUMMARY.md
|
|
@src/modules/nixos/services/open_code_server.nix
|
|
|
|
**Project Context:**
|
|
- MCP servers (Context7 and DuckDuckGo) should be configured from Plan 1
|
|
- OpenCode service needs to be running to test web search functionality
|
|
- Testing should verify both MCP servers are functional and accessible
|
|
|
|
### Tasks
|
|
|
|
<task type="auto">
|
|
<name>Task 1: Start OpenCode Service</name>
|
|
<files>None - systemd service</files>
|
|
<action>Start the OpenCode service using systemd:
|
|
sudo systemctl start opencode
|
|
Ensure the service is running and check logs for any errors</action>
|
|
<verify>systemctl status opencode shows service is active and running</verify>
|
|
<done>OpenCode service is running without errors</done>
|
|
</task>
|
|
|
|
<task type="auto">
|
|
<name>Task 2: Test Context7 Web Search</name>
|
|
<files>None - runtime test</files>
|
|
<action>Test web search through Context7 MCP:
|
|
1. Use the OpenCode API to send a web search query
|
|
2. Verify the response includes search results from Context7
|
|
3. Check that the service properly handles the MCP communication
|
|
Example query: "What is the current weather in New York?"</action>
|
|
<verify>Web search through Context7 returns valid search results</verify>
|
|
<done>Context7 web search is functional and returns expected results</done>
|
|
</task>
|
|
|
|
<task type="auto">
|
|
<name>Task 3: Test DuckDuckGo Web Search</name>
|
|
<files>None - runtime test</files>
|
|
<action>Test web search through DuckDuckGo MCP:
|
|
1. Use the OpenCode API to send a web search query
|
|
2. Verify the response includes search results from DuckDuckGo
|
|
3. Check that the service properly handles the MCP communication
|
|
Example query: "Latest news about AI technology"</action>
|
|
<verify>Web search through DuckDuckGo returns valid search results</verify>
|
|
<done>DuckDuckGo web search is functional and returns expected results</done>
|
|
</task>
|
|
|
|
<task type="checkpoint:human-verify" gate="blocking">
|
|
<what-built>Web search functionality through MCP servers</what-built>
|
|
<how-to-verify>
|
|
1. Test web search queries through both Context7 and DuckDuckGo
|
|
2. Verify search results are relevant and current
|
|
3. Check that the AI assistant can properly interpret and format results
|
|
4. Test a variety of query types (factual, news, technology)
|
|
</how-to-verify>
|
|
<resume-signal>Type "approved" if web search is working correctly, or describe any issues with search results or functionality</resume-signal>
|
|
</task>
|
|
|
|
<task type="auto">
|
|
<name>Task 4: Document Web Search Integration</name>
|
|
<files>Documentation in configuration or README</files>
|
|
<action>Document the web search capabilities in the OpenCode configuration:
|
|
1. Add comments explaining the MCP server configuration
|
|
2. Note which MCP servers are available for web search
|
|
3. Document any limitations or known issues with web search
|
|
4. Provide examples of effective web search queries</action>
|
|
<verify>Configuration file includes documentation about MCP web search capabilities</verify>
|
|
<done>Web search integration is documented with examples and usage notes</done>
|
|
</task>
|
|
|
|
### Verification
|
|
Before declaring phase complete:
|
|
- [ ] OpenCode service is running without errors
|
|
- [ ] Context7 web search returns valid, relevant results
|
|
- [ ] DuckDuckGo web search returns valid, relevant results
|
|
- [ ] AI assistant properly interprets and formats search results
|
|
- [ ] Web search capabilities are documented
|
|
- [ ] No errors in service logs during web search operations
|
|
|
|
### Success Criteria
|
|
- All tasks completed successfully
|
|
- Web search functionality through both MCP servers is working
|
|
- AI assistant can effectively use web search capabilities
|
|
- Configuration and usage are properly documented
|
|
- No errors or warnings introduced in the configuration
|
|
- Phase 4 (Internet Access & MCP) is complete
|
|
|
|
### Output
|
|
After completion, create `.planning/phases/04-internet-access/04-02-SUMMARY.md`:
|
|
|
|
# Phase 4 Plan 2: Web Search Integration Summary
|
|
|
|
Web search capabilities through MCP servers successfully tested and integrated.
|
|
|
|
## Accomplishments
|
|
- Started OpenCode service and verified it's running
|
|
- Tested and verified Context7 web search functionality
|
|
- Tested and verified DuckDuckGo web search functionality
|
|
- Human verification of web search results
|
|
- Documented web search integration
|
|
|
|
## Files Created/Modified
|
|
- `/home/gortium/infra/modules/nixos/services/open_code_server.nix` - Added documentation
|
|
|
|
## Decisions Made
|
|
- No significant decisions required - testing existing configuration
|
|
|
|
## Issues Encountered
|
|
- Any issues encountered during testing, along with resolutions
|
|
|
|
## Next Step
|
|
Phase 4 complete. Ready to proceed to Phase 5: TAK Server Integration
|