What happened
Hovering a conversation in the Desktop sidebar shows its full absolute working-directory path. This is noisy, leaks machine-specific path details into the primary summary, and is inconsistent with the rest of the UI, which identifies the workspace by project name.
Expected behavior: the hover card shows the registered project name. For sessions outside the project catalog, it falls back to the working directory folder name. The full path may remain available as secondary tooltip detail.
How to reproduce
- Open Maka Desktop with a registered project.
- Create or open a conversation in that project.
- Hover the conversation row in the sidebar.
- Observe that the hover card renders the full absolute
cwd instead of the project name.
Environment
- Maka commit:
fcfa0550e
- OS: macOS
- Surface: Desktop
- Node.js:
v22.20.0
Logs, screenshots, or additional context
The session hover-card implementation currently renders session.cwd directly. The project catalog already carries the human-readable project name.
What happened
Hovering a conversation in the Desktop sidebar shows its full absolute working-directory path. This is noisy, leaks machine-specific path details into the primary summary, and is inconsistent with the rest of the UI, which identifies the workspace by project name.
Expected behavior: the hover card shows the registered project name. For sessions outside the project catalog, it falls back to the working directory folder name. The full path may remain available as secondary tooltip detail.
How to reproduce
cwdinstead of the project name.Environment
fcfa0550ev22.20.0Logs, screenshots, or additional context
The session hover-card implementation currently renders
session.cwddirectly. The project catalog already carries the human-readable project name.