[Desktop] SSH sessions are a dead end for local work: can't start/see local sessions, can't switch environment, no in-app feedback

Environment: Claude desktop app (Code tab) on macOS, version 2.26454.0; session connected over SSH to a remote Linux GPU server.

What I wanted: keep code in a local repo on my Mac (fork → clone locally), and run GPU jobs on a remote server over ssh. A very common ML workflow.

What happened

1. An SSH session can't create a local session. The agent has no start_session / hand_off_to_session tool in an SSH session, so it can't open a session on my own machine. I had to do it myself.
2. An SSH session can't even see local sessions. list_sessions from the SSH session only shows sessions on the same SSH connection. So after I created a local session, the SSH-side agent couldn't hand context over to it. Context handoff has to go the other way, through a file plus a hand-written prompt.
3. A session's environment/folder can't be changed after creation, and there is no visible way to switch the current conversation to Local. Moving means starting a new session and losing the conversation flow.
4. New sessions are auto-named after the folder (e.g. "ML"), not the task.
5. The agent couldn't fork or clone for me. The SSH host had no GitHub auth. The Chrome extension wasn't connected, and the agent can't install or connect it. "Bypass permissions" doesn't help, because the problem is where the session runs, not permissions.
6. No obvious in-app feedback / thumbs-down button in the Code tab to report this.

Expected

• From an SSH session, be able to start or hand off to a session on the local machine (with the conversation carried over), or switch the current session between Local and SSH.
• Sessions on the local machine and on SSH hosts should be visible to each other for handoff.
• When a session is created, make it obvious whether it runs locally or on the remote host. I didn't realise the agent couldn't touch my laptop until it was deep into the task.
• Sensible session titles derived from the task.
• A visible feedback button in the Code tab.