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.

Signed-in projects sync in both directions in the background, normally every 30 seconds and when the connection returns. Opening a project or loading the home screen waits for the current sync attempt before reading the local list. The home screen updates when cloud projects arrive. Sync itself costs no credits and does not require a paid top-up.

If a cloud download fails, projects already cached in this browser can still open. A link to a project that is not cached stays on its project URL and retries the download instead of treating the project as deleted.

Switching browsers or devices

Use the same Google account and let the original browser finish syncing before continuing elsewhere. Reopen the project on the second device to load the available cloud revision. Simply opening or closing an unchanged editor does not create a new revision.

This is not collaborative editing: changes to the same project are not merged. If you edit it in multiple tabs, browsers, or devices at once, the snapshot with the latest recorded edit timestamp wins. Use a separate project for parallel work. A project already open in an editor does not live-update its viewport when another device edits it; reopen it before continuing.

Generated CAD, parameters, and chat sync. Checkpoints and renders remain in the original browser profile. Original imported sources up to 10 MiB each can restore automatically; larger sources stay local-only. For a complete handoff with imported geometry, download a .p2cad project file on the original browser and open it on the other device. See Importing CAD files.

Submitted messages and support records

When you are signed in, text and images received by the chat service are also saved privately for support and acceptable-use review, including requests that fail or stop at a credit gate. Saving this record costs no additional credits. It is separate from project sync and does not provide an in-app history restore or guarantee that every image appears on another device. To request account-level deletion of these records, contact support@prompt2cad.com. Clearing browser data alone does not remove server records.

Signed-out projects

If you start designing without signing in, the project lives only in this browser. Signing in from its open editor associates that project with your account; it does not transfer every other anonymous project in the browser. 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.

Project files

Use Project → Download project file (.p2cad) to save the complete project: its model, parameters, chat history, and local project metadata. Open it later from Project → Open project file.

Downloading a .p2cad file unlocks after your first top-up and the paid entitlement remains on your account for life. Downloads are temporarily suspended only if the balance falls below the −10-credit chat grace margin. Opening a project file is not gated. A .p2cad is a Prompt2CAD backup and handoff file, not a CAD interchange format; use STEP, DXF, GLB, or another export format for downstream tools.

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).

Acceptable-use checks

Chat requests are checked against the acceptable-use policy before generation. Clearly prohibited requests are blocked; if the check is unavailable, retry later. A blocked project cannot be exported. These checks do not certify geometry or replace your own engineering and safety checks. The checks themselves do not consume customer credits; generation and export eligibility follow the usual billing rules.

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: Importing CAD files — open DWG, DXF, SketchUp, OBJ, STL, GLB, or self-contained glTF models and continue designing them with the agent.