Staying sane during long Claude Code sessions
Agentic coding means a lot of waiting. Practical habits for long Claude Code runs: scoping tasks, checking in at the right moments, and seeing Claude's state at a glance.
Long Claude Code runs go better when tasks are scoped tightly, when you check in on events (an error, a question, the end) rather than reading every line, and when Claude's state is visible at a glance. A free plugin like Asciimood shows that state as an ASCII animation and keeps errors and questions in full view.
Waiting is part of the job now
With an agent like Claude Code, a single prompt can turn into minutes of reading, editing and testing. The work is good; the waiting is the new part. Reading every tool call as it scrolls by is the worst of both worlds: you are not doing your own work, and you are not really reviewing Claude's either.
1. Scope the task before you start
The clearest way to shorten a run is a precise prompt: which files, what done looks like, how to check it (a test to pass, a command to run). Claude spends less time exploring, and you have a clear thing to verify at the end.
2. Check in on events, not on lines
There are only a few moments when Claude needs you: an error it can't get past, a permission prompt, a question, and the end of the turn. Everything else can run on its own. Set things up so those moments are obvious and the rest is quiet.
That is the idea behind Asciimood: routine tool calls fold into one grey line each, while errors (the frame turns red), permission prompts, questions and the final answer always stay in full.
3. Make the state visible at a glance
When you glance over from another window, you want to know in half a second whether Claude is still reading, already writing, running the tests, stuck, or done. Asciimood gives each of those its own animation, a DNA helix while it reads, character rain while it writes, fire on an error, waves when it is done, with a status line showing the current action and the elapsed time.
/plugin install asciimood --marketplace tmdlz/asciimood4. Review at the end, properly
Because you did not watch every line, review the result: read the final answer, look at the diff, run the tests yourself. That is a better use of attention than following the scroll live.
Frequently asked questions
How can I tell what Claude Code is doing without reading the output?
Install the free Asciimood plugin: it plays a different ASCII animation for each state (thinking, reading, writing, running a command, error, done) with a status line showing the current action and elapsed time.
Does Asciimood hide errors?
No. Errors and failed tool calls always show in full, and the animation's frame turns red.