RepoPilot

odysseus-dev / odysseus

Search odysseus-dev/odysseus

GitHub

Code

How odysseus-dev/odysseus is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely public API
  4. Likely public API
  5. Likely start-up file
  6. Likely start-up file
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new agent tool

  • Define effect handlers in src/agent_runtime/effect_adapters.py to execute tool effects with proper error handling.
  • Register tool in src/agent_tools/__init__.py tool registry so agent loop can discover and invoke it.
  • Add tool capability hints in src/execution_capabilities.py to inform model of tool availability and usage patterns.

Add support for a new LLM provider

  • Register provider in src/llm_core.py routing logic to enable model selection and completion requests.
  • Add configuration keys in src/config.py for provider API endpoints and authentication.

Add a new search/retrieval backend

  • Extend src/search/core.py query execution to support new embedding or index format.
  • Implement ranking strategy in src/search/ranking.py for result relevance scoring.
  • Add cache invalidation logic in src/search/cache.py if search index changes.
  • Register provider in src/search/providers.py so agent can switch between search backends.

Add a new external service integration

  • Create integration module in src/integrations.py or new dedicated file handling API communication.
  • Add credential management in src/api_key_manager.py for service authentication tokens.
  • Create background job handler in src/background_tool_jobs.py for async sync or polling.
  • Expose via agent tool in src/agent_tools/ so chat interface can trigger integrations.

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.

Code quality and hotspots

Largest source files

  • Branch points1006 per file on average
  • Code issues134 errors, 701 warnings
  • Largest file38,040 lines
  • Hotspot load10 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions11 workflows
  • Tests1,523 test filesPytest · 1.8 test files per source file (file count, not coverage)
  • Dependency updatesCodeQL · Trivy

Test folders: specs/model-providers · specs · scripts

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.