Repository navigation
feat(console): restore session direct path input alongside picker - #7593
Conversation
|
Hi @Bruce-Yii, thank you for your first Pull Request! 🎉 📋 About PR TemplateTo help maintainers review your PR faster, please make sure to include:
Complete PR information helps speed up the review process. You can edit the PR description to add these details. 🙌 Join Developer CommunityThanks so much for your contribution! We'd love to invite you to join the official QwenPaw developer group! You can find the Discord and DingTalk group links under the "Developer Community" section on our docs page: We truly appreciate your enthusiasm—and look forward to your future contributions! 😊 We'll review your PR soon. |
Welcome to QwenPaw! 🎉Thank you @Bruce-Yii for your first contribution! Your PR has been merged. 🚀 We'd love to give you a shout-out in our release notes! If you're comfortable sharing, please reply to this comment with your social media handles using the format below:
Thanks again for helping make QwenPaw better! |


Fixes #7588.
What Problem This Solves
QwenPaw v2.1 allowed users to paste a working-directory path and press Enter to switch directly. During the session-scoped multi-directory refactor in #6976, the session single-path field was replaced by the bound-directory list, but the direct input capability was not migrated.
For deeply nested directories this leaves users dependent on the graphical picker even when they already have the exact path from a terminal, IDE, or file manager.
What Changes
PUT /chats/{id}/project-dirsbackend path.Evidence
The regression was traced to #6976 (
dd0c65ee), where the session single-path field was replaced by the multi-directory bound list. The PR's stated scope was multi-directory binding; it did not introduce a security/product decision forbidding typed paths. Agent scope retained its direct input, and the current backend continues to validate submitted paths with the same existing-directory checks.Regression tests verify:
Testing
SessionProjectDirectory.test.tsx: 20 passedtsc -b --noEmit: passedgit diff --check: passedThe full Vite production build did not complete within the sandbox's 300-second execution window; no build error was observed before timeout. Focused type-check/lint/test gates above passed.
Scope
Only the session project-directory Console component and its regression tests are changed. No backend API, security boundary, dependency, channel, or unrelated Console behavior changes are included.
Residual Risk
A live browser/backend visual interaction check was not performed in the sandbox. The request payload, primary-directory ordering, error behavior, and picker/input interaction are covered by automated tests.