SUZENT / Docs
THE SUZENT HANDBOOK

Organizing work into projects

Use projects to give related chats a shared folder, standing context, and one list of goals and tasks.

A project is how you keep one piece of ongoing work together, such as a report, a codebase, or a trip you're planning. Every chat in a project shares three things:

  • A library folder. Notes and deliverables saved in one chat are there in the next, and other projects can't see them. See What goes in the project library.
  • Project context. A short note, context.md in the project folder, that every chat in the project reads first. The agent keeps it up to date with the project's goal, current state, decisions, and a list of the files in the library.
  • A task list of the project's goals and tasks, from every chat.

When to start a project

Start one when work will span more than one chat, or when it has files you want kept apart from everything else. Quick, one-off questions are fine in Home, the project new chats go to by default. Chats that arrive from chat apps go to Social.

Create a project from the Projects list in the sidebar, or pick one on the new-chat screen. A chat can be moved to another project later; deleting a project moves its chats to Home.

To move or delete several chats at once, select them the way you would select files on your computer:

  • macOS: ⌘-click adds a chat, ⇧-click selects a range, ⌘A selects every chat in view, and ⌘⌫ deletes the selection.
  • Windows and Linux: Ctrl-click adds a chat, Shift-click selects a range, Ctrl+A selects every chat in view, and Delete deletes the selection.

Selected chats are highlighted. Right-click any of them to move or delete them all together. A plain click or Esc clears the selection.

Project settings

Open a project's settings from the ⋯ menu next to it in the sidebar's Projects list, or right-click the project. Home and Social have settings too, though they can't be renamed.

Folders gives every chat in the project access to folders on your computer, such as the codebase the project is about and a folder of reference material. The first folder is the project's working directory: chats start there, relative paths resolve inside it, and the agent can edit files there without asking. The other folders are mounted for every chat in the project, alongside any the chat mounts itself. Use Set as working directory on a folder to make it the first one.

Under the list, Suzent offers folders this project's chats already used and folders you picked recently; click one to add it, or use Choose a different folder to browse. With no folders, chats work in the project's scratch/ folder.

A chat that already has its own working directory, for example one opened from an editor, keeps it. The project library, including context.md, stays in the project folder. Changes apply from each chat's next message.

Give it standing instructions

Project context is the place for anything every chat should know: the goal, the audience, decisions already made, conventions to follow. Open the Context tab in the chat's side panel and click Edit to write it yourself, or ask the agent to note something there.

When the agent works in a folder that has an AGENTS.md or CLAUDE.md file, it follows those instructions too. If there are several, the one closest to the working folder wins.

Project context is about this project. What the agent learns about you is kept in memory and applies everywhere.

See what uses the context window

The Context side panel shows a colored usage bar and category totals for messages, tool calls and results, system tools, MCP tools, skills, memory, and repository instructions. Tool, skill, memory, and repository categories with source details can be expanded to see their individual contributions. Expand Memory & project context to find Project context (context.md) and its estimated token usage. Only the portion loaded into the model is counted. Older saved breakdowns combine core memory and project context; send another message to collect the file-level breakdown. Project context and repository instruction files are listed below; open a file to read its contents.

Counts marked ≈ are text-length estimates, not exact model token counts. The provider's input count for the last request is shown separately when available. Images and provider-managed content may add costs that the text estimate cannot measure. Compaction reserve is space budgeted before automatic compaction; tools marked not loaded are listed separately and excluded from used space.

The breakdown updates during a chat and is saved when the turn completes. Older chats need a new message to collect it. After manual compaction, the total updates immediately and the next model request refreshes the categories.

Track task progress

Set a goal with /goal and the agent keeps working until it's met. The task panel shows this chat's goal and execution steps, with Pause and Resume for automatic goal progress. Entire project in the same panel shows work across conversations, prioritizing anything that needs your input. Click a task to return to its conversation and review its results. The agent maintains the states; you can focus on the work itself. See Tasks & planning and Goal mode.

Keep an eye on what it's doing

The chat's side panel shows what the agent is working with: its files, the pages it read, interactive panels it shows you on the Canvas, and commands or sub-agents running in the background. Open a background task to follow it, stop it, or redirect a sub-agent.

Edit this page on GitHub ↗

On this page