Every engineer knows the part of the job that never makes it into the design review highlights. It’s the worst-case check you redo because a part changed. It’s the sizing calculation rebuilt for the third project in a row. It’s the report that has to record every step, so someone else can follow your work and sign it off.

Today we’re launching Maple Loop, an AI engineering agent from Maplesoft built to take on exactly that work. Here’s what it does.

Give it a problem, not a formula

Working with Maple Loop starts the way you’d brief a colleague. You describe the problem and point it to your files: schematics, datasheets, requirements, test data. Here’s a prompt from one of our worst-case circuit analysis runs:

“Our 3.3 V rail monitor resets the processor when the rail drops. The reset has to happen between 3.00 V and 3.20 V. Will that work with the parts we chose?"

From there, Maple Loop plans the work and moves through it the way an engineering team would: requirements, design, analysis, verification. It checks each phase before moving on. When it’s done, it comes back with the tolerance build-up for each part, the part costing the most margin, and a ranked list of fixes with what each one buys you.

You can start from a blank prompt like this one, or from a template for common jobs such as worst-case circuit analysis or PID control design. See it in action. 

Why the math runs in Maple

This is the part we care about most. General AI tools are good at producing answers, but in engineering an answer you can’t verify isn’t worth much. A plausible number from a language model can be wrong in ways that are hard to spot, and it gives your reviewers nothing to check.

So, Maple Loop splits the job.

 

You get the engineering, not just the answer

What comes back isn’t a chat transcript. It’s working files in tools you already know, with the full calculation inside.

Calculations arrive as Maple Flow documents, laid out like a clean hand calc with units carried through every step, ready for review. Full derivations come as Maple worksheets. And when a problem calls for system behavior, Maple Loop builds a MapleSim model you can simulate and tune.

The rest of the team doesn’t need Maple to benefit. From the same checked calculation, Maple Loop can produce Word reports, PDFs, Excel workbooks, PowerPoint decks, generated code and shareable dashboards.

Because everything is built on live Maple documents, the work doesn’t go stale. When a part changes, you change the input and rerun, and the analysis and documents update together. The next design revision starts from a working calculation instead of a blank page.

A new way to put Maple to work

Maple has always been about getting the math right. With Maple Loop, we’re putting the same engine to work in a new way, at the center of an AI agent that carries engineering projects from the first prompt to a reviewed result. It’s a natural next step for Maple: the same math you already rely on, now doing the work inside an engineering workflow.

Get access to Maple Loop

We’ve been testing Maple Loop with engineering teams on real problems across electrical and mechanical work, and many more.

Join the waitlist for access to Maple Loop.

What routine analysis would you hand off first? Which workflows should we focus on next?

Tell us in the comments.

Please Wait...