Skip to content

v0.2.2 — auto-pair: kill the pairing step for new agents

Choose a tag to compare

View all tags
@lodar lodar released this 13 Jun 12:10
· 25 commits to main since this release
v0.2.2
b07291c

One-tap onboarding: new telegram agents auto-pair, no "message the bot, paste a code" step

A customer's Telegram operator id is the same across their whole fleet, so 5dive now learns it once and auto-pairs every new agent.

  • Shared operator allowlist (/var/lib/5dive/operator-allow.json): learned from any agent pair --user-id and from the CoS mint event (agent cos claim now returns the bot creator's id, per Bot API ManagedBotUpdated.user).
  • agent create (telegram, no explicit --telegram-allowed-users) seeds the new agent's allowFrom from that store, so the bot accepts the operator's DMs immediately. Reports autoPaired in its result.
  • Dashboard skips the pairing step when autoPaired is true (guarded — a bot that could not auto-pair still falls through to manual pairing, never left unreachable). CoS onboarding is now: create bot in one tap → done.
  • Per-agent access is still fully customizable via the Telegram-access modal.

Builds on 0.2.1 (CoS managed-bot onboarding + cos set-avatar). Verified: test-vm smoke green; on-box end-to-end (create with no allowlist → autoPaired + access seeded from the store). Managed boxes update nightly; self-hosted: 5dive self-update.

Assets 2
Loading