Repository navigation
Gnosis v1.4.0 records Terms acceptance somewhere other than your own machine, and stops installing updates behind your back.
⚠️ Windows will probably flag this installer
This is expected, and it is a false positive. The installer is not code-signed yet.
Bitdefender flags it as Atc4.Detection — a behavioural heuristic, not a named virus signature. An unsigned installer that unpacks itself into %TEMP% and runs code from there looks, to a heuristic engine, exactly like a dropper. It will keep being flagged until the installer is signed by a verified publisher.
If your antivirus quarantines it:
- Add an exception for your Downloads folder and the Gnosis install directory before re-downloading.
- In Bitdefender: Protection → Antivirus → Open → Settings → Manage exceptions → Add exception.
- Then install again.
If it already quarantined a file mid-install, the antivirus may hold a lock on that exact path even after you add the exception — a reboot releases it.
SHA-256 of Gnosis-Setup-1.4.0.exe:
320B09485CC8AD0CC8633A19FFA4D0B357C41FB17A635CC8C98FAC1418F92E18
Updates are now notify-only
Gnosis no longer downloads or installs updates in the background. It checks on launch and every six hours, and when a newer version exists it tells you — in the app and in a Windows notification — and links here.
This is a deliberate trade. A silent background download of an unsigned installer does not produce a stale app; it produces a quarantined payload, a shortcut pointing at nothing, and no reason to connect the antivirus alarm to Gnosis. A user who ignores an update reminder is on an old build. A user whose antivirus interrupts a silent install is on a broken one. The second is much worse.
This reverts once the installer is signed.
If you are on a build older than v1.2.0, reinstall manually
Older builds shipped with autoInstallOnAppQuit = false, which did not mean "ask first" — it meant discard. Gnosis downloaded the update, showed a toast, and threw the staged build away if you closed the app without clicking Restart, then re-downloaded ~120MB next launch to delete it again.
That bug is in your installed copy, so its updater cannot rescue itself. Download the installer below once, and updates work normally from then on.
Terms of Use — Version 2
Version 1 said the project collected nothing and ran no servers. That is no longer true, and this release is where it changed.
When you press Accept — and at no other time — one record of that acceptance is sent to a server we operate. It contains exactly: a random installation id, the Terms version, a checksum of the exact text you were shown, the app version, the timestamps, and an email address only if you choose to type one (the field is optional and blank by default).
That is the entire list. There is no second call, no heartbeat, no usage reporting, no analytics. We do not know when you run Gnosis, what you ask it, or whether you are still using it. If you never accept, nothing is sent at all.
Why: a record of acceptance kept only on your computer is a record you can edit. A copy stays on your machine at ~/.dom/acceptance.json so you can always see what was recorded.
Everything else is unchanged: prompts, files, keystrokes and recordings never reach us. Gnosis still talks to OpenRouter, Groq, Brave and GitHub using your keys, under their terms.
Because §5 changed materially, you will be asked to accept again on first launch.
Also in this release
- Voice is on by default, disclosed on first run.
- Acceptance is keyed to a checksum of the exact text shown, not a version string — editing the Terms invalidates prior acceptance rather than silently recording people as having agreed to words they never saw.
- Acceptance is recorded locally first and always; if the server is unreachable the record queues and retries. Being offline never blocks acceptance and never loses it.
Full verification: 137/137 suites passing.