title: "Anti-Pattern: The God Session" last_updated: 2026-03-21 status: proven difficulty: beginner prerequisites:

  • Basic experience with any agentic coding tool

The God Session

What It Looks Like

You open a single session and ask the agent to refactor the auth module, add tests, update the API docs, fix three bugs, and deploy -- all without ever starting fresh.

Why Developers Do This

It feels efficient. You're "in the zone." Switching sessions seems like overhead. The agent remembers everything you've discussed... right?

Why It Fails

Every agentic tool has a finite context window. As the session grows, the agent starts losing early details. Instructions from prompt #3 get crowded out by prompt #30. The agent begins contradicting its own earlier work, misremembering file names, or silently dropping requirements.

The Symptoms

  • Agent "forgets" changes it made 20 minutes ago
  • Quality of output degrades visibly over time
  • Agent starts hallucinating file names or function signatures
  • You spend more time correcting than coding

What to Do Instead

One session, one focused task. Break large efforts into discrete units.

# Wrong: one mega-session
claude  # then proceed to ask for 15 different things

# Right: scoped sessions
claude "refactor auth module to use JWT"
# finish, review, commit
claude "add unit tests for the JWT auth module"
# finish, review, commit
claude "update API docs to reflect new auth flow"

Use /compact if a session runs long, and lean on CLAUDE.md to carry important context between sessions rather than keeping one session alive forever.