Managed remote on dUX

The managed remote flow is the most common way Syntax and dUX collaborate. From the developer's perspective, it's three or four clicks; behind the scenes, two systems are exchanging structured intents and placement responses.

The user-facing flow

1. Open Deployments → New Deployment.
2. Pick a category (Chat, General, Coding, Media, Vision, Custom) or open the Party Builder for multi-model.
3. Pick Managed Remote as the target.
4. Pick a tier: Latency or Throughput.
5. Set exposure: private endpoint, public endpoint with bearer, or both.
6. Submit.

Syntax submits the intent to dUX. The desktop app shows the deployment moving through statuses — accepted, provisioning, ready — and surfaces any issues as clear messages rather than dUX-internal errors.

What you see when it's ready

When dUX returns a "ready" status, Syntax wires the resulting endpoint into the Bridge. Practically, that means:

• The model appears in the harness's model list exactly like a local or self-hosted-remote model.
• Your harness routes to it transparently — no harness-side reconfiguration.
• Multi-model parties show every model in the party as part of a single deployment in the Active Deployments view; the Main Agent's tool list automatically includes its specialists.

Saved remote targets

After your first managed-remote deployment, you can save the target configuration — name, tier, exposure, replica policy. Subsequent deployments to the same logical target are one click and inherit the saved settings.

This is especially useful for teams that want a consistent set of deployments across members: save one set of targets at the org level and members can deploy to them without re-picking each setting.

Lifecycle

Once a deployment is ready, it stays running until you stop it. From the desktop app you can:

• Scale — increase or decrease replica count (within the tier's bounds).
• Stop — bring the deployment down. dUX releases the GPU resources.
• Replace — replace the deployment with a different model (atomic where possible).
• Upgrade — when the underlying base or engine images change, Syntax surfaces an "upgrade available" prompt; accepting issues a fresh deployment with the new images.

Multi-model parties on managed remote

When you deploy a party — Main Agent + Default Sub-Agent + up to six Specialists — the entire party deploys as a coherent unit on dUX. Specialists become tool calls available to the Main Agent exactly the way they do for local or self-hosted-remote parties.

Where to go next

• Inference → Managed remote — the inference-plane view of managed remote.
• Concepts → Party Builder