Documentation / Chat and AI

How Trace Works

Use visual editing and AI assistance together, with review at each design handoff.

Trace combines visual schematic and PCB editing with an AI assistant. You can ask about an existing circuit, plan a change or request supported design actions. The assistant helps with the work; you remain responsible for the requirements and the result.

Start with the right product

Trace desktop includes the design editors. In compatible workbench builds, the project tree, document tabs and assistant share one window. See Using the workbench.

Trace Plugin for Altium and KiCad connects the assistant to an existing host installation. Follow its host-specific guide; tools and save/reload behavior are not identical to native Trace.

Choose how the assistant should help

Select a mode before sending:

  • Ask explains and reviews without changing design files.
  • Agent performs supported edits and other actions in the open design.
  • Plan researches, asks questions and proposes a plan for review before execution.

Trace uses your chosen mode. Asking for an edit in Ask mode does not automatically authorize Agent edits.

Choose a supported model and describe the intended scope, exact parts, supply conditions and constraints. Compatible four-choice builds offer GPT Astra, GPT Sol, Trace Genie 2.0 Flash and Trace Genie 2.0; availability is build-dependent, not a universal release promise. The Genie choices are text-only. See Models for attachment and selection limits.

Work through the design

  1. Define the task. Open the intended project and sheet or board. Save work you want to keep and identify what may change.
  2. Review the proposal. Resolve questions and inspect part choices or a plan. Do not assume a suggested alternative has the same package, pinout or electrical behavior.
  3. Inspect the changes. Check the drawing and connectivity, symbol-to-footprint mapping and any generated files.
  4. Check the next handoff. Review schematic ERC before PCB work; establish the board outline, layers, rules and fixed placements before layout.
  5. Review the finished output. Examine DRC, remaining unrouted connections, mechanical constraints and exported manufacturing files.

The assistant can help interpret findings, but passing ERC or DRC only covers the configured checks. It does not certify circuit behavior, enclosure fit, thermal performance or manufacturing readiness.

Keep the project together

Native desktop projects use .kicad_pro for configuration, .trace_sch and .trace_pcb for designs, and paired .trace_sch.xo / .trace_pcb.xo drawing data. The desktop reads and writes these in-process.

These are native project files, not disposable AI intermediates. Keep the designs, drawings and required libraries together. Use supported import/export to exchange KiCad designs; changing a filename extension is not conversion. See Projects.

Know what is local and what is shared

Opening and editing a local project is not Workspaces publication. Using hosted AI does transmit messages and relevant design context, including supplied attachments and tool results. Trace's basic routing and advanced layout process submitted board data through hosted services.

Standard builds also collect product improvement data, such as design edits and AI conversations, to make Trace better unless you turn on privacy mode. Enterprise builds never collect it. See Privacy mode.

Workspaces is the explicit project-sharing workflow. Save writes editor files; a local Commit records work; Push publishes it and Pull updates the checked-out branch. The revised Workspaces GUI flows remain under validation, including unresolved Add/Open/Pull and stash-restoration outcomes. See Workspaces before relying on those flows.

If a task does not finish

Read the visible result before retrying. Stop does not roll back earlier edits, and a lost response does not prove nothing happened. Use the offered recovery control for the original task and inspect saved work before starting another action.

Working with chat explains queue, Stop, Retry and Resume. Version history covers native recovery; companion message controls are not a substitute for CAD undo.

Explore a workflow

  • Component Editor: generate, review and install a part.
  • Placement and routing: prepare and review Basic routing or Trace's advanced layout.
  • Simulation: evaluate a supported saved circuit under known conditions; a completed run is not automatically a PASS.
  • Firmware Notes: prepare a reviewed implementation handoff without compiling or flashing firmware.
  • Plugin Library Remediation: audit supported library sources and review new output copies.
  • Billing and access: check current account access and displayed usage before paid work.