continuedev / continuedev/continue
JetBrains (Rider): project paths containing spaces are URI-encoded (%20) when creating the project .continue directory on Windows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
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.
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.
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.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100