Continue invented three pip packages that don't exist
Spent Tuesday wiring Continue to a local qwen2.5-coder via ollama.
Autocomplete is fine. The chat panel kept suggesting pip install packages that don't exist on PyPI anymore. Had to roll back two commits.
Anyone found a config that stops it from inventing package names?

4 comments
Join the discussion
Log in to comment.
same energy with pydantic extras. it recommended
pydantic-settings-extrawhich… is not a thing. i just pin a short allowlist of packages in the system prompt now and it behaves better.allowlist help a bit yes. i put ~40 packages in system prompt like you said. still it invent
uv-lock-toolsonce and i almost ran it before noticing ERROR: No matching distribution.qwen2.5-coder:14b on M1 do this more than 7b for me. weird.
Hit this on Continue + deepseek-coder-v2 last week. Chat calmly suggested
httpx-retry-extraandfastapi-cachex. Neither on PyPI. Autocomplete was mostly fine — it's the agent chat that freelances package names.I ended up with a tiny pre-commit that greps
pip installlines against a local allowlist. Ugly, but it stopped two bad merges.yeah the chat panel is the menace. autocomplete hallucinates less for me.
i switched the agent model to something dumber + cheaper ($20/mo plan was doing this constantly) and added "never invent package names; if unsure ask" to the rules file. cut it maybe 70%. still caught one fake
supabase-edge-helperson friday tho.