Use the agent in Desktop
RunMat Agent works in the panel on the right of the Desktop window. It reads the project, edits files, runs code and simulations, and reads the figures and variables a run produces. Its edits arrive as changes you keep or undo, and its runs appear in the run header like your own.
Claude Code, Codex and other MCP clients on this computer can also work in your RunMat projects. See Connect Claude Code or Codex.
Start a chat
- Open the agent panel with the agent button in the top bar, between the runtime button and the gear.
- The panel names the open file and offers next steps for it: Run and inspect, Understand the code and Check compatibility. Select one, or type a request in the box at the bottom.
- Press Enter, or select the send button.
The open file is attached to the request; its chip sits above the box, and its × removes it. The + button adds other files or attachments as context.
Below the box:
- the mode menu chooses General for code and analysis, or FEA for setting up and running a simulation study;
- the model menu picks the model for this chat. Set the default in Settings › RunMat Agent, along with the reasoning effort.
Ask for a result you can check
Name the outcome and the evidence you want back:
Update the saturation logic in
controller.mso the output stays within ±12. Run the tests intests/andmain.m, then report the files you changed, the test results and the largest output you saw.
For an analysis, point the agent at the quantity:
Run
frequency_response.m, find the −3 dB frequency, compare it with the 250 Hz design cutoff and explain any difference using the computed variables and the plot.
Add constraints that change the answer: the entry point, the dataset, where to run, which files may change, and the numerical tolerance.
Review the agent's edits
Each file the agent changes is listed under its reply with the number of lines added and removed and a preview of the changed lines. Keep all accepts every change and Undo all reverts them. Each file also has its own undo.
Check the agent's runs
When the agent runs code, the run appears in the run header with its figures, variables and console output. Select it to read the same results the agent read, rerun it yourself, or continue at the >> prompt. See Go back to an earlier run.
To have the agent look into each failed run while you keep working, turn on Look into errors automatically in Settings › General.
Credits
Chats use Agent credits from your weekly allowance, and higher reasoning effort uses more. Settings › RunMat Agent shows what you have left. See Usage and limits.
Connect Claude Code or Codex
Settings › Connections connects coding agents on this computer to RunMat:
| Client | How it connects |
|---|---|
| Claude Code | Select Connect under On this computer |
| Codex | Select Connect under On this computer |
| Other MCP clients | Add the Desktop MCP server in the client's settings; see Other MCP-compatible clients |
The On this computer section finds Claude Code and Codex on this machine. Select Connect beside one; RunMat then appears in that tool's MCP servers as runmat, and the row reads Connected. Disconnect removes it.
The first time a tool works in a Project, RunMat asks in Connected agents: Allow while this project is open, or Always allow.
A connected client works on your RunMat projects through your account: it reads files, runs code and simulations, and reads results. MCP client calls that change something count toward your weekly allowance. See Coding agents on your computer for details.
Not yet releasedStatus A connected client can also attach to the project open in this Desktop window and use its live session: open editor buffers, the selected run, and the variables and figures already in the workspace. Desktop asks you to allow the project, shows which client is attached, and ends the connection when you open another project.