Skip to main content

​
Your Agent’s Brain on Disk

Everything Wolffish knows, remembers, and can do lives in ~/.wolffish/workspace/. This is your agent’s brain on disk — readable, editable, and git-versionable.

​
Directory Structure

​
Key Principles

Files are truth, cortex.db is cache. The SQLite database indexes everything above — episodes, knowledge, conversations (every message and tool call), task runs, feedback, usage, logs, and artifact metadata — and is fully disposable: delete it and Wolffish rebuilds it from the source files. A normal launch brings it current with an incremental mtime/size diff (~22ms); a full rebuild happens only when the index schema version bumps (~1.3 seconds for a 2GB workspace), never on every launch. Never edit cortex.db directly — edit the source files instead. Daily files over growing files. Episodes, feedback, and event logs are split by day (YYYY-MM-DD.md). This keeps individual files small, makes them easy to browse, and allows the brainstem to clean up old logs automatically. Capabilities are self-contained. Each folder under brain/cerebellum/ is a complete capability. You can delete any of them without affecting the core system. You can add new ones by dropping in a folder.

​
Inspecting the Workspace

Wolffish includes a built-in file viewer and markdown editor — you can browse and edit your entire workspace without leaving the app. For most use cases, it’s all you need. You can also open ~/.wolffish/workspace/ in any external editor if you prefer. Some useful things to inspect:

​
Touched folder chips

Along the top edge of a transcript there is a strip of folder chips — every folder the conversation changed files in, and how many. Each is one click from opening on your desktop, and it answers one question: where did this run work? Since v1.0.309 each touched directory collapses to the project folder that opens its tree, with the counts added up across everything underneath:
  • On a chat with no working folder set, every chip used to be labelled by the leaf of the path it happened to touch — …/wolffish-app/.github/workflows/ci.yml billed a chip reading workflows — so the folders you actually worked in were invisible.
  • Worse, work spanning two projects built the same way put two chips both named src on the strip, over two different codebases, with nothing to tell them apart. Now the chips read wolffish-app and wolffish-cloud.
  • The scan runs outermost boundary first — the first src, lib, test, docs or dot-directory on the path — while containers like apps are passed straight through, so the cloud desktop still bills as desktop rather than as a generic apps, and a .github folder folds into its project instead of claiming a chip of its own.
  • Paths outside the working folders keep a chip of their own, and a file changed directly in the working folder still bills it.

​
Version Control

You can git init the workspace directory to version-control your agent’s brain. This lets you track changes to personality, review memory evolution, roll back configuration changes, and share your agent setup with others.