Commands  ›  Clash Manager / Solver  ›  Clash Solver Move Service Into Detected Space

Clash Solver Move Service Into Detected Space

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

Coming soon

Before you run this

Active document; one service element resolvable; has a default 3D view for raycasting.

After it runs

ElementTransformUtils.MoveElement inside the inner Transaction; tracker audit.

When to use this

Don't use this when

Bulk moves — call in a loop if needed; each call is its own audit line.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) element unique id required (Bot) OR single selection (Human).
2) Resolve element; WireError if not.
3) Instantiate PlacementMoveElementIntoDetectedSpaceCommand with one-element element ids + optional threshold/step.
4) Delegate Execute; pipe its tracker outputs.
5) Tag tracker with delegated_to + solver context (clash id optional for audit linkage).

What you'll see in the chat

on start
Moving one service into detected space…
thinking
Resolving target service element…
Delegating to PlacementMoveElementIntoDetectedSpaceCommand…
on success
Service move delegated; outcome in tracker outputs.
on failure
Move service 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_move_service_into_detected_space
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolvermoveserviceintodetectedspace · move service into space · solver step 3 move

PillarClash Manager / Solver