# witcheer's Wingtips #37: hermes project

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

Canonical: https://hermeswatcher.com/wingtips/37  
Published: 2026-08-01  
[Original](https://notwitcheer.github.io/hermes-recipes/wingtips/37-hermes-project/) · [On X](https://x.com/witcheer/status/2083587946574389358) · [Full collection](https://notwitcheer.github.io/hermes-recipes/) · [Official docs](https://hermes-agent.nousresearch.com/docs/reference/cli-commands)

[Source Markdown](https://raw.githubusercontent.com/notwitcheer/hermes-recipes/8653fb699a137a32e81936fa33cabacd3f4f2095/docs/wingtips/37-hermes-project.md): use this file as the base for relative links in the verbatim text below.

Sources: [Hermes docs: Cli Commands](https://hermes-agent.nousresearch.com/docs/reference/cli-commands)


Hermes Wingtips #37: hermes project

real work rarely fits in one folder: an api repo, a web repo, an infra repo, all one product. a project gives that group one name.

(1) `hermes project create "My App" ~/code/api ~/code/web` creates one 

(2) `hermes project add-folder` grows it

(3) `hermes project use` sets it as active

what is super cool is that the Desktop app groups your sessions by project automatically, and binding a kanban board with `bind-board` gives every task a deterministic worktree and branch convention.