Skip to content

5dive

v0.1.9 Feature

This release adds 1 notable feature for engineering teams evaluating rollout.

Published 17d AI Agents & Assistants
✓ 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

The installer now stages the telegram‑codex plugin with its runtime dependencies.

Full changelog

Added

  • install.sh now stages the telegram-codex plugin into
    /usr/local/lib/5dive/telegram-codex — a whole-subdir tarball from
    5dive-com/5dive-plugins plus bun install --production of its runtime deps
    (grammy). This is what makes codex --channels=telegram (shipped in 0.1.8)
    work on customer VMs and not just hosts with a 5dive-plugins checkout:
    codex has no plugin marketplace, so its MCP server + lifecycle hooks run from
    this one shared copy, and 5dive-agent-start already resolves
    /usr/local/lib/5dive/telegram-codex ahead of the dev checkout. server.ts
    resolves each agent's own state dir from $HOME, so a single staged copy
    serves every codex agent. Staging lives in refresh_managed_files, so the
    daily update.sh → install.sh --upgrade cron stages/refreshes it on
    existing VMs too (no separate update.sh change needed). Override the source
    with CODEX_PLUGIN_TARBALL; fail-soft (warns, doesn't abort the install) if
    the fetch or bun install fails.

See CHANGELOG.md for the full breakdown.

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.

Sign up free

About 5dive

All releases →

Related context

Beta — feedback welcome: [email protected]