Follow Discord
Sweep 22 Oct 2026 · 20:42Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Writing the changelog v2.1.309 compose entry prose · 2/5

Claude Code v2.1.304 ·

Mods can no longer start background work after you press Stop

After Stop, a mod's attempt to start background work is refused, and you see a notice that a mod cannot resume work after Stop

You'll notice Improvements
JSON All of v2.1.304
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.304,
ImprovementsSection of the release

Unclear It is not clear what counts as a mod, or whether the block also applies to background work you start yourself.

What

After you stop Claude Code, a mod can no longer start new work that keeps running in the background. Claude Code refuses these requests and returns a message explaining why. They include:

  • subscribing to a pull request
  • starting a watch or a publish
  • running a command in the background
  • starting a schedule or a goal

When this happens, a short pop-up notice reads: "Stopped: type a message to continue; a mod cannot resume work after Stop". To let work continue, type a new message.

Why

Once you press Stop, work stays stopped. A plugin-driven mod cannot quietly start things up again until you send a message.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what counts as a mod, or whether the block also applies to background work you start yourself.

See this entry in the whole of v2.1.304 →

Feedback