Menu

1 / 4

9 Timeouts in Claude Code, Codex and Gemini CLI That Cut Long Test Runs Short

DEV Community: productivity·Gabriel Anhaia·9 days ago
#FMudIkTj
#devtoproductivity#devto#dev#claude#timeout
Reading 0:00
15s threshold

Book: System Design Pocket Guide: Fundamentals

Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go

My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools

Me: xgabriel.com | GitHub

Your integration suite takes 14 minutes on a clean run. You ask Claude Code to run it. Two minutes in, the Bash tool stops waiting, and the result Claude gets back reads Command did not complete within its 120s timeout and was moved to the background ( tools reference ).

In your terminal, the suite keeps going in the background. Run the same job in CI with claude -p and a text prompt, and a moved command gets 10 more minutes before Claude Code stops it ( same page ). If Claude didn't ask for a longer timeout, that is 2 minutes in the foreground plus 10 in the background: 12 minutes for a 14-minute suite.

That is one of nine limits that Claude Code, Codex and Gemini CLI put on long work.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.