Working in Buff Code
Everyday work in Buff Code: a session with the agent, changes and undo, plan and goal, side conversation, Git, automations, workflows, extensions.
This section is about everyday work: how to give the agent a task, follow what it does, check and undo changes, run large tasks and hand over repetitive work. Installation, sign-in and what the organisation provides are described in the neighbouring sections: Installation, Sign-in and working context, Models and usage.
Buff Code is a window (an app for Linux, macOS and Windows) and the buff console. They share one
core: sessions, pins, automations, workflows, extensions and the language are common. The pages describe
the window; what is done and how in the console is at the end of each page.
Where to start
- Open the project folder — on Home, “Projects” → the folder icon.
- Describe the task in the input field. The agent reads the code, makes edits, runs the tests and tells you what it did.
- Check the changes — under the answer there is a “Changed N files” summary; a click opens the diff. Don’t like it — “Rewind the turn”.
- Commit — the branch chip under the input field opens the Git window; the agent can suggest the commit message.
Pages in this section
| Page | About |
|---|---|
| The window and the session list | Home, the session column, pinning, groups, archive, the session state in a word, searching the conversations |
| Session: input field, modes, questions | the “+” menu, permission modes, permission requests, the agent’s questions, attachments and quotes, background work, balance |
| Changes and undo | the turn summary, the changes panel, safe undo, the file tree and file view |
| Plan, to-do list and goal | a plan with approval, the agent’s to-do list, the /goal goal with a check after every turn |
| Side conversation | a question along the way without derailing the main task |
| Git in the window | changes, a commit with a message from the agent, push, branches, history |
| Automations | scheduled tasks for the agent — even with the window closed |
| Workflows | subagents working in phases with a result; save and run again |
| Extensions | MCP servers, skills, commands, subagents, memory, hooks, trust |
| Settings and first launch | introduction, language, theme, text size, keys, proxy |
Everything is recorded
Every turn — yours, an automation’s or a workflow’s — is recorded in the organisation’s data just like an ordinary development session: it is visible in the workspace, you can ask questions about it, and usage is charged to the organisation’s plan. In detail — Development sessions.
Commands
Reference for the buff console and the commands inside Buff Code: context, modes, goal, side conversation, undo, Git, automations, workflows, extensions.
The window and the session list
How the Buff Code window is laid out: Home, the session column with pinning, groups and archive, the session state in a word, search by title and conversation.