What Agent Mode Does
Agent mode is the primary working mode in Trace. When you ask the AI to make a change — add a component, route a trace, fix a DRC violation, generate manufacturing files — it executes the change directly on your design files. The AI can:- Read your schematic and PCB files
- Make targeted edits (add/remove/modify components, connections, traces)
- Run ERC and DRC checks
- Generate Gerber, drill, and position files
- Search for symbols and footprints
- Take screenshots for visual analysis
- Create matched length groups
- Annotate reference designators
- Route traces (quick routing or advanced cloud layout)
When to Use Agent Mode
Agent mode is best for bounded, concrete tasks:
If your task has more than 3-4 steps or would benefit from research before execution, consider Plan Mode instead.
How It Works
When you send a message in Agent mode, the following happens:- Your message goes to the backend with your conversation history and project context.
- The AI reasons about what to do — you see thinking blocks stream in real-time.
- Tool calls dispatch — the AI requests actions like “read this file” or “write this component.” These execute locally on your machine.
- Results return — your app sends tool results back. The AI continues with that information.
- Changes sync — after all edits, the
.trace_schconverts to.kicad_schand your editor reloads.
The Activity Feed
As the AI works, you see an interleaved activity timeline in the chat:- Status messages — Friendly updates like “Reading schematic…”, “Adding component…”, “Running ERC…”
- Thinking blocks — The AI’s reasoning process, collapsible for review
- Text responses — Explanations of what was done and why
- Tool activity — Which files are being read or modified
Tool Execution
Tools execute locally on your machine — your design files never leave your computer. The server only sees tool results (e.g., “file written successfully” or “DRC found 3 violations”).File Tools
Design Tools
Server-Side Tools
These run on the backend (not your machine) and are also available in Agent mode:For the complete tool reference with all parameters, see Intelligent Tools.
Multi-Tab Parallel Execution
Each chat tab is an independent execution unit. You can:- Run Agent mode in one tab while asking questions in another
- Have two Agent tabs making edits to different parts of the design simultaneously
- Start a long routing task in one tab and continue working in another
Stopping and Connection Recovery
Stop
Click Stop (the ■ button on the composer or on your latest message) at any time. Stop halts generation on the server too — the AI doesn’t keep working (or billing) in the background after you stop it. What happens next depends on how far the response got:- Stopped before anything streamed — the round trip is cancelled cleanly and your prompt is restored to the input box, ready to edit and re-send.
- Stopped after partial output — the partial response (text, thinking, completed tool work) is kept in the conversation, so nothing the AI already did is thrown away.
Network drops
If your connection drops mid-response, the AI keeps working server-side and Trace automatically reconnects, continuing the response where it left off. If automatic reconnection fails, a Resume banner appears — click it to continue the same response without re-running your prompt or re-doing completed work.Versioning and Undo
Every edit the AI makes is automatically versioned:- Local history — git commits in
.history/(works offline) - Cloud sync — saved to Trace’s backend for cross-device access
- Per-message undo — click the undo button on any assistant message to restore the state before that message’s edits
Optimistic Concurrency
When the AI edits a file, it uses a hash-based safety mechanism:- Read the file + compute a hash
- Make the edit
- Before writing, verify the hash hasn’t changed (nobody else modified the file)
- If the hash matches, write succeeds. If not, the AI retries with the updated content.
Extended Thinking
For complex Agent tasks, the AI shows its reasoning in collapsible thinking blocks:- How it’s analyzing your design
- What tradeoffs it’s considering
- Why it chose a particular approach
- What constraints it’s working around
Todo Tracking in Agent Mode
For multi-step Agent tasks, the AI may create a todo checklist to organize its approach:- The todo widget appears in the chat panel
- Items update in real-time as the AI completes each step
- You can see exactly where the AI is in the process
Example Prompts
Adding Components
Modifying Values
Routing
Validation
Manufacturing
Research + Edit
Tips for Effective Agent Mode Usage
- Be specific about what you want changed. “Fix it” is vague. “Change R4 to 4.7k because the LED current is too high” gives the AI clear intent.
- One task per message for precision. For complex changes, break them into steps. This makes undo granular — you can roll back one step without losing others.
- Attach context when relevant. Drag a datasheet into the chat if you want the AI to implement a specific reference circuit.
- Let the AI run checks. After edits, ask “Run ERC” or “Run DRC” to validate. The AI can then fix any issues it introduced.
- Use multi-tab for parallel work. Route traces in one tab while reviewing the schematic in another.
Limitations
- Agent mode requires the desktop application (files must be local)
- Not available on the Free plan (Ask mode is free; Agent requires Pro/Ultra/On-Demand)
- Complex multi-step tasks may produce better results in Plan Mode where the AI researches and plans before executing
- PCB version rollback is limited — version restore is fully implemented in the schematic editor but has reduced functionality in PCBnew
Next Steps
- Ask Mode — when you want answers without changes
- Plan Mode — when the task needs research and approval
- AI Modes Overview — comparing all three modes
- Using Prompts — prompt writing tips
- Version History — understanding the undo/rollback system

