# witcheer's Wingtips #12: kanban's default worker workspace is scratch

Written by [witcheer](https://x.com/witcheer) at Nous Research. Republished with credit.

Canonical: https://hermeswatcher.com/wingtips/12  
Published: 2026-07-03  
[Original](https://notwitcheer.github.io/hermes-recipes/wingtips/12-kanban-s-default-worker-workspace-is-scratch/) · [On X](https://x.com/witcheer/status/2073051003482456511) · [Full collection](https://notwitcheer.github.io/hermes-recipes/) · [Official docs](https://hermes-agent.nousresearch.com/docs/user-guide/features/kanban)

[Source Markdown](https://raw.githubusercontent.com/notwitcheer/hermes-recipes/8653fb699a137a32e81936fa33cabacd3f4f2095/docs/wingtips/12-kanban-s-default-worker-workspace-is-scratch.md): use this file as the base for relative links in the verbatim text below.

Sources: [Hermes docs: Kanban](https://hermes-agent.nousresearch.com/docs/user-guide/features/kanban)


Hermes Wingtips #12: kanban's default worker workspace is scratch

you're handing a kanban task to a Hermes agent and want to keep the files it writes? one thing to know before you run it.

by default each kanban worker runs in a scratch workspace, and Hermes clears that workspace the moment the task completes. indeed, throwaway chores should not leave directories behind.

to keep the output, give the task its own workspace when you create it:

```
hermes kanban create "your task" --workspace dir:/absolute/path
```

two things to get right:

(1) name the workspace with dir: for anything you want to survive the run. no flag means scratch, cleared on completion.

(2) make the path absolute. Hermes accepts a relative path at create with no error, then rejects it when the worker spawns.