---
title: Why does my Codex agent keep showing /status every 30 seconds?
question: Codex terminal repeats /status on its own after an account switch
area: troubleshooting
surface: desktop
audience: beginner
keywords: ["/status", "status loop", "Codex 0.159", "Pro (More)", "account switch", "automatic switching", "switch status", "account not confirmed", "native-account-unreadable", "saved login"]
related: [automatic-usage-switching, quadrant-already-switching-providers, codex-inbox-message-not-submitted, claude-accounts-and-usage]
updated: 2026-09-29
visibility: public
---

# Why does my Codex agent keep showing /status every 30 seconds?

Codus types `/status` into an idle Codex agent to confirm which account it is using, after a start or an account switch. Codex CLI 0.159 changed that answer: it dropped the box around the details and shows the plan, for example "Pro (More)", instead of the signed-in email. Codus 0.2.195 and earlier could not read it, so the account was never confirmed, an automatic account switch never completed, and Codus asked again every 30 seconds for as long as the agent ran. Codus 0.2.196 or later reads the new answer and stops asking. Update through **Settings → Updates**, then fully quit and reopen Codus.

## Before you start

Check the Codus version in **Settings → Updates** and run `codex --version` in a terminal. The loop needs both Codex 0.159 or later and Codus 0.2.195 or earlier.

## What happens on 0.2.196 or later

1. After a start or an account switch, Codus reads the `/status` answer once the agent is idle.
2. When the answer shows an email, that is the account. When it shows only a plan, Codus 0.2.197 or later confirms the account from the running Codex process itself: Codus starts every Codex agent bound to one account folder, and it reads that binding back from the process, or, on Windows, from the report the agent's own start hook posts from inside that process. A process bound to a different folder is refused, one whose binding cannot be read is reported as unconfirmed rather than guessed, and the same process must stay in front from the question to the answer.
3. If the answer still cannot be read, Codus asks at most six more times, thirty seconds apart, then stops. The agent's row in **Switch status** then says the account could not be confirmed and tells you to finish a turn there or restart the agent from its quadrant.

## Saved logins on 0.2.196

Codus 0.2.196 confirmed the account by checking where the resumed conversation is stored, and saved logins share one conversations folder with the default login on purpose. So on 0.2.196 with Codex 0.159, a switch to a saved login was refused as unconfirmed and rolled back, and a Brain reported "The new Brain did not confirm its native conversation (native-account-unreadable)". Codus 0.2.197 or later confirms the account from the running Codex process instead, as described above. Update through **Settings → Updates**, then fully quit and reopen Codus before retrying the switch.

## Stop the loop on an older version

The repeated `/status` lines do not interrupt the agent's work and do not send a message. They stop when the agent's account is confirmed, when the agent is stopped, or when Codus is fully quit and reopened. Updating to 0.2.196 or later ends them for good.

## How do I know it worked?

Open **Claude** or **Codex** in the status bar, then **Switch status**. The agent's row shows its account and no longer says the account is unknown, and the terminal shows no new `/status` lines.