You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pick up a client conversation from a couple of weeks ago and continue it in Paseo, in the place where I want it to live.
Some context on the shape of my work, because I think it's why this bites me harder than it might bite others: I'm not doing worktree-based parallel development. There are a handful of unrelated client directories, often not even git repositories, with one long-running conversation each. Nothing to isolate, nothing to merge. Workspaces for me are just a way to group and find things, not a way to keep agents off each other's files.
How I do it today
In the CLI I'd run claude --resume and pick from the list. In Paseo I open Import Session and look for it there.
Where Paseo gets in the way
Three separate points of friction, all in the same "get this old session back into my hands" flow:
Finding it. Import Session offers the most recent 15 sessions per provider. One of my project directories has 116 session files in it, so most of my history simply isn't offerable — there's no search and no way to page further back. The workaround I ended up using is to open the session in the CLI and send it a message purely to bump its modification time so it floats to the top of the list. That only works when I already know which session I want, which is the thing I opened the list to figure out.
Putting it somewhere. When I create a fresh workspace to hold an imported session, the workspace doesn't exist yet in any durable sense — it evaporates unless something commits it. So the sequence that works is: create workspace, say "hi" to an agent I don't actually want, wait for it to commit, then import. I'm left with a throwaway agent whose only job was to make the workspace real.
Changing my mind. Once a session has been imported somewhere, that's where it stays. If I later decide it belongs in a different workspace, there's no way to move it — even though an agent's owning workspace and its working directory are clearly separate concepts.
What would the flow look like if it worked for me
I'd search Import Session by name or first prompt and find a session regardless of when I last touched it. Importing into a brand-new workspace would be the thing that makes that workspace real — no throwaway message. And if I later got the placement wrong, I'd move the agent to another workspace instead of re-importing it and losing its Paseo-side identity.
Underneath all three: for my kind of use, sessions are long-lived objects I keep coming back to, and Paseo's session handling is oriented around ones I've touched recently.
Originally written up as #2636, #2641 and #2620 before I'd read CONTRIBUTING — they're really one workflow, so I've merged them here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
What am I trying to do
Pick up a client conversation from a couple of weeks ago and continue it in Paseo, in the place where I want it to live.
Some context on the shape of my work, because I think it's why this bites me harder than it might bite others: I'm not doing worktree-based parallel development. There are a handful of unrelated client directories, often not even git repositories, with one long-running conversation each. Nothing to isolate, nothing to merge. Workspaces for me are just a way to group and find things, not a way to keep agents off each other's files.
How I do it today
In the CLI I'd run
claude --resumeand pick from the list. In Paseo I open Import Session and look for it there.Where Paseo gets in the way
Three separate points of friction, all in the same "get this old session back into my hands" flow:
Finding it. Import Session offers the most recent 15 sessions per provider. One of my project directories has 116 session files in it, so most of my history simply isn't offerable — there's no search and no way to page further back. The workaround I ended up using is to open the session in the CLI and send it a message purely to bump its modification time so it floats to the top of the list. That only works when I already know which session I want, which is the thing I opened the list to figure out.
Putting it somewhere. When I create a fresh workspace to hold an imported session, the workspace doesn't exist yet in any durable sense — it evaporates unless something commits it. So the sequence that works is: create workspace, say "hi" to an agent I don't actually want, wait for it to commit, then import. I'm left with a throwaway agent whose only job was to make the workspace real.
Changing my mind. Once a session has been imported somewhere, that's where it stays. If I later decide it belongs in a different workspace, there's no way to move it — even though an agent's owning workspace and its working directory are clearly separate concepts.
What would the flow look like if it worked for me
I'd search Import Session by name or first prompt and find a session regardless of when I last touched it. Importing into a brand-new workspace would be the thing that makes that workspace real — no throwaway message. And if I later got the placement wrong, I'd move the agent to another workspace instead of re-importing it and losing its Paseo-side identity.
Underneath all three: for my kind of use, sessions are long-lived objects I keep coming back to, and Paseo's session handling is oriented around ones I've touched recently.
Originally written up as #2636, #2641 and #2620 before I'd read CONTRIBUTING — they're really one workflow, so I've merged them here.
All reactions