Why isn’t my Claude Code or Codex column running?

An AI column set to Claude Code (local agent) or Codex (local agent) runs on your own subscription instead of an API key. When it stops filling, it is almost always because the claude or codex command-line tool on your computer is signed out. That login expires every so often and is separate from the Claude desktop app.

What you’ll see

Rows stay on Processing… and do not finish.
A message that Claude Code is not logged in or not installed. For example: “Claude Code isn't logged in, so this column can't run. Run claude auth login in a terminal to sign back in, then run the column again.”
In Settings, a line such as AI columns on “Claude Code (local agent)”: not logged in — run claude auth login in a terminal, then click Re-check. For Codex the command is codex login.
In the column’s model list, the model shows — not logged in or — not installed after its name.
After 10 minutes on one row: “Timed out waiting for Claude Code to process this row (10 min).”

Nothing is wrong with your table, prompt or rows. The app is waiting for a helper it cannot start.

Columns set to an API model (OpenAI, Anthropic, Gemini) are unaffected, because they do not use the command-line tools. If only your Claude Code or Codex columns are stuck, this is the reason.

1. Sign the command-line tool back in

Open Terminal (macOS) or a command prompt (Windows) and run:

claude auth login

For Codex, run codex login instead. A browser window opens. Sign in with your account and approve. You can also run claude and type /login inside it.

2. Check that it worked

claude auth status

Signed out, this reports an authentication method of none. Once you are signed in it reports your account.

3. Tell Manycrawl to look again

Open Settings and click Re-check on the line for your AI columns. When it is healthy it reads ready (logged in). Then run the column again. You do not need to restart the app.

Rows that failed while you were signed out keep their error until you run the column on them again.

If it says “not installed”

The message is “Claude Code isn't installed on this computer, so “Claude Code (local agent)” columns can't run here. Install Claude Code, or pick another model for this column.” Install the tool, or change the column to an API model.

If it says the worker can’t start

You may see “Claude Code's built-in worker can't start” followed by the tool’s last message, for example that the sign-in session expired. That is the same fix: sign in again, click Re-check, run the column. If the message does not look like a sign-in problem it ends with See the app log for details. Open the activity log and send it to support (see Contact support).

Why the Claude desktop app isn’t enough

Being signed in to the Claude desktop app does not sign in the claude command-line tool. They are separate programs with separate logins, and the desktop app keeps its own sign-in to itself, so Manycrawl cannot borrow it.

A different way: let a session you control do the work

Instead of the built-in worker, you can keep a Claude or Codex session open and let it work through the Manycrawl queue. In Settings, choose Connect Claude Desktop (it adds a manycrawl entry to ~/.claude.json) or Connect Codex (it edits ~/.codex/config.toml). For Claude, open the Code tab in Claude Desktop and approve the tools once. See the MCP page for the setup guides.

If it still doesn’t run

Keep Manycrawl open and signed in while the column runs. The work happens on your computer, not in the cloud.
Check your Claude or Codex usage limit. If you have hit it, wait for the reset or switch the column to an API model.
Try one row first after fixing the login, so you see the result quickly before running a large table.
If the app runs the column from an automation or a monitor in the background, you get a system notification instead of an on-screen message.

Still stuck? See Contact support and send the table, the column’s model, and what claude auth status prints.