Give agents your simulation and 3D data
Engineering results sit in desktop tools and in files too large for an agent to read. CoDim moves them to the cloud and gives agents tools that answer spatial questions on the full-resolution data. Your team sees each answer in the live 3D scene.
Which of the three bracket designs cuts peak stress the most?
I'll compare the three runs in the project.
codim dataset_list(Bracket study)
Baseline, Design A, Design B
codim extremes_locate(von_mises)
Each peak sits at the inner fillet
codim mesh_compare(Baseline)
Design B peak 23% lower, Design A 9% lower
codim scene_actor_set(von_mises)
One color scale across all three
codim view_screenshot
Captured Design B at the fillet
codim scene_report
Summary posted to the review thread
Design B cuts peak stress the most, 23% below the baseline at the inner fillet. The report is in the review thread.
Inspect
Dataset overviews, field statistics, and spatial summaries, returned as typed results sized for a context window.
Analyze
Probe points and lines, locate extremes, compare fields between meshes, and run filters from the catalog in the cloud.
Drive the scene
Create scenes, add datasets, set color maps, opacity, lighting, and camera, and capture the live view as an image.
Report
Post findings to the scene's threads, where the team reviews them next to the 3D data.
Agents act as the user, and every call is logged
An agent sees only what its user can see and changes only what that user can change. When it gets something wrong, the scene history shows what it did and on whose behalf.
- Agents sign in with OAuth and act as the user, with that user's permissions
- Scopes limit an agent to reading, analysis, scene edits, or collaboration
- Changes to shared scenes wait for the user to approve them
- Every tool call is logged, and scene edits are marked as made by an agent
- Text people typed into the data reaches the agent marked as untrusted
- Responses are capped, so a large dataset cannot flood the context window
Works with the agents your team uses
The CoDim MCP server is a remote server with standard OAuth sign-in. Connect Claude, Cursor, or any client that speaks MCP, and we turn it on for your workspace.
Point an agent at the dataset that breaks your tools.
Send us a run or a scan your team struggles to open. We will load it into CoDim and connect your agent to it.