Give your app a home
3 minute read · Projects & Git
Your project is the folder that contains your app. A workspace groups projects; a conversation holds the instructions and decisions around a piece of work. For a first app, one workspace, one project and one chat are enough.
- Choose how the project starts
- Keep the conversation attached to the right work
- Return to the same project tomorrow
- Keep a workspace useful as the app grows
Choose how the project starts
| Starting point | Action | Result to check |
|---|---|---|
| An idea with no files | Start a chat and ask the agent to create a named project. | A chosen local folder, detected stack and setup steps. |
| An existing app | Open its existing folder. | The correct files and repository appear; nothing is scaffolded over them. |
| An existing repository | Clone the repository into a chosen location. | The expected branch and checkout, followed by dependency setup. |
Give the workspace a recognizable name, such as Personal projects, and the project a specific app name. Moving a project between workspaces changes its organization; it does not relocate the physical checkout. Reordering the sidebar also leaves the folder untouched. A worktree created for a chat belongs to its parent project while keeping its own branch and directory.
Keep the conversation attached to the right work
Open the project before starting a task that should change it. If a conversation can access several projects, tell the agent which one is the target and inspect the selected project context. For example: “In Small Stories, add an article editor. Leave the shared component library unchanged.” Selecting a workspace is not blanket permission to edit every folder on the computer.
A standalone conversation can later be bound to a real project. Its conversation history stays available. Open an isolated worktree when two changes need independent checkouts; simply opening two chats keeps them on the same files unless you choose isolation.
Return to the same project tomorrow
Reopen the existing entry, confirm its local folder and use Start app if the process has stopped. On another device, bind the synchronized project to that device's checkout. If the path is missing, choose or clone the correct folder instead of creating a duplicate project record. Preview and parallel work explain the next steps.
Keep a workspace useful as the app grows
Group related projects together, such as a customer website and its internal dashboard. Give each chat a specific result: “Article search” is easier to revisit than several entries called “New chat.” Pin ongoing work and archive conversations you want to retain without keeping them prominent. Moving or reordering entries changes their organization, not the project files.
When work crosses projects, name both the responsibility and the boundary: “Read the API response in the server project, then update only the dashboard to match it.” Use linked tasks for a separate project conversation that needs its own instructions and result. Check both sides of the interaction before calling the change complete.
A missing folder, a stopped process and a locked Vault need different fixes. Choose the correct checkout for a missing path, use Start app for a prepared project whose process has stopped, and unlock the account's existing Vault for encrypted cloud data. Do not delete and recreate the workspace to clear one of those errors. Your saved organization, chats and local checkout are separate pieces of the work.