---
title: Why does Brain 1 say it is a side conversation?
question: Why does the Brain stop coordinating agents after a btw or side chat?
area: brain
surface: desktop
audience: beginner
keywords: [Brain 1, side chat, side conversation, btw, side, cannot coordinate, wrong thread, return to main conversation, inbox waiting, handoff]
related: [talk-to-the-brain, delegate-to-quadrant-agents]
updated: 2026-09-14
visibility: public
---

# Why does Brain 1 say it is a side conversation?

A provider's temporary side conversation can remain inside the same Brain tab. If that temporary conversation cannot coordinate agents, it does not by itself prove the saved main Brain has forgotten its role or an earlier provider handoff chose the wrong session.

## Before you start

The Codex recovery controls below require Codus **0.2.183 or later**. They are not available in 0.2.182. The tab name identifies the Brain, not necessarily the provider's active conversation.

## Return from a Codex side chat

When Codus confirms the temporary mode, **Side chat** appears in both Agent and Chat views. Its notice explains that new tasks and inbox messages wait until the main conversation is active again.

Use **Return to main conversation** once it is available. If it is disabled, finish the side reply or widen the Agent view as the notice requests. If returning fails, read the displayed error and preserve any draft before retrying. The app must confirm the mode changed; a click alone is not proof.

## On an older installation

Inspect the provider's Agent view and its displayed controls for returning to the main conversation. Keep the app version, provider and whether a side-chat command was used when reporting the issue. Do not delete the Brain, replace its instructions or switch accounts solely because a reply calls itself a side conversation.

An agent's description of its instructions is evidence to investigate, not sufficient proof of which saved session Codus launched. Compare the active conversation with the original launch before attributing the problem to a handoff.

## How do I know it worked?

The temporary-chat notice clears and the main conversation is active again. Check the waiting task or inbox message separately; returning does not establish that its work is complete.