Skip to content

v0.2.0 — Chief-of-Staff managed-bot onboarding (zero-token agents)

Choose a tag to compare

View all tags
@lodar lodar released this 13 Jun 10:36
· 27 commits to main since this release
v0.2.0
066bae8

🚩 Flagship: zero-token agent onboarding via Chief-of-Staff managed bots (DIVE-320)

The headline of 0.2.0: spinning up a Telegram agent no longer requires pasting a BotFather token. A customer-owned Chief of Staff (CoS) bot (Bot Management Mode on) creates and manages a dedicated child bot per agent on the customer's behalf, via Telegram Bot API 9.6 "Managed Bots".

CLI

  • 5dive agent cos set|verify|mint-link|claim|rotate — manage the CoS bot and mint/claim/rotate per-agent child bot tokens.
  • 5dive agent create --telegram-cos=<child-username> — claim the CoS-minted child token at create time instead of --telegram-token (the paste path stays as a fallback). Auto-configures the child bot's name + description on claim.
  • Per-customer CoS only (no central manager = no fleet single-point-of-failure); a leak is contained to one customer's fleet.

Dashboard

  • New-agent wizard now offers a one-tap "Create a bot automatically" path: it detects an available CoS, mints the deep link, and provisions the agent once you create the bot in Telegram. Pasting a token still works.

This kills the top onboarding-friction step and the "my agent won't reply" tickets that came with mis-pasted tokens. Unblocks per-agent bot avatars (shipping next).

Also since v0.1.84

  • Runtime GitHub-org resolution for the 5dive-com to 5dive-ai rename, plus migration of existing agents' marketplace refs (0.1.87, 0.1.88).
  • agent auth status --auth-profile scopes the credential check (DIVE-296).
  • openclaw auth tracks the 2026.6.6 flag rename (DIVE-297).
  • Per-agent ~/.local/bin/claude shim at agent create (DIVE-283).
  • README quickstart polish.

Managed boxes pick this up on the nightly refresh; self-hosted: `5dive self-update`.

Assets 2
Loading