Skip to content

Vimma 0.1.9 · Firefox 158.0.1

Choose a tag to compare

@JRanne JRanne released this 27 Oct 19:15
9ce3e9a

Updating

  • macOS: brew upgrade --cask vimma, or download vimma-0.1.9-macos-aarch64.dmg
    below and drag Vimma over the copy in Applications.
  • Linux: :update shows the command for how you installed Vimma; the user guide's
    Updates section lists them all.

0.1.9 · Firefox 158.0.1 (2026-10-23)

Added

  • Agents (MCP): sending a form and paying are checkpoints. Under any grant they ask with y and n only, marked ▲ in the theme's warning colour, and the agent goes on under its grant after either answer. A step pays when the page shows a payment card field (also in a payment provider's frame) or the pressed button or followed link says it pays (Pay now, Place order, Vahvista tilaus, … in six languages), also a button that sends no form; its question names the button, the site and the total the page states (▲ claude-code wants to pay: "Vahvista tilaus" on shop.example · the page says "Yhteensä 42,90 €"), and a button in a payment provider's frame of another site names that site, then the shop's (on pay.provider.example (in shop.example)). A form's question lists each field it sends with its value, a password as •••, hidden fields counted. A yes shows allowed payment on shop.example or allowed sending the form to example.com. The grant's hint is y once · 10a 10 min · n deny · x mute, so that a usual question fits one line at 1,280 pixels, and the grant's notice says that sending a form or paying still asks. The e2e baselines m0-mcp-stdio-question, m0-mcp-drive-keys-question, m0-mcp-forms-fill-question and m0-mcp-forms-submit-question change with the shorter hint and the form question, and m0-mcp-checkpoints-basket-ran, m0-mcp-checkpoints-pay-question, m0-mcp-checkpoints-card-question, m0-mcp-checkpoints-hosted-question (a payment provider's pay button in a frame of another site) and m0-mcp-checkpoints-hosted-allowed (the notice at its yes) are new.
  • Releases: vimma-ctl ships in every package (the tarball, the AppImage, the .deb, the .rpm, the PKGBUILD and the macOS app with its Homebrew cask), so each update replaces it together with Vimma. A vimma-ctl older than Vimma keeps the tools it knows: vimma-ctl mcp tells the agent it is older, and Vimma shows a one-line notice once per client and version.
  • Release packages carry the licence notices of what vimma-ctl links (Rust's standard library, musl, LLVM's libunwind) in vimma-ctl-licenses/, and the release SBOM lists vimma-ctl with them.
  • mcp: paying and sending a form are checkpoints (#522) (c2dadf6), closes #508
  • release: packages carry vimma-ctl's licence notices and the sbom lists it (#528) (5e26f06)
  • release: ship vimma-ctl in every package, and an older vimma-ctl says it is older (#517) (5741ea7)

Fixed

  • mcp: a one-line grant hint, an honest yes notice and a framed pay button's site (#526) (cd5d275), closes #525

Third-party notice

The AppImage starts with the unmodified AppImage type-2 runtime 20251108 (MIT), which
statically links libfuse 3.15.0 under the LGPL-2.1-or-later. Its source:
https://github.com/AppImage/type2-runtime/tree/20251108. The licence text and how to relink or replace the runtime are in
usr/share/doc/vimma/ inside the AppImage (--appimage-extract). vimma-ctl links Rust's
standard library, and on Linux musl and LLVM's libunwind, into its binary; their notices are in
vimma-ctl-licenses/ next to it, or in Vimma.app/Contents/Resources/ on macOS. Vimma is
MPL-2.0; the CycloneDX SBOM lists the other components.