Claude Code /stop — Cleanly Halt a Background Session

When work you set running in the background has already finished or is no longer needed but keeps running, it just eats resources and nags at you. /stop is a command that cleanly halts such a background-running session.

Definition (what it is)

/stop is a command that halts the current background session.

Background means a work state that keeps running behind the scenes even when you're not watching it directly in front. Being able to push long-running work to the back and do something else is the upside, but if a task is done or was started by mistake, you need to tidy it up. /stop does exactly that tidying. Because it deals with workflow, it's classified as intermediate.

How to use it (by level)

Basic — Halt a background session

Type this in the input box.

/stop

This halts the currently running background session. You can cleanly cut off work you no longer need.

Common pitfalls

• /stop is a command that halts work in progress. So you don't carelessly halt work whose result you still need, it's best to check what's running first before using it.

Real-world example

When background work like a test or build is done, or there's no reason to keep something you started by mistake, halt it with /stop. Cutting off needlessly running work lightens the environment and reduces confusion.

Taking it further

When you don't know what's running, it's safe to first check with /tasks (background task list), then pick what to halt and /stop it. Learning it as a pair with /background, which pushes work to the back, lets you naturally handle the flow of starting and tidying up background work.

Wrap-up

/stop is a command that halts a background-running session. You can cleanly cut off work that's done or no longer needed. Checking what's running with /tasks before halting prevents the mistake of stopping work you still need.

Based on Claude Code v2.1.154 (2026.05)