JetBrains (Rider): project paths containing spaces are URI-encoded (%20) when creating the project .continue directory on Windows
Maintainers usually reply within 3 days
@BetterAndBetterII is already working on this.
Since Aug 30, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- devtools
Research direction
Start by tracing the JetBrains project-path handling used when creating the project-specific .continue directory, searching for where filesystem paths are converted to URIs. Reproduce on Windows with a project path containing spaces, then verify that the directory is created at the actual path and not the %20-encoded location.
Written by the indexing model from the issue text.
Description
Summary
When using Continue in JetBrains Rider on Windows, creating or editing the project-specific Continue configuration causes the plugin to create a .continue directory under a URI-encoded filesystem path.
Instead of using the actual project path containing spaces, Continue creates directories where spaces are replaced with %20, resulting in an incorrect location outside the real project directory.
Environment
OS: Windows 11
IDE: JetBrains Rider 2026.2.0.2
Continue: 1.0.67
Project type: Unity/Rider project
Steps to reproduce
- Create or open a project located at:
C:\Unity Projects\My Project - Open the project in JetBrains Rider.
- Use Continue to create or modify the project-specific Continue configuration.
- Check where the
.continuedirectory is created.
Expected behavior
The project configuration should be created inside the actual project directory:
C:\Unity Projects\My Project\.continue
Actual behavior
Continue creates the directory under a URI-encoded path instead:
C:\Unity%20Projects\My%20Project\.continue
As a result, the configuration is written to an incorrect location.
- Dominant language
- TypeScript
- Stars
- 36.1k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 continuedev/continue
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
continuedev/continue#13291 ·
Maintainers usually reply within 3 days
-
Ollama provider drops `tools` after the first tool call, breaking multi-step agent loopsPossibly taken @dvd233 claimed this 23 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
continuedev/continue#13254 · 2 comments ·
Maintainers usually reply within 3 days
-
[Bug] LanceDbIndex interpolates paths into LanceDB SQL predicates — apostrophes in file/workspace paths break index deletes (stale chunks stay retrievable) and retrievalPossibly taken @seethinajayadileep claimed this 29 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
continuedev/continue#13233 ·
Maintainers usually reply within 3 days
-
docs: PZERO OpenAI-compatible apiBase examplePossibly taken @dajiaohuang claimed this 32 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
continuedev/continue#13198 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
continuedev/continue#13197 ·
Maintainers usually reply within 3 days
All issues in continuedev/continue
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day