HermesWatcher
Search⌘K For brandsSetup help
StartStart hereSetup plannerInstall Hermes AgentChat from your phoneYour first 24 hours
Use casesWorkflow blueprintsCase studiesUse-case collectionsCommunity libraryPrompt library
LearnWhat is Hermes Agent?Guideswitcheer's WingtipsTopicsFAQCommand cheat sheetGlossarySOUL.md gallery
ToolsTools & integrationsAll messaging platformsSkills directoryPlugins directorySkills, plugins & MCP
TroubleshootReleases
Work with usServicesNewsletterFor brands: partner with usFor AI agentsContactAboutFollow @HermesWatcher on X ↗ (opens in a new tab)

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

Republished in his own words, with credit.

witcheerBy witcheer · Nous Research

Back to wingtips

#12 · kanban's default worker workspace is scratch

· Scheduling & automation · CLI / Desktop / Gateway

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.

SourcesHermes docs: Kanban

All tips are written by witcheer and collected here with credit. Card images stay on his X posts.

witcheer says each tip ran on a real Hermes box before it shipped. Hermes changes fast, so check your version and the linked doc.