Skip to content

Projects and chats

A folder you work in. Aether keeps a project once you add it or chat in it, and groups its chats and worktrees under it in the sidebar.

A collapsed project shows how many chats it holds and the most urgent status among them, in this order: Waiting, Running, Failed, Done, Idle.

A Git worktree under a project. In the sidebar it is a nested group holding every chat whose folder is inside that worktree. Chats in the main checkout stay at the project’s top level. See Git and worktrees.

A chat run by a provider CLI inside a project. Each agent chat holds one live CLI session.

A chat with an OpenRouter model and no project. Direct chats cannot be leads.

An agent chat with Lead turned on. Its CLI gets tools to start, message, read and stop child chats. See orchestration.

A chat’s unsent composer text plus its attachments. Drafts survive switching chats, moving panes and restarting the app.

A file or image added to a message. The chat keeps its own copy in Aether’s attachments folder, so the message still works after the original moves or changes. Every CLI must be able to read that folder.

The folder a chat’s CLI runs in. It is fixed on the first send, to the project folder or a worktree.