Kilo Code 7.4.3: experimental image generation, project memory in VS Code, on-disk config reload
Adds an opt-in image generation tool, wires project memory into the VS Code extension, and introduces a reload action that picks up config, skills, agents, commands and MCP prompts changed on disk without losing sessions. Note: the published notes are headed 7.4.2 and the changelog text is truncated mid-entry, so this list may be incomplete.
PUBLISHED2026-07-09
OBSERVED2026-08-11
AGE1mo
SOURCES1
Minor
- Experimental image generation (text-to-image and image editing) behind
experimental.image_generation, via the Kilo Gateway or a user-supplied OpenRouter key. - Images read by the agent render inline in chat, clickable for a full-size preview.
- Project memory surfaced in the VS Code extension: Context settings controls, task-header and assistant-message affordances,
/memorycommand, command-palette entries. - Autocomplete in Jupyter notebooks for supported languages.
- Reload action reboots the per-directory instance and re-reads config, skills, agents, commands and MCP prompts from disk; sessions and history survive. Exposed as
/reload, a task-header and settings button, aKilo Code: Reload Config and Skillscommand, andPOST /instance/reload(returns 409 while a session is running). - Task timeline bars are keyboard/click activatable to jump the transcript.
Patch
- Custom provider models can be marked image-capable in VS Code settings.
- Agent Manager delays automatic branch naming until a task looks durable; read-only questions no longer claim a branch name.
- Codebase indexing now respects nested
.gitignoreand.kilocodeignore. - Commit-message endpoint returns a typed 422 with a clear "no changes" message instead of a generic server error.
- Model usage panel shows the full routed model id instead of collapsing it to
:free. - Fixes for dropdown clipping in the New Worktree dialog, bidirectional text input, Shift+Arrow selection across file mentions, and truncated localized settings labels.
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.