Skip to content

v1.4.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Oct 03:31
v1.4.3
3dc62fe
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Decepticon v1.4.3

This patch simplifies CLI engagement creation and supports switching conversations during a running session.

Changes

  • Creating an engagement asks only for its name and opens Plan. Target, mode and authorization-reference inputs no longer block workspace creation. Existing scopes remain resumable. (#963)
  • /mode plan, /mode red and /mode blue select conversations during a run, preserving each mode's thread, pending question and paused checkpoint. Switching first waits for server pause acknowledgment; failure keeps the original mode/run. Metadata and cancellation share one 10-second deadline. Escape opens commands from a question, and /resume reopens it. (#964)
  • Mode selection is independent of execution permission. Actual Red operations require current scope approval; review the validated Plan and use /mode red approve. Blue investigation requires a connected local sensor.

Updating

decepticon update --channel latest

Existing engagement data and database credentials do not need to be recreated. Startup update choice from v1.4.2 remains available: Update now or Skip when a newer release exists.

Verification

Name-only creation was exercised through the real launcher picker in a PTY, including invalid/duplicate names, cancellation, EOF and existing-scope resume. Runtime checks used the actual Node CLI and LangGraph JavaScript SDK against an owned HTTP/SSE fixture: pause and same-thread checkpoint resume, question restoration and answer resume, unavailable sensor/unapproved scope denial, and bounded pause failure. These fixture checks do not claim a real model or checkpoint database E2E run.

All 106 CLI tests, typecheck and build passed. Independent review approved the final runtime head. PR CI passed CLI tests on Linux/macOS, CLI image builds on amd64/arm64, web image build, LangGraph arm64 smoke and security checks. Name-only creation separately passed launcher tests and vet, including race/shuffle checks.

Final main CI and all 18 release jobs passed. After publication, verified all six launcher binaries, configuration/skill manifests, three PyPI packages with matching sibling pins, and all eight image digests/platforms with matching latest tags. The downloaded Linux launcher displayed only the engagement-name field in a real PTY; it was cancelled before service startup. The released CLI image ran in a real Docker container and resumed the original thread after Plan -> Blue -> Plan. The protocol fixture remains the boundary for that checkpoint observation.

Full changelog: v1.4.2...v1.4.3

Assets 18
Loading