Desktop app: workspace switcher hard to find / folder chip looks clickable but isn't
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
As a new desktop app user, I had a hard time figuring out how to change
the working directory for a new session.
Things I tried that didn't work:
- Clicking the folder chip at the top of the chat (e.g. "WK2-LLM and
Prompt E..."). It looks clickable but only opens a menu with
"Show in Explorer" / "Copy path" — no way to change the directory.
- Clicking "+ New session" in the left sidebar. The new session
silently inherited the previous workspace; I was never asked which
folder I wanted.
- Closing and reopening the desktop app. It reopened in the same
workspace.
The workspace switcher actually lives inside Customize → the dropdown
at the top of that panel, which is not where I would have thought to
look. I only found it after a lot of trial and error.
Net effect: switching workspaces felt hidden, and the folder chip
implies an action it doesn't actually offer.
Proposed Solution
Make changing the working directory discoverable from the places users
naturally look:
- Folder chip at the top of the chat
- Either make it open a directory picker on click, or add a small
"change" icon next to it. Today the chip looks interactive but
only exposes "Show in Explorer" / "Copy path", which sets a false
expectation.
- + New session flow
- When starting a new session, show the working directory up front
and let the user change it before sending the first message
(e.g. a "Working directory: <path> [Change]" row above the input).
- Optionally remember a per-user default instead of silently
inheriting the last session's workspace.
- Customize panel
- Keep the workspace dropdown there for power users, but it
shouldn't be the only entry point. Label it clearly as
"Working directory" so it's findable via search/scroll.
The goal: a new user should be able to switch folders without trial
and error or reading docs.
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