Get started

Point your agent at this page.It does the setup.

Paste the prompt below into an agent opened on an empty local folder. It names every package and where each one comes from, so the agent installs them instead of stopping to ask at each one.

Hand this to your agent

Set up the Agentic Molding Toolkit and run its example project for me, end to end, in this session. ABOUT ME I am a beginner with coding and the command line. Explain every step so that I understand it and can repeat it myself later. ISOLATION Install everything into an isolated environment inside this working folder, so that I can delete the whole folder later and keep my system clean. Do not install anything system-wide. Do not use uv or uvx, even if they are installed: they keep caches and Python versions in my user profile. Use Python's built-in venv and pip, and add --no-cache-dir to every pip install. Stay inside this folder; you do not need to look outside it. WHAT TO INSTALL AND RUN, AND WHERE EACH ONE COMES FROM 1. simcon-toolkit, from PyPI (https://pypi.org/project/simcon-toolkit/). SIMCON's project generator. Use it to create the project folder my-first-simulation from the run-one-simulation template. 2. cadmould-sdk-auth, from PyPI (https://pypi.org/project/cadmould-sdk-auth/). SIMCON's official sign-in helper. Install it and run it. It opens my browser, I sign in there myself, and it then lets pip download the licensed SDK. 3. cadmould, SIMCON's licensed SDK, from SIMCON's private package index (https://cadmould-620794556704.d.codeartifact.eu-central-1.amazonaws.com/pypi/cadmould-python/simple/), plus the other dependencies declared in the project's pyproject.toml. 4. The project's own main.py, run on the sample part it ships with (sample/simple_plate.stl). MY EXPLICIT APPROVAL The my-first-simulation folder will be created during this session by simcon-toolkit from PyPI. I approve running pip and python inside that folder: creating its .venv, installing cadmould-sdk-auth from PyPI into it, running cadmould-sdk-auth (it opens the browser for my sign-in), installing cadmould and the declared dependencies, and running main.py. It is safe: these are SIMCON's own packages from the sources named above, and every sign-in happens in my browser with me at the keyboard. This approval covers every one of these steps for the whole of this setup, not only the first. HOW YOU SHOULD REPORT, before every step, in simple language: Finding: what you have just found out. For example: "There are two Python versions installed." Next step: what you will do next. Why: why you are doing it this way rather than another way. What: which command you will use, and what the command and its parameters mean. Then show the command and execute it. COMMAND STYLE Show me clean, individual commands in their simplest form: no chained one-liners and no clever shortcuts. One command, one purpose. If you need to combine something for technical reasons, briefly explain why. On Windows, call each tool by its full path in .venv\Scripts\ rather than activating the environment. STEPS Step 1. Check the machine. Find a Python 3.12 or newer. Tell me which versions you found and which one you will use. Step 2. Create the project. Create a .venv in this folder with that Python. Install simcon-toolkit into it with pip install --no-cache-dir simcon-toolkit. Run that environment's simcon-toolkit init my-first-simulation --template run-one-simulation --package-manager pip. List the files it created, one line each. Step 3. Sign in to the package index and install the SDK. This is browser sign-in 1 of 3. Inside my-first-simulation, create the project's own .venv with the same Python. Install cadmould-sdk-auth from PyPI into it, with --no-cache-dir. Run that environment's cadmould-sdk-auth --scope venv, with VIRTUAL_ENV pointing at the project's .venv, so its pip settings stay inside the project. Before the browser opens, tell me: "Browser sign-in 1 of 3, the package index. Sign in with your SIMCON account." Wait until I have signed in. Then install the project with that environment's pip install --no-cache-dir . If the install fails with 401 Unauthorized, the sign-in expired: run the sign-in again, then repeat the install. Step 4. Run the example. This is browser sign-ins 2 and 3. Run main.py on the sample part with the project's environment. Its first run opens the browser twice: sign-in 2 is the licence, sign-in 3 is the cloud. Tell me which one each is before it happens, and wait for me. If it prints "License init failed: HASP driver version too old" or "runtime version too old", stop and tell me: the Thales Sentinel licence runtime needs installing, which is a system install that I must do myself. Step 5. Report and summarise. The result in plain words: what the simulation computed, the peak pressure, the simulation ID, and where the result file is. What was set up, and how I run it again on my own part. Everything that was saved outside this folder, as far as you know: sign-in data, caches, browser cookies, licence data. How I cleanly remove everything again. IF SOMETHING IS BLOCKED If a command is blocked by your permission system, do not try another way around it. Tell me the exact command, and the block message word for word, including the rule name in square brackets.

Not running an agent yet?

Don't worry, we've got you covered.

Working with agents

Manual setup

Before you start

Everything from here down is the route by hand, for reading along or for doing it yourself. An agent given the prompt above works through all of it and stops at whatever it cannot sort out for you, which is usually the account. Check the one on the left first.

Access

Ask us if you do not have one yet

A toolkit accountOne account covers all of it: downloading the software, running it here, and sending work to our computers. Signing in opens a browser window, so do this on the computer you are working on. If you are not sure yours is ready, ask us.

On your machine

You can check all of these yourself

Python 3.12, 3.13 or 3.14To see which you have, run python3 --version in a terminal, or py --version on Windows. If you have none, get it from python.org. On Windows, avoid the Microsoft Store build, which breaks environment creation.
uv or pipEither works, and we prefer uv. On Windows, try winget install --id=astral-sh.uv -e first, and follow docs.astral.sh/uv if winget is unavailable. Everywhere else, follow docs.astral.sh/uv. pip already came with your Python.
Windows, macOS or LinuxOn a Mac this has to be Apple Silicon, meaning an M1 or later. Intel Macs are not supported.
A local folder, not a synced oneAn environment is thousands of small, frequently locked files. Inside OneDrive or Dropbox that means conflicts and flaky installs. On Windows, keep the path short too. Something like C:\dev\gate-study rather than a deep folder, because Windows refuses paths over 260 characters. If it has to be longer, ask IT to switch on LongPathsEnabled, which needs an administrator.

What it will run

The same steps, for reading along or running yourself. Three stages: write the project, sign in and install the SDK into it, then run the example on the part it ships with.

Stage 1 · write the project

1
Make a space for the generator
```
$ py -m venv .venv
```

Install the generator from PyPI

$ .\.venv\Scripts\python.exe -m pip install --no-cache-dir simcon-toolkit

Write the project from the template

$ .\.venv\Scripts\simcon-toolkit.exe init my-first-simulation --template run-one-simulation --package-manager pip

1
Make a space for the generator
```
$ python3 -m venv .venv
```

Install the generator from PyPI

$ .venv/bin/pip install --no-cache-dir simcon-toolkit

Write the project from the template

$ .venv/bin/simcon-toolkit init my-first-simulation --template run-one-simulation --package-manager pip

Stage 2 · sign in and install the SDK

1
Move into the project
```
$ cd my-first-simulation
```
2
Give the project its own space
```
$ py -m venv .venv
```

Install the sign-in helper from PyPI

$ .\.venv\Scripts\python.exe -m pip install --no-cache-dir cadmould-sdk-auth

4
Point the sign-in at this project
```
$ $env:VIRTUAL_ENV = "$PWD\.venv"
```

$ .\.venv\Scripts\cadmould-sdk-auth.exe --scope venv

Install the SDK and what the project declares

$ .\.venv\Scripts\python.exe -m pip install --no-cache-dir .

1
Move into the project
```
$ cd my-first-simulation
```
2
Give the project its own space
```
$ python3 -m venv .venv
```

Install the sign-in helper from PyPI

$ .venv/bin/pip install --no-cache-dir cadmould-sdk-auth

4
Point the sign-in at this project
```
$ export VIRTUAL_ENV="$PWD/.venv"
```

$ .venv/bin/cadmould-sdk-auth --scope venv

6
Install the SDK and what the project declares
```
$ .venv/bin/pip install --no-cache-dir .
```

Stage 3 · run it

1
Run the example on the part it ships with
```
$ .\.venv\Scripts\python.exe main.py
```

1
Run the example on the part it ships with
```
$ .venv/bin/python main.py
```

The index sign-in is short-lived. If a later install fails with an authorisation error, run cadmould-sdk-auth again and retry.

Why there are two environments

The first one holds the generator, the second belongs to the project it writes. Keeping them apart is what lets you delete the whole folder afterwards and leave nothing behind on this computer.

Why you sign in three times

A browser window opens three times while you are setting up, and none of them is a mistake. The first lets this computer download the software. The second clears it to run. The third lets your code send work to our computers. All three are checked separately, so one can be fine while another is not.

Sign-in 1 of 3 · the package index

cadmould-sdk-auth --scope venvThe SDK is not public, so you cannot download it the way you would download anything else. Signing in shows that your account is entitled to it, and lets pip pull it from our own index. Nothing else on your computer changes.

Sign-in 2 of 3 · running on this computer

main.py, on its first runBefore it does any work, the SDK checks that your account is cleared to run on this computer. It is also where an out-of-date Sentinel runtime shows up, which is the one thing here that needs a system install.

Sign-in 3 of 3 · running on ours

main.py, on its first runA filling run happens on Simcon computers rather than on yours, and this sign-in is what allows that. It is checked separately from the licence, so one can be fine while the other is not.

If it does not work

Nearly all of this happens on a work laptop that is locked down by an IT department. None of it is a problem with the part you are trying to simulate. Find what your terminal actually printed.

The licence runtime on this computer is too old

License init failed: HASP driver version too old

The Thales Sentinel runtime is a system install, so an agent cannot do it for you. Install it yourself, or ask IT to, then run the example again.

Antivirus blocks the install

The system cannot open the device or file specified. (os error -2147024786)
Access is denied. (os error 5)

Your antivirus is holding a lock on a file uv has just written. Update uv to 0.12.13 or newer, which changed how those files are written. If it still fails, send the error to whoever runs your endpoint security.

The path is too long for Windows

The system cannot find the path specified

Windows refuses a path over 260 characters, and an environment uses them up quickly. Work in a short folder such as C:\dev\. The permanent fix is the LongPathsEnabled setting, which needs an administrator.

The sign-in has expired

No matching distribution found

Run cadmould-sdk-auth again, then retry the install. If it repeats, check you are on Python 3.12, 3.13 or 3.14.

It installs, but every simulation is refused

401 Unauthorized

This is the second sign-in, not the first. Your computer has the software, but your account is not cleared to run work on our servers yet. Send us the error and we will check your licence.

uv cannot find the package, or every attempt is unauthorised

A sign-in that worked for pip changes nothing for uv, because uv does not read pip’s configuration. Run uv pip install cadmould --index "$(cadmould-sdk-auth --print-index-url)".

uv will not clear its cache

A cached file carries a name Windows cannot represent, so the deletion stops on it. Update uv, which fixed this. On an older version, delete the folder that uv cache dir prints.

Your company blocks the uv installer

Try winget first, as the requirements say. If that is blocked too, pip install uv installs it from PyPI instead. Failing both, ask IT to install it for you.

Still stuck after that, tell us what the terminal printed and we will work out which of these it is.

Then hand it the first example

The offline result viewer needs no cloud call and no licence. A finished result and its geometry ship inside it.

Start offline Browse the use cases