Chimera 0.78.2

Chimera 0.78.2

[0.78.2] - 2026-10-27

Added

• SVG images are accepted, after validation. Vector models such as Recraft V4.1 Vector return SVG; Chimera rebuilds it from an allowlist (no scripts, event handlers, external links or entity declarations), saves it as .svg, and serves it with a sandboxing Content-Security-Policy. (#1115)

Changed

• Google search in your own Chrome follows "Ignore permissions". With the switch on, searches in the paired, visible Chrome run without a card, still paced (one every 20 s, 30 a day) and stopped at a CAPTCHA. When every search key is out of credit or refused, web_search tells the agent to use the browser's Google search instead. (#1116)

Fixed

• generate_image reports OpenRouter's upstream image errors instead of "no image", names the replacement for the retired gpt-image-1 and gpt-5-image ids, and asks Gemini for a square image. (#1123)

• A browser navigation that failed before any page loaded (for example, a site not yet granted to the Chrome extension) no longer marks the turn as having read untrusted content. (#1122)

• The Chrome extension works on current Chrome again: the download denial no longer fails every action with "Cannot access browser-level commands" (downloads are cancelled by a guard instead), Cancel on Chrome's debugging bar can be undone with "Resume Chimera actions" in the popup, and the popup stops offering Allow for a site already granted. (#1121)

• The deepseek-v4-flash catalogue row reads 0.14 in, the live OpenRouter price, so the cost shown for it is not understated. (#1120)

• Registering the Chrome host checks that its Python can read the OS vault (keyring) and refuses with the exact install command when it cannot; before, the extension stayed "paired, disconnected" with no reason given. (#1119)

• Google search in the paired Chrome works: the extension only attaches to web pages in its own tab group (a group tab left on a chrome:// page made every action fail with "Cannot access a chrome:// URL"), and the results page is recorded by its URL, so trusted sources apply to it. (#1118)

• The Chrome extension pairing survives desktop app updates: the browser host accepts the app's service from any version folder of its own service-bin, instead of only the exact version it was registered with. (#1117)