Skip to content

5dive

v0.2.0 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agents ai automation shell claude-code cli
+4 more
codex gemini self-hosted systemd

Summary

AI summary

Updates Also since v0.1.84, DIVE-320, and CoS across a mixed release.

Changes in this release

Feature Medium

`5dive agent create --telegram-cos=<child-username>` claims CoS‑minted child token, falling back to manual token paste.

`5dive agent create --telegram-cos=<child-username>` claims CoS‑minted child token, falling back to manual token paste.

Source: llm_adapter@2026-06-13

Confidence: high

Feature Medium

CLI commands added to manage Chief of Staff bot and child tokens.

CLI commands added to manage Chief of Staff bot and child tokens.

Source: llm_adapter@2026-06-13

Confidence: low

Feature Medium

Dashboard wizard offers one‑tap automatic Telegram bot creation via CoS.

Dashboard wizard offers one‑tap automatic Telegram bot creation via CoS.

Source: llm_adapter@2026-06-13

Confidence: low

Feature Low

Per‑agent `~/.local/bin/claude` shim added at agent creation (DIVE-283).

Per‑agent `~/.local/bin/claude` shim added at agent creation (DIVE-283).

Source: llm_adapter@2026-06-13

Confidence: high

Feature Low

`agent auth status --auth-profile` scopes credential check to specific profile (DIVE-296).

`agent auth status --auth-profile` scopes credential check to specific profile (DIVE-296).

Source: llm_adapter@2026-06-13

Confidence: high

Feature Low

`openclaw auth` tracks 2026.6.6 flag rename (DIVE-297).

`openclaw auth` tracks 2026.6.6 flag rename (DIVE-297).

Source: llm_adapter@2026-06-13

Confidence: high

Feature Low

Zero‑token Telegram agent onboarding via Chief‑of‑Staff managed bots (DIVE-320).

Zero‑token Telegram agent onboarding via Chief‑of‑Staff managed bots (DIVE-320).

Source: granite4.1:30b@2026-06-13-audit

Confidence: low

Feature Low

CLI commands `5dive agent cos set|verify|mint-link|claim|rotate` manage CoS bot and child tokens.

CLI commands `5dive agent cos set|verify|mint-link|claim|rotate` manage CoS bot and child tokens.

Source: granite4.1:30b@2026-06-13-audit

Confidence: low

Feature Low

Dashboard wizard adds one‑tap "Create a bot automatically" path using CoS.

Dashboard wizard adds one‑tap "Create a bot automatically" path using CoS.

Source: granite4.1:30b@2026-06-13-audit

Confidence: low

Refactor Low

README quickstart documentation polished.

README quickstart documentation polished.

Source: llm_adapter@2026-06-13

Confidence: high

Full changelog

🚩 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`.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track 5dive

Get notified when new releases ship.

Sign up free

About 5dive

All releases →

Related context

Beta — feedback welcome: [email protected]