Decepticon 2.0.0

Decepticon 2.0.0

The terminal now has a fixed conversation/composer layout, mouse controls and a clear graphite/silver status band. Greetings and status questions no longer become unsolicited assessment runs.

Upgrade and compatibility

/resume now opens saved sessions, including while paused. Select a conversation, then send a message to continue. /resume <thread-id> restores an explicit conversation. The old /resume [message] pause-feedback meaning is replaced: send feedback directly in the composer. /answer returns to a pending structured question. This advertised command change makes this a major release under RELEASE.md.

Existing engagements, saved conversations and database formats are retained; no reset or data migration is needed. Python import aliases remain available and deprecated. Upgrade with decepticon update --channel latest, then restart the OSS CLI.

Changes

• Fullscreen interactive terminals: click model/session/menu controls, place the input caret, scroll history with wheel/PgUp/PgDn, follow latest and expand tool results. Keyboard controls remain available. Use --no-alt-screen or /tui inline for native scrollback, and --no-mouse or /mouse off for native selection. Unicode/wrapped drafts and external-editor return preserve input state. #1097
• Unify first-launch Go prompts, inherited text and conversation controls around neutral surfaces. Group session/model/connection, observed route, requested effort, approximate context and compaction state in a visible footer. #1097
• Refresh approval from current trusted, bound launch context on resume, including revocation. Expose canonical OPPLAN enums/integer priorities; stop replaying main-model failures as compaction failures. #1096
• Separate conversation completion from assessment completion. Preserve pending work and terminal receipts during greetings/status/questions; keep evidence, review, budget and resume guards for assessment work and explicit autonomous search. #1099
• Explain upstream cybersecurity/content-policy refusals without misleading authentication-priority advice or router dumps. Provider access remains provider-controlled. #1095
• Isolate configured-developer credential tests and stabilize the macOS port-recovery fixture. #1098, #1097

Verification

Source checks include full Python coverage, CLI/Go/Web/Worker suites and production builds; final-source CI/security must pass before tagging. Actual WSL launcher → engagement → compiled CLI → real auth/gpt-5.6-sol responses verify greeting-only behavior, stale approval restoration and saved-session continuation. Same-volume restart preserved conversations, files and ports. Real Docker recovery moved occupied 7474 to 7476, returned HTTP 200 and retained the selected port on restart.

The actual downloaded 2.0.0 launcher and versioned CLI/backend images passed the same real-model flow: two greetings without tools, saved-session restoration without dispatch, refreshed stale approval and continuation returning INTERACTIVE-RESUME-OK, exit zero. The source-to-candidate upgrade preserved all three prior threads, 27 messages, four workspace file hashes and host ports. Six launcher checksums, three PyPI distributions, config/skill manifests and all eight image digests/platforms, keyless signatures and CycloneDX SBOM artifacts were independently verified. Sandbox’s oversized SBOM uses OCI attestation without Rekor upload; its image signature verifies normally. Publication/channel verification is performed after the protected publish job completes.

The renderer mounts visible rows; retained history/cache can still grow. Custom drag selection, clipboard ownership and automatic URL opening are not implemented. Native Windows/macOS product acceptance is not claimed by the WSL checks. Research and interaction limits.