Kilo Code 7.4.13 (pre-release): Agent Manager session control, per-model reasoning effort, Shift+Tab variant cycling
Pre-release adding Agent Manager controls — agents can stop and remove a targeted session, and the Compare Models picker can run each compared worktree at a different reasoning effort. Shift+Tab now cycles reasoning-effort variants in prompt inputs, which overrides the previous focus-navigation behaviour unless disabled via a setting.
PUBLISHED2026-07-20
OBSERVED2026-08-11
AGE22d
SOURCES1
Features
- Agents can stop and remove a targeted Agent Manager session
- Per-model reasoning effort in the Compare Models picker, so compared worktrees run the same prompt at different effort levels; effort shown next to the model name in the collapsed selector
- Custom file-extension allowlist for codebase indexing, to limit scans and support extra text formats
- JetBrains Context settings for compaction and file-watcher ignore patterns
- Shift+Tab cycles reasoning-effort variants in sidebar chat, Agent Manager and the New Worktree dialog; disable with
kilo-code.new.chat.shiftTabCyclesVariant(Settings > Display) to restore Shift+Tab focus navigation
Fixes
- Background process tool cards respect the Terminal Command Blocks display setting
- Here-document content shown as plain text in terminal approval prompts
- Bidirectional text support so RTL and mixed-language chat renders correctly
- Clarified when reverting a conversation does not restore workspace changes; disabled snapshots link to the Checkpoints setting
- New-worktree dialog reachable from primary actions and keyboard shortcuts, with an explicit quick-create action
- Diff content no longer paints over sticky headers of expanded Edit/Write/Apply Patch cards
- Sessions stay usable after deprecated local review commands finish without a status transition
- Image-output models included in the Kilo Gateway chat model list
- Fixed double scrollbars and widened the new-worktree prompt field
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.