Manage your work
A project gives related work a home. A conversation keeps one line of work together with its runtime, messages, and tool activity.
Start in the right folderCopy link to section: Start in the right folder
For a local coding agent, select the folder you want it to work in. Check that choice before the first message. The runtime's permissions still determine what it can access.
A B4 conversation uses its connection's agent route instead of treating your Mac folder as the server's workspace.
Name and find conversationsCopy link to section: Name and find conversations
The app gives a new conversation a title based on its first message. Rename it when a more specific title would help you find it later.
Use the command palette to search conversation titles. Pin the conversations you return to often. Archive completed work to move it out of the active list; use the sidebar's archive view to find it again.
Keep the context usefulCopy link to section: Keep the context useful
Ask follow-up questions in the same conversation when they depend on earlier work. Start a new conversation for a separate task or a different runtime. A provider change does not migrate another runtime's private session context.
Closing, quitting, and logging outCopy link to section: Closing, quitting, and logging out
The window and the background coordinator have separate lifetimes. Read any active-work prompt when quitting or logging out. Logging out stops local work as part of closing the account; a remote B4 run can continue on its own server.
When you return, check the turn's reported state before sending another request. If it is unresolved, use the app's recovery action rather than guessing whether the work ran.