← Back home

Cloud & Local Data

Builds run in the cloud; model code can live in your own repo

Forgent3D has two entry points: prompt the cloud agent in the browser, or let your local agent drive it through the skill. Both run the same CAD engine — the difference is where the model code comes from and where it stays.

How the cloud agent handles data

  • - Prompts, generated model code, build output, and 3D previews live in your Forgent3D workspace.
  • - The CAD kernel and build environment are already running, so nothing is installed on your machine.
  • - Models are private by default and only appear in the public library when you explicitly share or publish them.

How the local skill handles data

  • - Your local agent writes the model code inside your own repository, where it can be versioned, reviewed, and maintained.
  • - Builds and geometry measurement still run in the cloud, and the built result plus its 3D link land in the same workspace.
  • - It fits people already working in Claude Code, Codex, or Cursor who want model code to sit next to the rest of their source.

How to choose

  • - Use the cloud agent when you want the fastest result, a demo, or something to share.
  • - Use the skill when model code should live in your repository alongside the rest of the project.
  • - For sensitive designs, decide first whether they should go to any hosted service; if you also connect external AI tools, review their context sharing, privacy, and retention settings.

Run the loop once, end to end

Sign in and generate your first model in the cloud, then install the skill if you want your local agent to model too.

Open Quick Start