5dive

v0.2.2 Feature

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

Published 4h AI Agents & Assistants

View tool

✓ 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

Affected surfaces

auth breaking_upgrade

Summary

AI summary

One‑tap Telegram agent onboarding automatically pairs agents using a shared operator allowlist.

Changes in this release

Type	Severity	Summary	CVE
Feature
Feature	Medium	Adds one-tap Telegram agent onboarding with auto-pairing. Adds one-tap Telegram agent onboarding with auto-pairing. Source: llm_adapter@2026-06-13 Confidence: high	—
Feature	Low	Implements shared operator allowlist stored in /var/lib/5dive/operator-allow.json. Implements shared operator allowlist stored in /var/lib/5dive/operator-allow.json. Source: granite4.1:30b@2026-06-13-audit Confidence: low	—
Feature	Low	Seeds new agent's Telegram access from the shared allowlist when creating without explicit --telegram-allowed-users. Seeds new agent's Telegram access from the shared allowlist when creating without explicit --telegram-allowed-users. Source: granite4.1:30b@2026-06-13-audit Confidence: low	—
Feature	Low	Dashboard skips manual pairing step if autoPaired is true, falling back to manual pairing otherwise. Dashboard skips manual pairing step if autoPaired is true, falling back to manual pairing otherwise. Source: granite4.1:30b@2026-06-13-audit Confidence: low	—
Feature	Low	`agent cos claim` now returns the bot creator's user ID from Bot API ManagedBotUpdated.user. `agent cos claim` now returns the bot creator's user ID from Bot API ManagedBotUpdated.user. Source: granite4.1:30b@2026-06-13-audit Confidence: low	—

Full changelog

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.

View diff on GitHub

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

Share on X Share on Bluesky

Track 5dive

Get notified when new releases ship.

About 5dive

All releases →