by Corepass

Use Remy

Branch a conversation

Explore another approach from an existing discussion.

Scope: The steps below use a local chat in the desktop app.

A conversation branch starts a new chat from an existing response, keeping the discussion up to that point so you can try another approach. The original chat remains available.

1. Decide when to branch

What you want to do Suggested action
Correct the result of the current task Continue in the original chat
Try another approach from the existing discussion Branch from the relevant response
Start an unrelated task Start a new chat and describe the new goal

For example, if Remy has explained two possible implementations, branch from that response to explore the alternatives in separate conversations.

2. Branch from a response

  1. Open the original chat and find the Remy response you want to branch from.
  2. Look at the controls below the response. For older responses, you may need to hover over them to reveal the controls.
  3. Click the branch icon labeled Branch in new chat.
  4. Wait for the new chat to open on the right and review the discussion it carries over.
  5. Explain the direction you want to explore in the new chat.

The branch includes the selected response and the conversation before it. Later discussion in the original chat is not part of this branch's starting point.

Example prompt
Keep the requirements we have already agreed on, but explore another implementation first.
Analyze an approach that reuses the existing API. List the modules that would change, the tradeoffs, and how to verify it.
Do not edit files, install dependencies, commit, or push code yet.

3. Understand the file state

Branching a conversation does not undo file changes or automatically create a Git branch or an isolated project checkout.

If you branch from an older response, the project files stay as they are now. They do not return to their state at the time of that response. Check the files and uncommitted changes before asking the new chat to edit them.

Example prompt
Inspect the current project files and uncommitted changes.
Explain how they differ from the state discussed at the point where this chat branched.
List the differences without editing files. Wait for my confirmation before continuing with the new approach.

When two chats use the same project folder, finish and review one set of edits before deciding what to do next. To compare code implementations independently, prepare isolated working directories through your project's usual version-control workflow.

4. Return to the original chat

Open the original chat from the sidebar, or click Continued from chat in the branch to return to the corresponding point in the source conversation.

Conclusions reached in the branch do not automatically become part of the original chat's later discussion. When you return, provide the conclusion you want to adopt and ask Remy to check the current files.

5. If branching fails

  • An empty chat cannot provide a valid branch point. Choose a chat that already has a response.
  • If the project cannot be found, check the folder associated with the chat.
  • Check the sidebar and error message before clicking again, to avoid repeating the operation.
  • If the original task is still editing files, wait for it to finish before asking the branch to edit the same folder.

6. Keep exploring