AltoDocs

Add a filled annulus — a ring. Diameters, not radii, because that is how a washer or a pipe is specified. innerDiameter 0 gives a solid dot. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_donut

Add an ellipse (or elliptical arc): centre, semi-axes rx (local X) and ry (local Y), optional rotation. Provide startDeg+endDeg (parametric degrees) for an elliptical ARC; omit them for a full ellipse. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_ellipse

Fill a closed region. Either pass an explicit boundary ring as points, OR a boundaryId (a closed polyline/circle/ellipse to fill). pattern "solid" = filled; "lines" = parallel hatching at spacing/angleDeg. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_hatch

Add an annotation LEADER: an arrow pointing at geometry, a path back, and text on a shelf — one object. THIS IS HOW YOU LABEL A DETAIL. Never draw a line and place a text near its end: they are then two entities that drift apart the moment either is moved, and nothing keeps the arrow attached to the words. points[0] is the ARROW TIP (put it ON the thing being annotated); the last point is where the shelf starts — usually up and out into clear space. Two points is the normal case. The arrowhead, elbow, shelf and text wrap are all derived, so you never position them. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_leader

Add a straight line from (x1,y1) to (x2,y2) in world mm. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_line

Create a NOTE BLOCK — a framed, multi-column block of flowing prose (general notes, "GENERELLE NOTER", specification paragraphs, material schedules written as text). USE THIS INSTEAD OF add_text FOR ANY BLOCK OF NOTES. One note block replaces the dozen separate text labels that a notes block used to be, and the app lays it out: you give the frame, the column count and the items, and every line position is derived. Columns therefore CANNOT overlap and never need check_text_fit or space_text — inserting a note in the middle reflows the rest by itself. Only reach for add_text when the label is a genuine one-off pointing at geometry (a part name, a leader label), not a block of prose. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_note_block

