codeg 0.30.7 allalaadimine

pi gets a deep pass — reasoning, images, real diffs and rewound branches now come through correctly, and a new session no longer opens with a page of startup noise.
Local screenshots render inline in replies, imported worktrees land under their repo, and six bundled agents move up.
New
- Local images in a reply now render inline instead of a blocked placeholder, and click to open in the image viewer. (#691, @Adam-Dalloul)
- pi is now a local MCP source — servers in ~/.pi/agent/mcp.json show up in MCP settings and can be edited there. (#653 requested by @galact-byte, #673 @dawNotPoi)
Improved
- Updated bundled agents: DeepSeek 0.9.0, Kimi Code 0.42.0, OpenCode 1.18.30, CodeBuddy 2.149.0, Grok 1.0.25, Qoder 1.1.49.
- DeepSeek's model panel follows 0.9.0 — the built-in list is now deepseek-flash and deepseek-v4-pro, image detail is replaced by a pixel budget, and a list written by an older codeg says so and is repaired by saving it again.
- pi's settings panel now warns that a custom config or session directory only applies to pi itself — sessions written there won't appear in codeg's history.
Fixed
- pi's reasoning is no longer dropped — thinking blocks were read from the wrong field and vanished entirely.
- A rewound pi session now shows only the branch you're on, not the abandoned ones still sitting in the same file.
- Opening a pi session no longer starts with pi's startup banner as the assistant's first message.
- More of a pi transcript survives: images, an edit's real diff, cancelled commands marked failed, an error message on a failed turn, and context-compaction cards.
- A Codex code-mode MCP call keeps its identity when you reopen the session — real tool name, arguments, result and error state, instead of a generic script card. (#702, @asteroida123)
- An imported worktree session now lands under its repo, so it joins the repo's worktree group and gets its branch label. (#552 reported by @Luis-WowApps, #707 @Adam-Dalloul)
- An agent process is no longer left running when a connection ends at the wrong moment. (#701, @asteroida123)
Thanks to @Adam-Dalloul, @asteroida123 and @dawNotPoi for contributing to this release, and to @Luis-WowApps and @galact-byte for the reports.