Skip to content

5dive

v0.1.6 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

✓ 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

breaking_upgrade

Summary

AI summary

preseed_claude_agent no longer wires the standalone StopFailure hook into new fork agents' settings.json to avoid double‑firing DMs and resume scripts.

Full changelog

Changed

  • preseed_claude_agent no longer wires the standalone StopFailure hook (/usr/local/lib/5dive/stop-failure-telegram.sh) into new fork (telegram@5dive-plugins) agents' settings.json. Plugin v0.4.4 (5dive-com/5dive-plugins@cc27c84) bundles the same hook via hooks.json, so preseeding the standalone copy would double-fire on every rate-limit (two DMs, two resume-after-reset.sh forks both pressing "1" on claude's Stop-and-wait menu). The standalone file stays installed by scripts/install/agent-cli.sh + scripts/update.sh for backward compatibility — agents on upstream telegram@claude-plugins-official still reference it.

Notes

  • Companion change in 5dive-api/scripts/update.sh strips the standalone StopFailure entry from existing fork agents' settings.json on the next 03:00 UTC customer-VM update cron.

See CHANGELOG.md for the full breakdown.

Breaking Changes

  • `preseed_claude_agent` no longer injects the standalone StopFailure hook (`/usr/local/lib/5dive/stop-failure-telegram.sh`) into new fork (`telegram@5dive-plugins`) agents' `settings.json`; the plugin now bundles it via `hooks.json`.

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]