Brews

A brew is an agent session in Coldtea.

Use the Brews sidebar when you want to get back to a session, see which project or worktree it belongs to, or decide whether to reopen, fork, rename, or delete it.

What shows up as a brew

A brew usually comes from one of three places:

• A plain terminal agent session.
• A task-linked session started from the Tasks surface.
• A worktree session created for isolated branch work.

The row shows the agent, the session title, recent activity, and any worktree or cloud-run signal Coldtea knows about. The exact actions depend on the agent and the session record. For example, OpenCode sessions can expose resume and fork actions because OpenCode has session IDs Coldtea can use.

Opening a brew

Opening a brew brings the session back into the workspace. Depending on your settings and the current pane, Coldtea may ask whether to replace the active pane or open the brew in a new tab.

If you always want resumed brews to open in their own tab, turn on Open brews in a new tab in Settings.

Before you send a follow-up prompt, check the path and branch. A resumed session still needs the same care as a terminal you never closed.

Naming and pruning

Rename a brew when the generated title is too vague. Good titles are boring and specific:

• Fix login redirect
• Docs feature pages
• Review COL-290 diff

Delete old brews when the session no longer helps you. Deleting a row removes Coldtea's session record, and for agents with their own saved-session command, Coldtea may also ask the agent CLI to delete the underlying saved session.

Do not keep stale brews as a memory system. Put lasting context in a task, plan, or session log.

Worktree and task context

A brew can be tied to a worktree or a task. That is the useful version of history: not “here is some terminal output,” but “this agent was working on this task in this branch.”

Use task-linked brews when the work needs review or handoff. Use a plain brew for quick local questions and throwaway experiments.

When to fork instead of continue

Fork or start fresh when the old session has the wrong assumptions, too much stale context, or a path you no longer trust.

Continuing is best when the next instruction is obvious from the current terminal state, task, plan, or diff. If you have to explain the whole job again, a fresh brew is usually cleaner.

Next: start or continue agent work or review the core brew model.