Does canceling a task restore my original files?

Do not assume so. Inspect the affected files and use the relevant application’s version or recovery options when needed. Stopping work and reversing changes are separate operations.

Is there one switch that disables all Dispatch work?

Do not assume a universal switch exists. Stop the active task, review schedules, and manage the particular permissions or connections you want to remove.

Will pausing a schedule stop a run already in progress?

Check the active run separately. A schedule determines future starts; use the current task’s controls to end work that has already begun.

Should I delete the conversation after stopping?

First preserve the information needed to inspect partial work and recover it. Deleting a conversation is not evidence that external actions or file changes were reversed.

How to Stop Claude Cowork and Check What Finished

Stop active Cowork work, inspect partial results, and distinguish canceling one run from pausing scheduled tasks or removing access to your apps.

September 19, 2026Updated October 21, 20265 min read

To stop Claude Cowork, open the active task, use its stop control, and confirm that the run has stopped before checking its partial results. Stopping a run does not undo files or external actions already completed. If you also want to prevent future scheduled work or remove app access, handle those separately.

fenbs can retain what finished, what remains uncertain, and where a later session should resume. That is especially useful when you stop a delegated task from another device and need someone to inspect the actual output afterward.

What is the immediate stopping routine?

Open the specific active task rather than starting another conversation about stopping it.
Use the stop control shown in that task. Inspect its state to confirm it is no longer working; do not rely only on a quiet message stream.
Read the last reported action and inspect any output it identifies. Treat an interrupted action as unverified until you check its destination.
If recurring work is involved, check the schedule separately and pause or delete the future runs you no longer want.
Record completed work, possible partial changes, and the first check required before a continuation.

Anthropic confirms you can stop or redirect work in its unified Claude guide (opens in a new tab). Accounts can have different interfaces during that change, so the visible task control is a better guide than an assumed button position. If the control is unresponsive, inspect the task on another supported surface and seek vendor help rather than assuming it stopped.

For a Dispatch-delegated task (opens in a new tab), open its underlying session: development work appears in Claude Code, and knowledge work appears in Cowork. Stop the actual run there. For a coding run, follow the separate Claude Code stopping guide.

Will closing the app or laptop stop the task?

Do not use closing a window as proof of cancellation. Anthropic explains that cloud work can continue after you leave the page or close a laptop. Work that reaches local files or apps still depends on the desktop connection, but interrupting that connection is different from confirming that the whole task was canceled.

Check the task’s own state and inspect any connected destination that matters. For example, a report may have been created in the cloud even though an attempt to save a local copy could not finish. Those are two different results, and a later session needs to know which one you verified.

The Cowork overview explains the broader workflow. If your difficulty is a failed or unresponsive run, the separate Cowork troubleshooting guide owns that diagnosis.

How do stopping a run and disabling access differ?

Stop the active run when you want the current work to end. Remove a capability when you no longer want the assistant to use it. These choices can overlap, but they are not substitutes: disabling one app connection does not establish that every other part of a task has ended.

Choose the control that matches your goal
Your goal	What to inspect or change
End the current run	Use the task’s stop control and confirm its state.
Prevent later recurring runs	Review the task’s schedule and pause or delete it.
Prevent desktop computer use	Review the computer-use setting in the desktop app.
Remove access to a connected service	Disconnect that service, then inspect any work already done there.

For computer use, Anthropic documents Settings > General, under Desktop app, and the Enable computer use setting in its computer-use guide (opens in a new tab). Turning that capability off is a capability change, not a universal Dispatch or cloud-task cancellation switch.

For a connected app, open Customize > Connectors, find the affected app, and disconnect it, as described in Anthropic’s connected-app controls (opens in a new tab). Keep a note of why you removed access so a future assistant does not immediately ask you to restore it without understanding the concern.

What should you inspect after stopping?

Check the effects of the task, not just its final message. Open the output folder or application and look for newly created files, changed records, and incomplete drafts. If a source file was modified, compare it with an authorized earlier version before deciding whether to keep or reverse the change.

Files: which were created, moved, replaced, or left incomplete?
Connected services: did a draft, message, event, or other record actually appear?
Verification: which results did you inspect yourself, and which are only reported?
Remaining work: what can safely continue, and what needs a person’s decision?

Stopping halfway through a sequence can leave a valid partial result. A document might have a finished outline but unfinished references. Keep the useful draft and mark its limits. Asking an assistant to “clean everything up” without identifying those limits can destroy evidence or overwrite work you meant to keep.

For example, if the task was organizing supplier documents, first list which documents moved and where they are now. Do not rerun the whole organizing request until you understand the partial arrangement. Save that checked state through the fenbs handoff workflow before anyone resumes.

How do you prevent another run or prepare a continuation?

If the task recurs, open Scheduled and review the relevant entry. Anthropic’s scheduled-task instructions (opens in a new tab) document pausing or deleting schedules. Check the current run independently; preventing tomorrow’s run and ending today’s work are distinct actions.

For a later continuation, state exactly what remains. Include the reason you stopped, the last verified result, and whether any decision or permission is still pending. A new assistant should not interpret “continue” as authorization to repeat every action from the original request.

Example checkpoint after a stopped task

Stopped because: The draft used the wrong source folder.
Confirmed complete: A new report outline was saved.
Keep: The outline and original source files.
Unverified: Whether the final table includes outdated figures.
Next: Check the table against the approved folder before changing it.
Approval: Do not send the report until a person reviews it.

Use fenbs AI context to keep the approved source and the stopping reason available together. If a recurring error caused the interruption, a lesson can explain what happened and what the next assistant should check first.

How fenbs helps

Keep the useful work when you stop the run

Save the finished portion and the remaining checks with the task in fenbs. Where we left off tells the next connected assistant why work stopped and what to inspect before continuing, without treating an interrupted run as complete.

Create a free account

Free for one person · No credit card · Works with Claude, ChatGPT, Cursor and more

How to do this with fenbs

Create a free account and add the project containing the stopped work.
Create or update the task with the intended outcome. Put the recovery steps, source locations, and current limits in its plan.
Record what you checked and what remains unverified. Save Where we left off with the stopping reason and first action for the next session.
Connect a supported assistant, ask it to read the context, and have it confirm the recovery plan before changing anything. Save progress again after the check.

fenbs does not stop Cowork or Dispatch, pause their schedules, or reverse their actions. If you only need to cancel one run, the task controls are the right place. fenbs helps when the partial work must remain understandable to whoever picks it up next.

Find more continuation routines in the AI handoff library. Keep the next action small enough that you can inspect its result before authorizing more work.