Problem
In the Kilo Cloud app session listing, I can select a cloud thread and fork it to VS Code Kilo or the Kilo Code CLI, but there is no option to fork it into another cloud session.
To accomplish a cloud-to-cloud fork today I have to fork the session out to the CLI or VS Code and then fork/export it back into the cloud. That is an unnecessary, roundabout limitation.
Expected behavior
From a cloud session, allow forking directly into a new cloud session (e.g. a "Fork to cloud" / "Continue in new cloud session" action), the same way cloud sessions can currently be forked to CLI and VS Code.
Context
- Forking to CLI and VS Code already works from the cloud session listing.
- The reverse direction (forking/exporting back to cloud) also works via the CLI/VS Code.
- Only the direct cloud-to-cloud path is missing.
Problem
In the Kilo Cloud app session listing, I can select a cloud thread and fork it to VS Code Kilo or the Kilo Code CLI, but there is no option to fork it into another cloud session.
To accomplish a cloud-to-cloud fork today I have to fork the session out to the CLI or VS Code and then fork/export it back into the cloud. That is an unnecessary, roundabout limitation.
Expected behavior
From a cloud session, allow forking directly into a new cloud session (e.g. a "Fork to cloud" / "Continue in new cloud session" action), the same way cloud sessions can currently be forked to CLI and VS Code.
Context