release aidev SIG 3/5

Kilo Code JetBrains 7.0.12: prompt queueing and skill-command approvals

The JetBrains plugin can now accept a new prompt while a session is still running, queueing it visibly so it can be removed before processing. Permission prompts show the verbatim skill command and skill name, skill-context commands can be batch-approved, and diff review gains branch changes plus full-context file diffs. Shell commands the parser cannot scan now fail closed.

PUBLISHED2026-08-01
OBSERVED2026-08-11
AGE10d
SOURCES1
  • Queue additional prompts during a running session; queued prompts appear in the conversation and can be removed before Kilo picks them up
  • Permission prompts show verbatim skill commands and the skill name
  • Execute commands from skill context with batch approval
  • Session diff review: branch changes in the session header, richer diff navigation, full-context file diffs
  • Permission prompts made deterministic across queued permissions, compacted summaries, escaped skill names, auto-approve transitions
  • Permissions enforced for shell commands the parser cannot scan; untrusted or malformed skill command batches fail closed
  • Large branch diffs: capped inline diff previews, compacted diff tree paths, horizontal scrolling for long file names
  • Long chat sessions reflow after load without resizing the tool window
  • Send/stop button stays in sync when attachments change during a busy session
  • CLI agent loops no longer freeze when a provider stalls after response headers
  • Session reverts kept atomic; snapshot diffs more resilient on Windows
  • Provider stream errors surface more detail; retry handling consistent for rate limits and stream failures
  • Missing nested config unsets handled; unset keys removed from layered config files
  • Faster CLI startup via deferred module loading and telemetry work
  • JetBrains CLI pin bumped to Kilo CLI v7.4.17; includes upstream OpenCode updates through v1.17.9

COMMUNITY

No curated reactions recorded for this event. Facts and takes are kept in separate layers — community context is added by hand, never blended into the record above.