Chats & Projects

Conversations

• ⌘N starts a new chat; ⇧⌘N opens a second window. Every chat keeps its own model and streams independently.
• Pin, rename, and delete from the sidebar; ⌘F searches inside a chat, the sidebar field searches across all of them.
• A green dot beside a chat means it is running now; a grey dot means it ran earlier this session. The trail clears when you quit.
• Each reply shows the model, duration, and token/cost figures; expand the activity card to see every step the agent took.
• Return sends; Shift+Return starts a new line. The field grows with your text, then scrolls.
• Attach images with the paperclip, drag-and-drop, or ⌘V (up to 6); click a thumbnail to enlarge, copy, or remove it.
• The right pane shows the project's Files and the run's Artifacts; select one to preview it. Code and config files are syntax-colored, images and PDFs render inline, and Open hands anything to its own app.
• Share or export a chat — right-click it in the sidebar: Share… opens the macOS share sheet (Mail, Messages, AirDrop, Notes), Copy as Markdown puts it on the clipboard, Export as Markdown… saves a file (also ⇧⌘E). By default that is the conversation only — what you and Naseem said, no tool calls. With Tool Details offers the same three with one line per tool call, for when someone needs the trail. File → Import Conversation… brings a file back as a new chat, in its project if the name matches.

How a run works, start to finish

• You send a request. The chat model — the one in the header menu — reads it together with your project notes, the profile's instructions and the tools it may use.
• It plans and works. It reads files, runs commands, drives the Simulator, and so on, asking first where approval is required. If the job has independent side tasks and sub-agents are on (Pro), it hands each one to a sub-agent: a fresh helper with only that task, running on the sub-agent model. You see N sub-agents working while they run; only their summaries come back to the chat model.
• The chat model writes the answer. Every reply you see is written by the chat model — never by a sub-agent, never by the reviewer.
• Checks run before you see it. Built-in checks first: did it actually use tools when the task needed them, and does every file it says it created exist on disk. Then, if your profile names a review model (Pro), that model reads the request, the answer and the list of tool calls, and returns pass or fail with a reason.
• Pass — the answer is shown to you unchanged. The reviewer adds nothing to a good answer.
• Fail — the reason goes back to the chat model, not to you, as not complete yet, here is why; reply with the complete answer. The chat model fixes it, by itself or by delegating again, and the checks run once more. You see the send-back as a small note in the activity card.
• It always ends. At most two reviews and three send-backs per run; after that the run stops and shows the chat model's last answer, so a strict reviewer can never trap a run.
• Afterwards, Usage & Cost lists every call by model: the chat model's turns, the sub-agents' calls, and the reviewer's call.

Project notes

• Naseem keeps notes inside each project, in a naseem/ folder you can read, edit, and commit: project.md (what it is, stack, how to build and test), roadmap.md (Done, In progress, Next, Known issues) and journal.md (one line per run).
• Start with the card — in a new project chat, Set up this project writes the first two files from the code. After that, every chat reads them first, the start cards come from the roadmap's Next items, and Naseem updates roadmap.md and journal.md after runs that change the project.

Projects

• A project groups related chats around a shared working directory — every chat in the project reads and writes the same folder.
• Use one project with several chats (e.g. one per profile) to run a small team over the same workspace.
• A new chat inside a project starts with cards about that project, drawn from its notes (see Project notes above). Set the projects folder in Settings → General so new projects land where you keep code.
• Right-click a project → Color to tint its folder icon and name so it stands out in a long list.