Add a FOLDED STEEL PLATE of one thickness as a SINGLE closed outline — a beam shoe (bjælkesko), L-bracket, gusset, stiffener, base plate, cleat. USE THIS, NOT several rectangles: a bent plate is one piece of steel, so on a section it is one outline with mitred corners and NO internal seams — hatchable, selectable and movable as the one part it is. Give the INNER face (the face touching the member it wraps) as `path`: 2 points = flat plate, 3 = an L, 4 = a U. The material grows to one side by `thickness`; pass `awayFrom` (e.g. the wrapped beam's centre) and it grows off the member automatically, so you never have to reason about which way round you listed the path. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_plate

Place a setting-out mark: a coordinate with a symbol and nothing else. Its size is PAPER mm, so it stays the same size on the sheet whatever the view scale is. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_point

Add a regular polygon as a closed polyline. inscribed:true puts the VERTICES on the radius; inscribed:false (circumscribed) puts the FLAT SIDES on it — that is the across-flats a hex nut or bolt head is specified by, so getting it backwards silently draws the wrong size. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_polygon

Add a polyline (or closed polygon) through a list of points in world mm. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_polyline

Add an axis-aligned rectangle by its bottom-left corner (x,y) and width/height (world mm). Created as a closed polyline. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_rectangle

Append a row to a layout's title-block revision table. rev defaults to the next letter (A, B, …). ALWAYS pass an explicit date from the user / context — never invent one (omitting it leaves the cell blank). Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_revision

Draw a revision cloud around a region that changed. Pass the PATH; the scalloped bulges are derived, so the cloud can be rescaled and still read as a cloud. Order the points counter-clockwise — the bulges go OUTWARD from the enclosed area. Pair this with add_revision, which records the change in the title block: the cloud says WHERE, the revision table says WHAT. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_revision_cloud

Add a smooth spline (Catmull-Rom curve) through a list of points in world mm. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_spline

Create a ruled TABLE — bolt schedules, quantity take-offs, bar schedules (bojeliste), revision matrices: anything where a value's meaning comes from its ROW and COLUMN. USE THIS INSTEAD OF add_text OR add_line FOR ANY TABULAR DATA. You give the column widths and the rows of cells; the app derives every rule and baseline, auto-heights each row from its wrapped content, and draws the grid. Cells therefore cannot drift out of their column and rows cannot collide. NOT for flowing prose — a general-notes panel is add_note_block, because notes have no row/column relationship. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_table

Add a single- or multi-line text label at an insertion point (world mm). height is the text height in mm (~250 at building scale; omit for that default). Supports rotation, justification, colour and bold/italic/underline/strikethrough. For a BLOCK of prose (general notes, spec paragraphs) ALWAYS set maxWidth to the column width — the text word-wraps to fit instead of overrunning its neighbours; without it only your manual \n breaks wrap. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_text

Add a viewport (a scaled window onto model space) to a layout. x,y,w,h are PAPER mm from the sheet's top-left corner (y DOWN — paper space, not model space). Aim it with `window` (a model-space rectangle to show — drives both "fit" and the centring) or `center` (model point at the viewport centre); with neither it centres on the whole geometry. The result echoes the applied scale and the centred model point. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_viewport

Add an opaque mask that hides whatever is under it, so a label can sit over hatching and still read. Draw it BEFORE the text it protects, and keep it just larger than the words. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_add_wipeout

ALIGN: move + rotate a selection so src1 lands exactly on dst1 and the src1→src2 direction matches dst1→dst2. scaleToFit also scales so src2 meets dst2 exactly. One call instead of working out a rotation and a translation separately and getting the order wrong. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_align_entities

Duplicate entities in a pattern. kind="rect": a grid of cols×rows spaced by colSpacing/rowSpacing. kind="polar": count copies around a centre (cx,cy) spread over fillDeg degrees (default 360). Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_array

BREAK: split an entity at one point, or remove the span between two. One point splits in two; two points cut the piece between them out. A broken circle becomes an arc. Order of the two points does not matter. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_break_entity

Chamfer (bevel) the corner between two LINES with an equal setback distance. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_chamfer

Answer "will this actually READ on the printed sheet, and does it FIT the view" with numbers instead of guesswork. For each viewport it reports the TRUE scale denominator (computed from the viewport's own zoom — trustworthy even when the scale label says "Custom"), the MODEL RECT it frames, every text that plots below the 1.8 mm legibility floor (with the model height that would reach it), every text merely under the 2.5 mm comfortable height, and every entity that spills outside the window with the overhang per edge. It also resolves the trade-off for you: the scale that WOULD fit the content, the paper mm the smallest text would then plot at, and the viewport size needed to show it all at the CURRENT scale. Call it whenever the user says something must "fit" a view or a sheet, before and after any layout change, and ALWAYS before shrinking text to make room — this is what tells you whether shrinking is even allowed. Scope with ids/layers; by default it judges everything the window touches. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Read-only.

cad_check_paper_fit

Report which TEXT entities OVERLAP each other, measured on the boxes the renderer actually inks. Use this instead of working overlaps out from coordinates yourself — read_drawing already gives you each label's occupied rectangle, and this compares every pair of them for you. Returns each colliding pair with the overlap in mm and how far to move to clear it. Scope it with ids or layers, or call it bare to sweep the whole drawing. minGap (mm) also flags labels that are merely too close to read apart — 20–30 mm is a normal drafting gap at 60 mm text. Call it BEFORE and AFTER any annotation edit. Read the overlap SHAPE: a tall thin overlap between stacked labels is a spacing problem (space_text); a wide overlap between two prose blocks usually means their columns are too wide for the grid they sit on — narrow each one with update_style { maxWidth } instead of shuffling them around. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Read-only.

cad_check_text_fit

Delete ALL entities in the drawing — DESTRUCTIVE and NOT undoable by you. Only for when the user has EXPLICITLY said to wipe / clear / start the drawing over in their own words. Never infer it: "do it again", "just do it", "make it better" or "I forgot to save" are NOT requests to erase the drawing — redraw around what exists, or ask. Requires confirm:true as your attestation that the user explicitly asked. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_clear_drawing

Create a new layer (or update its default style if it already exists). Newly drawn entities inherit the layer's colour/lineweight/linetype unless overridden. Use distinct colours per layer. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_create_layer

Create a new paper-space layout (an issued drawing sheet), with a default title block ("tegningshoved", unless titleBlock=false). MULTI-VIEW (preferred for a real sheet): pass `views` — one entry per view. They are auto-tiled into a tidy grid across the printable area, each labelled and independently scaled/aimed, so you get a plan + sections sheet in ONE call. This is the right way to build a multi-view sheet: do NOT create the layout and then bolt viewports on, because the default single view already fills the sheet and leaves no room. Omit `views` for a simple one-view sheet: you get ONE viewport filling the printable area above the block, auto-fitted to the model at the closest STANDARD scale. Then set_title_block to fill in the fields, and read_layouts to verify. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_create_layout

Delete entities by id. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_delete_entities

Delete a layer. Its model, saved-block and paper-space entities are reassigned (to reassignTo, else "0") rather than deleted. Layer "0" itself cannot be deleted. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_delete_layer

Delete a layout (sheet) with its viewports and title block. Model-space geometry is untouched. Use only when the user explicitly asks to remove a sheet. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_delete_layout

Delete a viewport from a layout. The sheet and model-space geometry are untouched. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_delete_viewport

Place setting-out marks along an entity: count = that many EQUAL divisions (so count-1 marks, since the ends already exist), or spacing = a mark every N mm. Measured along the true path length, so it works on a polyline or an arc, not just a straight line. Use it for pile rows, bolt runs and stud centres. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_divide_entity

Duplicate entities, offset by (dx,dy) in world mm. The copies get fresh ids. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_duplicate

Edit the DEFINING GEOMETRY of ONE existing entity IN PLACE — its id, layer and style are preserved (use update_style for colour/width/text content, move/rotate/scale_entities for whole-entity transforms). Pass the fields for the entity's type: lines/dimensions take x1,y1,x2,y2 (any subset — e.g. move just one endpoint); circles take cx,cy,radius; arcs take cx,cy,radius,startDeg,endDeg; text takes x,y (the insertion point); polylines/splines take points (REPLACE the whole vertex list) or vertices [{index,x,y}] (patch specific vertices by 0-based index — a rectangle is a closed 4-vertex polyline, so stretch/resize it by patching its corners). The result echoes the new geometry. ALWAYS prefer this over delete + redraw, which churns the id and loses the entity's style. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_edit_geometry

EXPLODE a block insert: replace it with copies of its member entities in WORLD coordinates (transformed by the insert's position/scale/rotation, with fresh ids) so you can edit the pieces individually. The block DEFINITION and any other inserts of it are untouched. Nested inserts inside the block stay inserts (explode them separately). Returns the new entity ids. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_explode_block

EXPLODE: break composites into primitives — a block into its geometry, a polyline into lines, a table/note block/leader into lines and texts, a revision cloud into arcs. This is LOSSY and one-way: the pieces no longer reflow, restyle or re-measure as one object. Prefer editing the object itself (update_note_block, update_table, update_leader); explode only when you genuinely need loose geometry. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_explode_entities

Extend a LINE: stretch the end nearest (nearX,nearY) forward until it meets the nearest boundary entity. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_extend

Fillet (round) the corner between two LINES with a radius. radius 0 = a sharp corner (extend/trim both to the intersection). Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_fillet

GROUP: bind the given entities into one lightweight group (AutoCAD GROUP, NOT a block). From then on, selecting, moving, copying, rotating, scaling, mirroring or deleting ANY member acts on the whole group in the editor — and read_drawing tags every member with its group id. The entities stay independent (same ids, layers, styles; no definition is created), and the group can be released later with ungroup_entities. Entities already in a group are skipped — pass the ids of the UNGROUPED entities you want to bind together. Use this for "keep these N things together while I edit", and make_block for a reusable component you will insert repeatedly. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_group_entities

Place an instance of a named block (from read_drawing's block list) at (x,y), with optional scale and rotation in degrees. Pass layer:"…" like on add_* calls — otherwise the insert lands on the ACTIVE layer, which is rarely where a symbol belongs. Operates on a saved standalone CAD file using the same command and mutation guard as the editor chat panel. Coordinates follow that command’s units. Supply expectedVersion from a fresh CAD read and reuse identical requestId on retry.

cad_insert_block