Summary
Let the operator choose whether SimpleX Gateway's own SimpleX profile is marked as a bot (peerType: "bot") or runs as a plain SimpleX user, instead of always creating it as a bot.
Background
Today the profile is always created as a bot, because the only headless profile-creation flags are --create-bot-display-name / --create-bot-allow-files (in the lundog/simplex-chat image entrypoint), which set peerType: "bot". The bot marker is cosmetic — it makes peers' SimpleX apps highlight commands and show command menus — and is a fine default, but it isn't appropriate for every use (pure transport for another service, send-only notifications, a plain scripted node).
Why it's deferred
There is no CLI flag to create a non-bot profile headlessly, so "plain" mode can't just omit a flag. Options:
- Create as a bot (as today), then clear
peerType over the WebSocket API on first start (/_profile with the bot marker removed) when plain mode is selected — needs an idempotent first-start step.
- Or contribute a non-bot create option upstream (
lundog/simplex-chat entrypoint and/or simplex-chat itself).
Proposed UX
A toggle (config or action) "Act as a bot" (default on). When off, the gateway's profile is a plain SimpleX user. Document that it's cosmetic (command menus in peers' apps) and applies at/after profile creation. Display name and file sharing already live in the Configure Bot Profile action.
Context
Split out of the simplex-chat → SimpleX Gateway rename.
Summary
Let the operator choose whether SimpleX Gateway's own SimpleX profile is marked as a bot (
peerType: "bot") or runs as a plain SimpleX user, instead of always creating it as a bot.Background
Today the profile is always created as a bot, because the only headless profile-creation flags are
--create-bot-display-name/--create-bot-allow-files(in thelundog/simplex-chatimage entrypoint), which setpeerType: "bot". The bot marker is cosmetic — it makes peers' SimpleX apps highlight commands and show command menus — and is a fine default, but it isn't appropriate for every use (pure transport for another service, send-only notifications, a plain scripted node).Why it's deferred
There is no CLI flag to create a non-bot profile headlessly, so "plain" mode can't just omit a flag. Options:
peerTypeover the WebSocket API on first start (/_profilewith the bot marker removed) when plain mode is selected — needs an idempotent first-start step.lundog/simplex-chatentrypoint and/or simplex-chat itself).Proposed UX
A toggle (config or action) "Act as a bot" (default on). When off, the gateway's profile is a plain SimpleX user. Document that it's cosmetic (command menus in peers' apps) and applies at/after profile creation. Display name and file sharing already live in the Configure Bot Profile action.
Context
Split out of the
simplex-chat→ SimpleX Gateway rename.