Commands  ›  Clash Manager / Solver  ›  Clash Solver Find Corridor From Point

Clash Solver Find Corridor From Point

Clash Manager / Solver writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; default 3D view; either (x,y,z) or a single-element selection.

After it runs

No model mutation; audit entry recorded.

When to use this

Don't use this when

Actual movement — MoveHorizontallyIntoSpace command does that.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Resolve point: (x, y, z) if Bot; else BB centre of single selected element.
2) WireError if no valid point.
3) Delegate to SpaceAnalysisFindCorridorWidthFromPoint.GetAll(doc, x, y, z, max_distance_ft).
4) Save probe + result into tracker outputs.
5) Human path pops a TaskDialog; Bot emits JSON only.
6) WireError on no-3d-view / no-walls-both-axes; WireFault on exception.

What you'll see in the chat

on start
Probing corridor width at point…
thinking
Resolving point source…
Delegating to SpaceAnalysisFindCorridorWidthFromPoint…
on success
Corridor {corridor_width_mm} mm; long axis {corridor_long_axis}.
on failure
Corridor probe failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_solver_find_corridor_from_point
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolverfindcorridorfrompoint · find corridor width · clash solver lateral move probe

PillarClash Manager / Solver