simplex chat cli

Run support workflows through the CLI without losing the privacy model.

Use the planner to turn upstream SimpleX Chat concepts into a concrete rollout, support, relay, and data-boundary decision.

Unofficial boundary AGPL-3.0 source v6.5.5 release noted
Abstract private relay planner with encrypted message queues across devices and relay nodes.

Workflow

What this page helps decide.

CLI profile

The terminal client can be useful for business support, cloud-running profiles, and automation planning.

Bot path

Bot and support workflows need careful token, profile, and operator boundaries before they touch customers.

Remote control

Desktop-to-CLI control and remote profiles add convenience, but they also create operational responsibilities.

Decision matrix

What the planner checks before a rollout.

AreaQuestionPlanner output
IdentifiersHow will users connect without phone numbers, handles, or global IDs?Invitation, address, and group workflow map.
RelaysDo preset servers satisfy the pilot, or does the team need self-hosted SMP relays?Relay posture, domain checklist, and operations tasks.
Data ownershipWho owns backups, device loss, passphrases, and profile recovery guidance?Device-owned data policy and support script.
Business supportDoes customer support need business addresses, broadcasts, or bot handoff?Support conversation model and moderation checklist.