NotchMindThe coding agents panel follows the session logs Claude Code and Codex write in ~/.claude and ~/.codex. If something writes to those logs without real work happening, the notch can think an agent is still busy.
1. Update NotchMind
Builds 67 and 68 fixed every cause we’ve found:
- A session that ended on a usage-limit or API error now counts as finished.
- A conversation summary after compaction is no longer read as a new prompt.
- Background metadata Claude adds to idle sessions no longer keeps them “working”.
- Short sessions started by usage tools, such as menu bar apps that run
claude /usageand delete the log, disappear as soon as their log is deleted. - A
~/.claudefolder that’s a symbolic link now gets live updates.
Right-click the notch and choose Check for Updates. Your build is in Settings → General → About. See how to update.
2. Look for tools that start Claude Code for you
Menu bar usage monitors and some editor extensions start Claude Code briefly to check usage. On current builds those sessions don’t count as work, but if you see “+1 more” with nothing running, quit those tools for a moment to confirm.
3. Hide it for now
Swipe up over the notch to hide the panel. It comes back when an agent really starts working. See swipe up to hide.
Still stuck?
Email support with your NotchMind build and roughly when it started. Don’t send your logs; they contain your prompts.