HOOOK

Projects

A project is a folder on disk with an AGENTS.md file in it. That simplicity is the point: nothing is locked inside the app.

What a project gives you

Creating a project makes a real directory under your workspace and writes an AGENTS.md into it: 

~/.hoook/workspaces/<workspace-id>/projects/<project-slug>/AGENTS.md

You can edit that file in the app or in any editor. Rename the project and Hoook renames the folder to match. Delete it and the row and folder go together. There is no proprietary format and nothing to export.

Writing AGENTS.md

AGENTS.md is where you put the context an agent should always have: what the project is, tone and constraints, what to avoid, useful background. Plain markdown, no schema.

AGENTS.md is also the file that Claude Code, Codex, and several other agent CLIs read on their own when started in a directory. So the file is useful in an agent tab today regardless of what Hoook does with it, because the agent reads it directly from disk.

Projects and chats are not linked yet

This is the important caveat, and it is easy to be misled by the UI. The daemon knows how to fold AGENTS.md into a chat's system prompt, but the app does not yet tell it which project a chat belongs to. In practice, project instructions do not reach your chats. The plumbing exists on both ends and is not connected in the middle.

Until that is fixed, treat AGENTS.md as instructions for agent tabs, which read the file themselves, and paste any context you need into chats manually.

Known gaps

  • The Skills panel inside a project always reads "No skills installed". It is not connected to the skills API, even if you have skills installed.
  • Knowledge has an Add button that does nothing yet.
  • Transfer and Archive are visibly disabled.
  • There is no Brand entity, despite brands appearing in marketing material.