Tasks and projects

Projects and tasks#

A project is an opened local folder or repository. A task is the focused coding conversation and run associated with that project. Keeping those levels separate makes it possible to return to a feature, investigation, or review without losing the project context. The project remains tied to the selected folder on the desktop computer.

Start or continue work#

Choose File → Open project… to open the project chooser. Open folder selects an existing folder, Clone repository brings a repository into the local workspace, and Create project creates a new folder with Git initialized. In the left navigation rail, Projects lists available projects. Each project exposes New chat in <project>, which starts a task in that project. New chat in the rail starts a task from the current Code context. Selecting an existing task returns to its transcript and current work surfaces.

The composer prompt is labeled Task message. Context files, slash skills, and @ references can be added before sending. The task model, reasoning setting, permission, and delegation mode are visible at the composer. Task tools on the right keep Files, Git, Agents, and Usage beside the conversation, so evidence can be inspected while the task remains open.

Organize the rail#

Task rows provide actions such as Pin or Unpin, Rename, Archive or Restore, and Delete. Search chats narrows the visible task list. Archived switches the rail to archived projects and chats; the Settings → Archives area provides a broader archive view. A task can be reopened after a desktop restart when its local project and state remain available. A local archive is not an account-synced Code history.

Continue from another surface#

The paired mobile Remote library groups projects and tasks by computer. Remote → Search remote chats locates a task, and selecting it opens the desktop-backed transcript. The phone can send task messages and inspect permitted work surfaces, while the desktop retains the project, runtime, terminal, and Git controls. Account-backed Chat conversations use the Chat surface and account services rather than the local Code project model.

Keep project context clear#

Opening a different project changes the folder context for new work. A task should be continued in its listed project when file paths, terminal commands, or Git changes depend on that folder. Code files, Quickstart, and Troubleshooting provide adjacent guidance for project selection and recovery.