Code
How panniantong/agent-reach is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Likely public API
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd a new web scraping channel (e.g., a new social media platform)
- Create a new file in agent_reach/channels/ that extends the Channel base class
- Implement required methods: async read(), async search(), and platform-specific initialization
- Add platform credentials and configuration keys to agent_reach/config.py
- Register the new channel in agent_reach/cli.py argument parser and channel selection logic
Add support for a new LLM provider backend
- Create new backend module in agent_reach/backends/ implementing the backend interface
- Add provider configuration keys and credential handling in agent_reach/config.py
- Integrate backend selection logic in agent_reach/core.py orchestration
- Update CLI argument parser to expose backend selection option
Expose a new agent skill or capability via MCP
- Define the skill logic as a new method or channel in the agent_reach/channels/ or agent_reach/core.py layer
- Register the skill as a callable tool in agent_reach/integrations/mcp_server.py with proper JSON schema
- Document the skill parameters, usage, and examples in agent_reach/skill/SKILL.md
- Add reference examples in agent_reach/skill/references/ organized by category (search.md, social.md, etc.)
Change the public API
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.