docs: fix quick-start venv setup and MCP command in README#563
Open
pprieri wants to merge 1 commit into
Open
Conversation
Step 2 was calling `uv pip install` without first creating a venv, which fails because uv requires an explicit environment target. Added `uv venv .venv` and pinned installs to that venv with `--python .venv/bin/python`. Step 4 used `uv run --directory /path/to/ai-dev-kit`, but there is no `pyproject.toml` at the repo root, so uv has no project to resolve and cannot guarantee the packages installed in Step 2 are on the path. Replaced with the direct venv interpreter path, which is also what `install.sh` generates when it writes the MCP config automatically.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 2 was calling
uv pip installwithout first creating a venv, which fails because uv requires an explicit environment target. Addeduv venv .venvand pinned installs to that venv with--python .venv/bin/python.Step 4 used
uv run --directory /path/to/ai-dev-kit, but there is nopyproject.tomlat the repo root, so uv has no project to resolve and cannot guarantee the packages installed in Step 2 are on the path. Replaced with the direct venv interpreter path, which is also whatinstall.shgenerates when it writes the MCP config automatically.