Trace brings research, design assistance and checks into your workflow. You do not need to memorize internal tool names: describe the task, choose its scope and inspect what the assistant actually did.
Research and explain
Use Ask for questions that should not change your files:
- “Explain the power path on this sheet.”
- “Compare this exact part's operating limits with my supply and load.”
- “What should I check in this datasheet before choosing the package?”
Provide the relevant datasheet or use Add to Chat where supported to identify design elements. Stock and pricing results are a lookup, not a reservation; verify the exact manufacturer part, package, quantity and supplier before buying.
Images and PDFs can provide context, but attachment support is separate from model vision. Compatible four-choice builds offer GPT Astra, GPT Sol, Trace Genie 2.0 Flash and Trace Genie 2.0; the Genie choices are text-only. Use the options supported by your build and see Models and Attachments.
Edit a schematic
Use Agent for a bounded design change, or Plan when you want to review a multi-step approach first. For example:
Add a decoupling capacitor for U1 using the manufacturer's recommendations. Preserve the existing connectors and explain any connection changes.
Review the actual connections, component values, package and pin numbers. An ordinary amendment and a full redraw are different requests; state whether the existing drawing should be preserved.
Native .trace_sch files and their paired .xo are project files, read and written in-process by the desktop—not disposable conversion output. See Projects and Schematics.
Find or generate a part
Finding a catalog part, generating a symbol/footprint, installing an accepted library part and placing it in a design are separate steps.
In compatible desktop builds, the Component Editor lets you generate from an exact part number or datasheet, inspect the preview, request changes and accept installation. Check:
- Symbol pin numbers, names and electrical types.
- The exact package variant and symbol-to-pad mapping.
- Pad dimensions, pitch, orientation and units against the manufacturer drawing.
- Library associations after saving and reopening.
A generated preview is not proof of a correct footprint. A 3D body is a visualization aid, not certification of tolerances or enclosure clearance. The companion's review and installation happen through its own host workflow.
Prepare and review PCB layout
Establish schematic-to-board connectivity, footprints, outline, layers and design rules first. Identify mechanical constraints and approve fixed component positions before requesting layout.
Basic routing (Quick routing in older builds) and Trace's advanced placement and routing are different workflows. Review the Basic routing card before Route board; review the charge and preservation settings before an advanced run. Choose placement-only, routing-only or both where supported; a request about one net or one part is not permission for a whole-board run.
In native classification controls, Protected keeps an approved placement and Unplaced permits placement work. Protected is not editor Lock. Routing-only does not require protecting every component.
Review preflight findings, the displayed usage/time limits and the saved result. Advanced layout processes submitted board data in the cloud. Check fixed positions, unrouted connections and DRC afterward; engine completion does not prove signal integrity, thermal suitability or physical access.
See Placement and routing and Billing and access.
Check behavior
The assistant can help run and interpret supported ERC/DRC checks. Their scope is the configured electrical/design rules.
In capable native schematic sessions, Simulation evaluates a saved design under known conditions with suitable models. Inspect the actual results and requirements: missing models, partial runs and unevaluated assertions do not become a PASS. Opening a saved-run viewer does not start the solver.
Compatible companion builds have a separate plugin Simulation window. They do not gain a native workbench tab; source export, model and host limits still apply.
Review Library Copies
In newer Trace Plugin builds, Library Remediation inventories supported library sources, runs checks and offers a separately requested AI review. Review findings and proposed fixes before writing a new output copy. A library check does not modify the live circuit or certify a part against every manufacturer requirement.
Prepare Firmware Notes
With a supported Agent request or enabled workflow, Firmware Notes record design-grounded pin maps, initialization requirements and unresolved assumptions for implementation elsewhere. They do not compile, flash or run firmware, and they do not authorize physical hardware actions.
Manufacturing
Before fabrication, inspect exported Gerber/drill, BOM and assembly files as applicable. Confirm part choices, orientation, dimensions and manufacturing requirements independently. See Exporting.
AI tool reference
The workflows above describe tool scope; the actions available in your session depend on its editor and permissions. Chat progress, tool rows and review cards help you see work in progress. A proposed action, accepted request or final sentence is not evidence that files were saved, a part installed or a cloud operation completed.
Use Working with chat for queue, Stop and interrupted tasks. Choose modes explicitly: Ask is not automatically promoted into editing. Stop does not undo earlier effects; do not resubmit an action whose delivery is unknown.
Use native history or the host's supported recovery for design changes. Editing a message or truncating a companion conversation is not CAD rollback.
Collaborate deliberately
Workspaces separates local Save, Commit, Push and Pull. Browsing a project is not opening its working copy, and cloud publication needs the relevant permission.
The revised GUI workflows remain under validation, including unresolved Add/Open/Pull and stash-restoration outcomes. Do not assume a source implementation is a shipped, accepted workflow or repeat an uncertain publication to bypass its recovery state.