Releases: BrokkAi/brokk
Releases · BrokkAi/brokk
brokk-acp-rust-0.3.1
Validate reasoning effort for models without presets (#3612)
brokk-acp-rust-0.3.0
rust acp server version bump
brokk-acp-rust-0.2.0
brokk-acp-rust v0.2.0
Release 0.23.6
Add Python usage graph support (#3518) - Extracts reusable usage graph adapter hooks and routes Python through UsageAnalyzerSelector with regex fallback preserved. - Adds Python export/import extraction, package barrel traversal, dotted namespace import handling, static wildcard re-export support, and guarded receiver/type inference. - Adds hierarchy-aware Python member usage matching and regression coverage for true positives, false positives, local shadowing, cycles, aliases, and fallback behavior.
Release 0.23.5.beta8
ACP: hide GUI-only config keys from /config command (#3502) The /config slash command exposed and accepted writes to Brokk Swing-only settings (theme, notifications, jvmMemorySettings, layout flags, etc.) that have no effect when the agent runs in ACP server mode. Users were getting "Updated configuration successfully" with no observable result. A new GUI_ONLY_GLOBAL_KEYS set drives both filtering of the snapshot output and rejection of writes via rejectGuiOnlyKeys(), called at the top of applyGlobalSettings. The rejection works for both dotted-path (/config global.theme dark) and JSON-batch forms — fail-fast on the whole batch. Help text and the available-command palette example now use global.exceptionReportingEnabled false, plus a note explaining that GUI-only keys reject the entire batch — clients should strip them before sending. A new promptConfigSnapshotOmitsGuiOnlyKeys test iterates GUI_ONLY_GLOBAL_KEYS and asserts none appear in the /config snapshot, catching drift if a future contributor re-adds a map.put for one of these keys. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Release 0.23.5.beta7
LutzAgent: emit context-engine status via showStatusBanner (#3481)
The two narration lines in scanContext() ("Brokk Context Engine
analyzing repository context..." / "Brokk Context Engine complete...")
were emitted as raw bold-markdown via io.llmOutput(...). In ACP/Zed
this rendered as plain agent_message_chunk text, while the sibling
emitContextAddedExplanation call already routed through
showStatusBanner and produced a compact tool_call card. The visual
asymmetry showed up in the transcript as bold prose sandwiching a
single styled card.
Route the two narrations through showStatusBanner with empty details
so all three context-engine signals share one mechanism. After the
upstream ACP override (#3480, showStatusBanner -> emitCompactStatus),
every emission now lands as a title-only THINK card in Zed.
GUI/CLI consoles fall back to the IConsoleIO default, which renders
the headline as a status banner via ExplanationRenderer.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Release 0.23.5.beta6
MOP/ACP: parse legacy <message type=...> framing on display-side repl…
Release 0.23.5.beta5
brokk-acp-rust: reject writeFile through symlinks pointing outside cw…
Release 0.23.5.beta4
ACP: explicit status APIs + earlier callCodeAgent/context/model/title…
Release 0.23.5.beta3
Java ACP server: per-session cwd, clean output, duplicate-key fix (#3…