qwen-code issue proposes opt-in java_durable admission switch as slice D7-3
wenshao · ghdev · 2026-10-14
This is QwenLM/qwen-code issue #14167, proposing the third and final slice split from #14122: an opt-in javadurable admission profile with a deployment-level switch.
Current state: javadurable is an outcome, not a request — the admission stage is decided by harnessConfirmed ? "HARNESSCONFIRMED" : "JAVADURABLE" in ManagedAgentStore, meaning JAVADURABLE is recorded only when the Harness did not confirm.
Proposal: D7-3 adds an off-by-default switch that lets an entry request javadurable admission and receive the operation, admission stage, and delivery state back. Per the D7 text in #12867, a 202 on that path means "saved, and responsible for delivery".
Hard gate: this slice must not start until D7-1 and D7-2 land, since #12380 requires durable command delivery and original-command reconciliation before Stage D may expose javadurable. The acceptance criterion: with the switch off, behavior stays byte-identical to today, verified as an inspectable property of the configuration class rather than an inference.
More from coding & agent
- Isolating Antigravity chats per subfolder with AGY Rules and PreInvocation Hooks — bibryam · 2026-10-16
- Gemini shown off modding Minecraft to turn players into any Spider-Man — zacharynado · 2026-10-16
- Workflow: annotate UI screenshots in tldraw, hand to Claude, get better UI — max__drake · 2026-10-16
- Beyond chat wrappers: designing stateful, multimodal AI apps as interaction conductors — dr_cintas · 2026-10-16
- IBM engineer maps 5 levels of AI coding, from manual to a 3-day agent software factory — TejasKumar_ · 2026-10-16
- 10 open-source repos that let your AI agent reverse-engineer apps and games — victor_explore · 2026-10-16