JTO-3: add Claude Code repository guidance#538
Conversation
Co-Authored-By: Claude <noreply@anthropic.com> Co-authored-by: multica-agent <github@multica.ai>
There was a problem hiding this comment.
Code Review
This pull request adds a new CLAUDE.md file providing comprehensive guidance, development commands, and architecture details for Claude Code. The review feedback correctly identifies that backend execution and test commands need to be run within the Poetry virtual environment (using poetry run -C api) to prevent module resolution errors.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| # Start the FastAPI server on PORT or 8001 | ||
| python -m api.main |
There was a problem hiding this comment.
Since backend dependencies are installed using Poetry in the api directory (poetry install -C api), running python -m api.main directly from the repository root will fail with ModuleNotFoundError because the virtual environment is not active. To run the backend server correctly using the Poetry environment, prefix the command with poetry run -C api.
| # Start the FastAPI server on PORT or 8001 | |
| python -m api.main | |
| # Start the FastAPI server on PORT or 8001 | |
| poetry run -C api python -m api.main |
| # All tests via the project runner | ||
| python tests/run_tests.py | ||
|
|
||
| # Test categories | ||
| python tests/run_tests.py --unit | ||
| python tests/run_tests.py --integration | ||
| python tests/run_tests.py --api | ||
|
|
||
| # Single test file examples | ||
| python tests/unit/test_google_embedder.py | ||
| python tests/api/test_api.py | ||
|
|
||
| # Pytest directly, when useful | ||
| pytest tests/unit/test_google_embedder.py | ||
| pytest tests/unit/test_google_embedder.py::test_name |
There was a problem hiding this comment.
Similar to starting the backend, running the tests directly with python or pytest from the repository root will fail to locate the installed dependencies (like adalflow, requests, etc.) unless executed within the Poetry virtual environment. Prefix these commands with poetry run -C api to ensure they run in the correct environment.
| # All tests via the project runner | |
| python tests/run_tests.py | |
| # Test categories | |
| python tests/run_tests.py --unit | |
| python tests/run_tests.py --integration | |
| python tests/run_tests.py --api | |
| # Single test file examples | |
| python tests/unit/test_google_embedder.py | |
| python tests/api/test_api.py | |
| # Pytest directly, when useful | |
| pytest tests/unit/test_google_embedder.py | |
| pytest tests/unit/test_google_embedder.py::test_name | |
| # All tests via the project runner | |
| poetry run -C api python tests/run_tests.py | |
| # Test categories | |
| poetry run -C api python tests/run_tests.py --unit | |
| poetry run -C api python tests/run_tests.py --integration | |
| poetry run -C api python tests/run_tests.py --api | |
| # Single test file examples | |
| poetry run -C api python tests/unit/test_google_embedder.py | |
| poetry run -C api python tests/api/test_api.py | |
| # Pytest directly, when useful | |
| poetry run -C api pytest tests/unit/test_google_embedder.py | |
| poetry run -C api pytest tests/unit/test_google_embedder.py::test_name |
No description provided.