Documentation
Command reference
Every command in Schema — all 74 of them, across the schematic and PCB editors. The AI agent drives the editor through this exact vocabulary, so anything listed here is something you can issue yourself and something the agent can do for you.
Schematic editor
Placing objects13
place_symbolPlace a new symbol.place_junctionPlace an explicit connection dot.place_no_connectMark a pin as intentionally unconnected.place_bus_entryPlace the diagonal stub joining a bus to a wire.place_netclass_labelAttach a net class to whatever the label touches.place_net_labelPlace a net label at an absolute position.place_powerPlace a power/ground symbol driving a named net.place_net_label_at_pinPlace a net label exactly on a symbol pin.place_textPlace a free-text annotation on the sheet.place_text_boxPlace a bordered, word-wrapped text box.place_imageEmbed a raster image in the sheet.place_rule_areaPlace a named polygon carrying rules for whatever falls inside it.place_tablePlace a table of text cells.
Wiring and nets6
draw_wireDraw a wire between two pins.connectPut a pin on a net, landing at the nearest point of it.delete_wire_betweenDelete the wire path between two pins.disconnectTake one pin off its net, leaving the rest of the net alone.delete_wireDelete a wire by its endpoint coordinates (mm).draw_busDraw a bus between two points.
Editing the sheet11
delete_symbolDelete a symbol by reference.moveMove a symbol to an absolute position in mm.rotateRotate a symbol.mirrorMirror a symbol about an axis.cleanupRemove junction dots that no longer connect anything.set_symbol_flagsSet whether a symbol appears in the BOM and on the board.set_unitSelect which unit of a multi-unit part this symbol draws.set_body_styleSwitch between the standard body (1) and the DeMorgan/IEC alternate body (2).set_dnpMark a symbol Do Not Populate.set_sim_excludeExclude a symbol from simulation.set_propertySet an existing field on a symbol.
Inspecting and checking6
validateReport document invariants that no longer hold.why_connectedSay whether two pins are on one net, and by what route.netsList every net, its members, and whether its name is unique.net_atName the net at a pin and list every other pin on it.describeReturn the schematic as JSON — the agent's view of the sheet.statusReport editor state as one line of text.
PCB editor
Inspecting the board8
describe_pcbReturn the board as JSON — footprints, pads, traces, vias, unrouted connections.list_unroutedList the ratsnest — the connections that still need routing.describe_board_viewReport what a board image would contain, without rendering it.render_boardRender a synthesised image of the board for visual inspection.selectSelect board items by reference, net or type.query_atList the items near a point, as JSON.get_selectionList the currently selected items, as JSON.suggest_snapFind the nearest snap point to a position.
Footprints and placement4
Routing copper6
route_traceRoute a trace between two pads.delete_traceDelete the traces connecting two pads.place_viaPlace a via at a board position.place_arc_trackPlace a curved copper track through three points.insert_viaDrop a via at the active route's end and flip to the other layer.cleanup_tracesRemove zero-length, duplicate and contained traces and merge collinear ones.
Interactive routing session10
begin_routeStart an interactive route at a pad.add_waypointAppend a vertex to the active route.commit_routeFinish the active route at a destination pad.cancel_routeAbandon the route in progress.get_route_stateReturn the interactive router's state as JSON.set_angle_modeConstrain the bend angles new segments may use.set_routing_modeChoose the collision strategy the router uses.set_route_widthSet the copper width used for new segments.flip_postureToggle HV-first / 45-first bend posture.set_auto_postureLet the engine pick the bend posture from the cursor trail.
How to read these
Each command page shows the usage line, every argument and what the command does when it cannot do what you asked. Angle brackets mark a required argument, square brackets an optional one — so place_symbol <Library:Part> <Ref> [Unit] <X> <Y> takes four arguments, or five if you name a unit.
The failure behaviour is documented as carefully as the success behaviour, because that is what an agent needs in order to recover. A command that cannot do what it was asked says so and changes nothing, rather than doing something approximate.
Drive all of this from one sentence
Describe the circuit you want. The agent issues these commands, checks the result, and shows you what it did.