start.sh: MCP installation fails with older uv due to directory shadowing
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
Research direction
Open start.sh and compare the existing UI launch command with the MCP installation and retry commands. Reproduce the failure from the repository root with uv run artemis mcp --help, then verify the MCP help and installation commands succeed with the Python module entry point under the reported older uv environment.
Written by the indexing model from the issue text.
Description
Description
When running ./start.sh from the repository root and choosing to install MCP configuration, installation fails with:
ImportError: cannot import name 'RunTree' from 'langsmith'
(<project>/.venv/lib/python3.14/site-packages/langsmith/__init__.py)
The Showcase UI build completes successfully before this failure.
Environment
- macOS
- Python 3.14.5
- uv 0.5.9
- Repository commit: 371aa6d
Reproduction
From the repository root:
uv run artemis mcp --help
This reproduces the same import error without modifying IDE configuration.
Verbose uv output shows:
DEBUG Running `python artemis mcp --help`
Cause
In this environment, uv interprets artemis as the local directory instead of invoking the installed console script. This places the package directory on the module search path, allowing artemis/platform to shadow Python's standard-library platform module.
Expected behavior
The MCP command should run successfully from the repository root.
Verified workaround
uv run python -m artemis mcp --help
uv run python -m artemis mcp --install all
Both commands succeed with the same Python environment and dependencies.
Proposed fix
Use uv run python -m artemis for MCP installation and the retry instructions in start.sh, consistent with the script's existing UI launch command.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 779
- Avg merge
- 20m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/artemis
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100