Commands  ›  Clash Manager / Solver  ›  Clash Solver Connect Into Nearest Terminal Via Flex

Clash Solver Connect Into Nearest Terminal Via Flex

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

Coming soon

Before you run this

Active document; source + terminal resolvable; matching system types.

After it runs

One FlexDuct/FlexPipe inside one Transaction.

When to use this

Don't use this when

Cross-system terminal connects — use ConnectorOps direct with AllowCrossSystemWithWarning=true.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Validate both resolvers.
2) Instantiate ConnectorOpsConnectIntoNearestTerminalViaFlexCommand with strict gate.
3) Delegate Execute; pipe outputs.

What you'll see in the chat

on start
Flex-connecting terminal with strict system-match…
thinking
Delegating to ConnectorOpsConnectIntoNearestTerminalViaFlexCommand…
on success
Flex terminal connect delegated, strict gate enforced.
on failure
Flex terminal connect 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_connect_into_nearest_terminal_via_flex
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolverconnectintonearestterminalviaflex · strict flex terminal · solver terminal connect

PillarClash Manager / Solver