v1.5.0

Decepticon v1.5.0

Highlights

• Modern terminal composer: multiline input and paste, history search, persistent private drafts, external editor, searchable command/mode/model/session pickers and a mode/agent/connection footer.
• Restore scoped conversations and pending questions with --resume / --continue; manage waiting instructions with /queue. Failed runs retain pending input, and unrelated sessions cannot consume it.
• Independent Blue monitoring state and compact notifications during Red conversations. Use /alerts for investigation details, /status for connectivity and decepticon doctor --json for read-only diagnostics. Export conversations privately as Markdown or JSON.
• Name-only engagement creation opens Red. Import reviewed scope with /scope import <file> --confirm, then explicitly approve using /mode red approve. Plan is optional and does not grant execution authority.
• Separate stable agent capabilities and reusable skills from versioned Markdown business workflows. Workflow snapshots remain pinned on resumed conversations; remote MCP workflows are resolved by the target server.
• Persistent light/dark dashboard preference and optional vendor-neutral OpenAI-compatible gateway support.

Fixes

• Prevent LiteLLM database migration startup timeouts by using its cached native Prisma CLI while retaining normal migrations.
• Correct /mode completion, forward Delete, mode-switch failure recovery, cross-session queue isolation and stale Blue errors after reconnection.
• Preserve engagement configuration and operator-question/file decisions through resume paths; support existing workspaces with missing scope.
• Improve finding metadata/YAML handling, all-document plan exports, completion coverage checks and generated access-control tests.
• Improve Skillogy term lookup and key-only installations; reject unpriced routes under budget caps and block requests when model inventory fails.

Upgrade

Update the launcher and matching Docker images/configuration together. The new validation and role-purpose endpoints require the updated server. Existing engagement data and database volumes are preserved; a database reset is not required.

Unscoped legacy conversations remain available in /sessions legacy and require explicit linking to their engagement. Existing workflow checkpoints retain their pinned source. To change a workflow, create a new execution conversation. Blue recent UI details are bounded; the monitor remains the durable incident store.

The CLI update remains an operator choice when a newer version is available. Local Blue observation does not claim complete host-wide telemetry or autonomous response.

Changes and verification

Key PRs: #1001, #1002, #999, #1000, #997, #995, #994, #993, #991, #988, #985, #987, #986, #984, #982, #981, #980, #979, #977, #978, #975, #970, #956.

Verified on the final source: 5,838 Python tests in CI (43 skipped), 178 CLI tests on Linux and macOS, complete Go race tests, 13 native PTY scenarios, and five actual Docker CLI flows. Real Codex OAuth inference and the Red agent dialogue succeeded. Fresh isolated WSL startup reached all seven services in 255.6 seconds; container/network recreation recovered in 110.2 seconds while preserving database data and all saved conversation messages. Fourteen local terminal screenshots were retained.

Release assets include platform launcher binaries, configuration checksums, agent-skill checksums, and an image digest manifest. See Chagelog.md for the canonical version history.