Skip to main content

Requirements

See Supported Software for the full list of supported CAD and simulation platforms. Nexus runs on Windows 10 or Windows 11 (64-bit), and on Linux (x86_64, glibc 2.28 or newer) — see Linux system requirements.

Connect in three steps

How long does this take? About 5 minutes end to end — roughly 2 minutes to download and install the Cosmon Connector, then it auto-detects your CAD/CAE software the first time you open it. No manual configuration required.
1

Sign in

Go to desktop-app.cosmon.com/login and sign in with your Cosmon account.
2

Install the Cosmon Connector

Download and install the Cosmon Connector on your engineering workstation. This is the bridge between Nexus and your installed CAD/CAE software.
The Connector runs locally on your machine. Your files and models never leave your workstation without your explicit action.
3

Open your software and connect

Launch SolidWorks, Ansys, COMSOL, or Abaqus. The Connector will detect the running application and establish a connection automatically. You’ll see a status indicator in the Nexus interface confirming the link.

Your first prompt

Once connected, try a simple command to confirm everything is working. In SolidWorks:
In Ansys Mechanical:
Nexus will describe what it’s doing and confirm the result.

Prompting Guide

The quality of your results depends on how you prompt. These eight rules will help you get reliable, precise outputs from Nexus every time.

1. Lead with outcome

Start with what you’re trying to achieve, not the specific operations you think are needed. Nexus can figure out the steps — your job is to define the goal.

Better

“Create a support bracket that can withstand a 200N downward load at the free end with a safety factor of 2 or greater.”

Worse

“Add a fillet here and make the wall thicker.”

2. Be specific

Include exact values: dimensions, tolerances, material grades, load magnitudes, mesh sizes. Precision in equals precision out.

3. Give file paths

When referencing parts, assemblies, or simulation files, include the full path. This removes ambiguity and ensures Nexus acts on the right file.

4. State what should not change

Tell Nexus which features, constraints, or dimensions are locked. This is especially important when editing existing models.

5. Chain steps

For multi-step workflows, list the steps explicitly and in order. Nexus will confirm progress at each stage before moving on.

6. Attach context

Share relevant background: design specs, applicable standards, prior results, or customer requirements. This helps Nexus make better decisions throughout the task.

7. Describe symptoms when debugging

When something isn’t working, describe what you observe — not the fix you think is needed. Nexus diagnoses better from symptoms.

Better

“The solver is failing at step 3 with: ‘Highly distorted elements detected near node 4521.’ It’s happening at the sharp re-entrant corner on the inner rib.”

Worse

“Fix the mesh error.”

8. Iterate

You don’t need to get the perfect prompt first time. Start with a clear goal, review the result, then refine. Nexus maintains context across the conversation.