EN

Changelog

What changed

Every version, dated and in plain language — not the developer changelog, but the part that makes a difference to you.

easo 0.10.2 21 September 2026

Starting a writing session needs this device's signing key, and the first time you use it your operating system asks whether it may. easo used to wait for your answer on the connection — so a dialog that opened behind another window, which is where it tends to open, left the assistant with no answer at all and no document could be drafted. easo now asks for the key beside the conversation rather than in it.

  • While the dialog waits, everything else keeps working: questions to your QMS are answered in the same time as always
  • If you have not answered yet, easo says so in words — and explains that approving it once is enough
  • The same request works the moment you have clicked; no restart, no second attempt

easo 0.10.1 20 September 2026

When easo cannot reach your QMS on behalf of your assistant, it now tells you why instead of only that something failed — and it names the most common reason outright: a QMS kept in a folder like Documents, Desktop or a cloud drive, which an application needs its own permission from the operating system to read. Your files were never at risk and nothing was lost. Finding that out used to take an afternoon.

  • easo does not guess: where the cause cannot be placed, the message says a permission is missing without naming a folder — and where it is not a permission question at all, it offers no guess
  • An administrator who disconnects their own device from the channel now stays disconnected
  • Someone who may not disconnect is told why, instead of looking for a button that is simply absent
  • When you bring old documents in, the import now says where you choose it what that means: a file taken in unchanged stays outside search and outside the editor until you convert it

easo 0.10.0 18 September 2026 Security release

When your company requires two approvals, easo now tells the person whose turn it is that it is their turn. The document says it is waiting and for how many signatures; the bell asks by name when the author picked someone; and they sign where the draft lies — without taking anyone's work over.

  • Sending a draft back is a step of its own now: with a reason, and the reason reaches the person who wrote it
  • Your AI assistant helps instead of only reading: it answers which clauses a text addresses and what is missing for one. Your assistant does the reasoning, easo supplies the verified briefing — easo runs no AI of its own for this
  • And it writes with you, in a session you open yourself: only there does the assistant see drafts at all. What it writes is your draft under your signature, through the same review and release as everything else. What it does not know it marks as an open point instead of inventing it
  • A picture a colleague inserted now reaches the person reviewing their draft
  • A reported vulnerability in a bundled TLS library was answered the day it surfaced

easo 0.9.0 11 September 2026 Security release

Your AI tools can now answer from your QMS — and only from what your company has signed off. An administrator switches AI access on in the company settings; after that, the AI on your team's devices answers from your released, signature-verified documents, and every answer names the version, the release and the verification result. Drafts stay out. The channel is off by default.

  • Access is a company decision: an administrator switches it on, the setting is recorded as a signed change like any other rule, and the same policy decides whether members may disconnect their own device — allowed by default
  • One press connects a device: easo registers the channel with the AI tool and shows a receipt of what it did. easo sets up Claude Desktop and Claude Code itself; any other tool that speaks the open MCP standard is connected with a command easo copies out for you
  • The AI reads, it does not decide: releasing, signing and withdrawing stay with people. A document whose signature does not check out is reported as a finding instead of being served as content
  • easo itself transmits nothing — the channel opens no network connection and reads your local working copy. Where your AI tool sends what it read is that tool's business, not easo's
  • Three reported vulnerabilities in bundled third-party libraries were answered the day they appeared

easo 0.8.1 20 August 2026

A false alarm is gone: on Windows, a machine-wide setting from a widely used developer tool could change line endings on a document's way to the screen — easo then reported a failed verification, although signatures, releases and documents stayed intact throughout. The check was right to flag a difference; only the cause was harmless.

  • easo now makes sure on every computer that documents reach the screen exactly as they were signed
  • A computer that was already affected puts itself right the next time a document is opened
  • For administrators, one press writes this protection into the QMS itself — so it holds even where easo is not running

easo 0.8.0 16 August 2026

This release is about pointing at the place you mean — and about putting right what was filed wrong. A comment no longer has to describe where it belongs: it hangs on the passage it is about. And a document filed under the wrong type can be corrected without withdrawing it.

  • Select the words, write your note — the passage stays marked, while reading and while writing. The marking follows your edits and steps aside once the quoted text is gone
  • Comments moved out of the narrow strip into a column with room to write; “New version” takes you straight to the marked passage, and on release easo offers to close the ones you have just addressed
  • The policy that came in as a procedure gets the right type and the right number — content, history and identity stay the same, and every old reference still finds it
  • Synchronisation tells you what your team actually received rather than what easo attempted: a release that has not arrived says so, says how long it has been waiting, and offers the repair in one press

easo 0.7.0 12 August 2026

This release is about responsibility: every process has someone responsible for it, and each document answers by itself who is responsible today — change it once and it applies everywhere immediately, with no new version.

  • The process map shows who owns what at a glance; the attention bell flags a process with nobody responsible — including when that person has left the team
  • Ending someone's access asks, in the same step, who takes over
  • A document you took in unchanged as a file becomes editable easo text at the press of a button, as a new version of the same document
  • Every clause reference now records permanently which standard it means: were a second one to arrive, nothing already written would need reinterpreting

easo 0.6.0 9 August 2026

This release is about writing: long documents show their structure in the rail, links finally point somewhere, and tables behave like tables.

  • Choose the size before inserting a table, change rows and columns at the table itself, tick action items off
  • Diagrams are drawn in easo's own colours — on screen and in the exported PDF; one that will not draw tells you which line to look at
  • Two fixes reach the documents themselves: a column's alignment survives saving, and empty table cells no longer leave a stray line break in the released text

easo 0.5.0 8 August 2026

The purchase path is repaired: buying a plan leaves easo in the right state without a restart — and what you entered about your company now reaches the invoice.

  • Invoices can go to an address of their own instead of someone's personal one
  • Updates now show their progress

easo 0.4.1 7 August 2026

A bugfix release: invitations and synchronisation are now fully aligned with the plans.

  • Nothing changes for the free tier: the whole engine, locally, for one person

easo 0.4.0 7 August 2026

easo now runs on Windows too — a signed installer, five installer languages, and self-updating from the very first version.

  • Installs without administrator rights, Windows 10/11 (64-bit)

easo 0.3.0 4 August 2026

The Team subscription can be bought straight from inside the app.

  • The first launch guides you through the setup — with no Git vocabulary
  • Settings are tidied into four clear pages
  • First full self-update: from inside the app, signature-verified

easo 0.2.0 22 July 2026

The first public version, for macOS.

  • Signed with an Apple Developer ID and notarized by Apple
  • Keeps itself up to date — straight from us, with no app store

Which version you get

The download page always offers the current version — we deliberately do not advertise older ones: easo keeps itself up to date, and an outdated copy of software that signs releases is not something to recommend to anyone. The artefacts of every published version stay archived and reachable on our download host under releases/<version>/, in case you need to trace a particular build.

If you already have easo installed there is nothing to do: new versions are offered in the app and installed signature-verified.

Stay in the loop

easo is available for macOS and Windows. The newsletter tells you what comes next — new versions and new content, nothing else.

Notify me