Projects

A project is one design conversation: the chat history, the current geometry code, the parameters, the checkpoints, and the cached renders. The Projects icon in the header opens the project manager.

Creating a project

There are two paths:

• New Project button in the project manager — opens an empty editor.
• Sign in for the first time — your first conversation creates a project automatically, named "Untitled Project" until either you rename it or the agent suggests a name based on the first model.

Each project is independent. The agent does not see what is in other projects unless you explicitly paste the context into a message.

Switching projects

Open the project manager and click any project to switch. The chat panel, viewport, and parameters all swap to that project's state.

Naming and renaming

The header shows the current project name. Click it to rename — type a new name and hit Enter. The change is local until the project is synced to the cloud (next section).

The agent will also suggest a name once your first model is built. The suggestion appears as a small chip you can accept or dismiss.

Where projects live

This is the most important thing to understand:

• Locally on your machine — every project, signed in or not, is saved in this browser, on this profile. Clearing your browser data deletes them.
• In the cloud — projects belonging to signed-in users are also synced to the server, tied to your Google account. Switching browsers or devices, you sign in and the projects re-appear.

The sync is one-way mirroring: your local copy is the source of truth while you are editing; the server gets an updated copy when meaningful state changes (a turn finishes, parameters changed, the project is renamed). Race conditions are rare but possible — if you edit the same project simultaneously in two tabs, one window's changes will overwrite the other's on next sync. Don't do that.

Signed-out projects

If you start designing without signing in, the project lives only in this browser. Signing in later does not back-sync those local projects to the cloud — they stay local. Export anything you care about before clearing browser data.

Deleting a project

Project manager → trash icon next to the project. Confirms once. Local copy is removed and the server is told to delete the cloud copy as well.

There is no recycle bin. Deleted projects cannot be recovered. Export STEP / GLB / PNG before deleting anything you might miss.

Checkpoints, not project history

Each project has its own checkpoint stack (see Iterating). Checkpoints are local-only by design — they are large (a full snapshot of the model at one point in time) and they are scratchpad state, not finished work. They do not sync to the cloud and do not survive clearing your browser data.

If you want a state to be portable, restore the checkpoint, then export the geometry as STEP / GLB.

Multi-file projects

A project can hold more than one "file" — sub-designs within the same conversation. Use the + in the file switcher to add a new one. Examples:

• Designing a kitchen with two cabinet runs as separate files in one project, so the conversation context is shared.
• Iterating two variants of the same piece in parallel ("modern A" and "modern B") to compare.

Each file has its own geometry code, parameters, and checkpoint stack, but they share the project's chat history.

Renders gallery

Photorealistic renders (see Views and screenshots) are stored separately from the project geometry, in your browser. They show up as a strip at the bottom of the viewport and persist across sessions. Renders are local-only — clearing browser data wipes them, and they do not sync to the cloud (they are large, and easy to re-generate).

Token limits

Conversations are unbounded in principle but auto-compact once they grow past a soft limit (around 600k input tokens). Compaction summarises the oldest messages so the agent keeps the important context without paying for the full transcript every turn.

You will see no UI for this — it is transparent. If a very long-running project ever starts behaving as if it forgot something, that is the cause; pasting the key fact back into the chat fixes it.

Next: Exporting overview — how to get the model out of Prompt2CAD.