Skip to content

Releases

Antimatter v23

Choose a tag to compare

@bytetroll bytetroll released this 13 Nov 21:36

Antimatter v23

Desktop v23 uses compatibility package 23.0.0. It expands Antimatter's
chat workspace with native development tools and configurable communications.

  • Chat and memory: private WYSIWYG Markdown notes, Carbon copy/export,
    compact view/status controls, opt-in idle compaction, and a Pensieve library
    with custom entries and read-only shipped references. Notes and memory edits
    retain drafts and detect conflicting changes.
  • Workspace: nested project groups, removable default groups, chat ordering,
    collapsible private imports, and consolidated settings. Themes cover the app,
    editor, and terminal; included palettes are Antimatter, Gruvbox, Solarized,
    GitHub, Monokai, and Emacs. Hotkeys, send modifiers, window chrome,
    always-on-top, and tool visibility are configurable.
  • Rust and C++ IDE: project templates, Cargo/CMake and single-file actions,
    diagnostics, build/test/run, rust-analyzer/clangd integration, and LLDB-DAP
    debugging. The visual board creates and connects source modules while
    preserving hand edits. This is an MVP for these languages. Install the
    corresponding compiler, language server, and debugger on the development host;
    see native tool setup.
  • Dashboards: Cluster reports peer vitals and controls engines within device
    grants. Security scans a confirmed workspace, tracks finding reviews, and
    exports reports. Feature Management includes a local native C API, Matrix
    bindings, and a separate Linux SDK archive.
  • Comms and Email: Discord bot channels, Slack channels, Teams chats,
    Outlook, Google Mail, and Yahoo Mail. Configure your provider app registrations
    or supported bot/app-password credentials. Credentials use the system keyring;
    agent access is granted per project and external sends require approval.
    Read and send paths have protocol-fixture coverage; live account sign-in still
    requires your registrations and provider consent. See
    connection setup and limits.
  • Optional tools: a floating or docked saved-reply pad and playable Doom with
    Freedoom data. Doom saves persist across restarts. The package includes the
    pinned engine, game data, corresponding source, and license notices.
  • Inference and packaging: bounded continuation handles reasoning-only model
    replies. The reviewed CPU and experimental HAG backends and the pinned Vulkan
    compatibility runtime remain included. Dependency review resolves the packaging
    glob advisory without changing the native backend pins.

Linux remains the qualified shipping platform. Android package 23.0.0 uses
upgrade counter 10017 and is retained as an unsigned, non-installable
signing handoff, separate from the desktop download. Provider registrations,
system graphics drivers, and native development toolchains are not bundled.


Antimatter v22 — previous source revision

This source revision adds Execute Software core-team credits and an enterprise
licensing and support contact in the README. It uses compatibility package
22.0.0 and Android upgrade counter 10016. The changes do not announce a
new binary build; published artifacts remain available on
GitHub Releases.


Antimatter v21 — previous release

Desktop v21 uses compatibility package 21.0.0. This is the first desktop
binary release assembled from the clean public source history. Android retains its
public v1 label, with package 21.0.0 and upgrade counter 10015, but is
not published as an installable APK in this release.

  • Standalone public project: MIT licensing, contributor and security guidance,
    support links, and source/history audit tooling. Setup and release documentation
    use explicit configuration without assuming a maintainer's machine, private
    network, or companion checkout.
  • Choose a trusted update folder: discovered feeds can show available updates,
    but installation requires selecting and saving a trusted folder in Settings →
    Updates. Clearing or changing that selection cancels pending work for the old
    feed. Automatic updates remain available for the folder you have selected.
  • Fresh backend packages: CPU and experimental HAG binaries are imported from
    the reviewed public Beholdd build with exact commit, archive and file hashes.
    The pinned Vulkan compatibility runtime remains included. Graphics drivers are
    supplied by the host system; HAG remains experimental with its documented model
    and hardware limits.
  • Dependency and license inventory: Electron 44.10.2, Vite 6.4.5 and Model
    Context Protocol SDK 1.32.2, with updated transitive dependencies. Each release
    includes a CycloneDX inventory reconciled against its packaged JavaScript and
    Electron files, plus dependency, Rust runtime and embedded-template notices.
    Debug source maps are excluded from desktop packages so upstream build-machine
    paths do not enter the distributed application; the final path-leak check remains enforced.
    The unchanged Vulkan binaries retain their reviewed public upstream diagnostic
    paths, verified against the pinned distribution and distinguished from our build paths.
  • Reproducible release checks: isolated assembly checks the desktop and Android
    sources, native PTY, backend health/model discovery, ABI requirements, installer,
    repair and uninstall behavior. The updater smoke uses the current package in a
    temporary profile; it does not establish compatibility with every historical
    binary or replace device/model qualification.

The Android build is retained separately as a tested, unsigned and non-installable
handoff. Production signing and phone installation verification remain necessary
before distributing an Android APK. Desktop assets do not contain that unsigned APK.

Supported build hosts use Node.js 22.20+, 24.12+, or 25+. Public release identity,
installer pins, package metadata and Android counters remain synchronized. Existing
release history is retained below.


Antimatter v14 — previous release

Desktop v14 adds the Vault: credentials you keep on this computer that a conversation may
use without ever being told what they are. The compatibility build is 14.0.0; Android
remains v1, with upgrade counter 10011.

  • The Vault, off until you turn it on: Settings → Vault. Store the credentials you would
    otherwise type by hand — your sudo password, a service login — each under a short tag, with a
    label, an optional account name and a note saying what it is for. Secrets are sealed by the
    operating system keyring and written to <userData>/vault.json at mode 0600. There is no
    plaintext fallback and no reveal control: on a session with no GNOME Keyring or KWallet the
    Vault refuses to store anything and says so, and the only way to change a stored value is to
    type a new one over it.
  • What a conversation can see: two tools, and the difference between them is the design.
    vault_list returns tags, labels, account names, notes and the environment variable each
    credential would arrive under — never a value — and is a read, allowed in every permission mode,
    because a model that cannot see which credentials exist asks you for one in chat instead.
    vault_use spends one, and always stops for your approval first, including under Full
    access: the question is not whether a turn may change files but whether it may act as you, and
    no permission level can answer that in advance.
  • How the secret actually travels: nowhere near the model. The unsealed value stays in
    Antimatter's main process — it is not sent to the window, to the bundled tool server, or into a
    tool argument, which is what the approval prompt quotes, what the transcript stores and what is
    replayed to the model on every later round of a turn. Antimatter sets it as an environment
    variable on the shell that runs the next command, not on the command line, because
    /proc/<pid>/cmdline is world readable on Linux and /proc/<pid>/environ is not. The model is
    told the variable's name and how to read it from standard input.
  • Bounded by the approval, not by the turn: one approval covers at most ten commands and five
    minutes, so a privileged step of two or three commands does not become a reflex of repeated
    prompts. The grant is dropped when the turn ends, when the Vault is switched off, and when the
    credential is edited — a replaced secret never stays armed in a run already under way.
  • Accidental leaks are masked: every tool result that passes the Vault, not only the shell's,
    is scanned and the granted value replaced with [vault:<tag> redacted] before the model or the
    transcript sees it. That covers env, a script that prints its own configuration, a file the
    secret reached and a delegated agent's report. It does not cover deliberate exfiltration — a
    model granted a secret runs commands that can encode it — which is why each use is a decision
    you make with the reason in front of you.
  • Its own card in the transcript: a Vault call does not render as an ordinary tool row. It gets
    a framed card with the vault mark, the credential's tag, the stated purpose in full, and a
    standing line saying the value is not in the card, was not sent to the model and is not in the
    transcript. There is no "show value" control because the window was never given one.
  • Never unattended: scheduled runs, orchestrated work and delegated sub-agents receive no Vault
    tools at all, catalogue included. There is nobody there to approve a use, and only the
    conversation you are watching can spend a credential.

Also fixed:

  • An unavailable Pensieve bundle no longer fails the turn it was attached to. vendor/pensieve/
    is gitignored...
Read more

Antimatter v21

Choose a tag to compare

@bytetroll bytetroll released this 05 Nov 05:09

Antimatter v21

Desktop v21 uses compatibility package 21.0.0. This is the first desktop
binary release assembled from the clean public source history. Android retains its
public v1 label, with package 21.0.0 and upgrade counter 10015, but is
not published as an installable APK in this release.

  • Standalone public project: MIT licensing, contributor and security guidance,
    support links, and source/history audit tooling. Setup and release documentation
    use explicit configuration without assuming a maintainer's machine, private
    network, or companion checkout.
  • Choose a trusted update folder: discovered feeds can show available updates,
    but installation requires selecting and saving a trusted folder in Settings →
    Updates. Clearing or changing that selection cancels pending work for the old
    feed. Automatic updates remain available for the folder you have selected.
  • Fresh backend packages: CPU and experimental HAG binaries are imported from
    the reviewed public Beholdd build with exact commit, archive and file hashes.
    The pinned Vulkan compatibility runtime remains included. Graphics drivers are
    supplied by the host system; HAG remains experimental with its documented model
    and hardware limits.
  • Dependency and license inventory: Electron 44.10.2, Vite 6.4.5 and Model
    Context Protocol SDK 1.32.2, with updated transitive dependencies. Each release
    includes a CycloneDX inventory reconciled against its packaged JavaScript and
    Electron files, plus dependency, Rust runtime and embedded-template notices.
    Debug source maps are excluded from desktop packages so upstream build-machine
    paths do not enter the distributed application; the final path-leak check remains enforced.
    The unchanged Vulkan binaries retain their reviewed public upstream diagnostic
    paths, verified against the pinned distribution and distinguished from our build paths.
  • Reproducible release checks: isolated assembly checks the desktop and Android
    sources, native PTY, backend health/model discovery, ABI requirements, installer,
    repair and uninstall behavior. The updater smoke uses the current package in a
    temporary profile; it does not establish compatibility with every historical
    binary or replace device/model qualification.

The Android build is retained separately as a tested, unsigned and non-installable
handoff. Production signing and phone installation verification remain necessary
before distributing an Android APK. Desktop assets do not contain that unsigned APK.

Supported build hosts use Node.js 22.20+, 24.12+, or 25+. Public release identity,
installer pins, package metadata and Android counters remain synchronized. Existing
release history is retained below.


Antimatter v14 — previous release

Desktop v14 adds the Vault: credentials you keep on this computer that a conversation may
use without ever being told what they are. The compatibility build is 14.0.0; Android
remains v1, with upgrade counter 10011.

  • The Vault, off until you turn it on: Settings → Vault. Store the credentials you would
    otherwise type by hand — your sudo password, a service login — each under a short tag, with a
    label, an optional account name and a note saying what it is for. Secrets are sealed by the
    operating system keyring and written to <userData>/vault.json at mode 0600. There is no
    plaintext fallback and no reveal control: on a session with no GNOME Keyring or KWallet the
    Vault refuses to store anything and says so, and the only way to change a stored value is to
    type a new one over it.
  • What a conversation can see: two tools, and the difference between them is the design.
    vault_list returns tags, labels, account names, notes and the environment variable each
    credential would arrive under — never a value — and is a read, allowed in every permission mode,
    because a model that cannot see which credentials exist asks you for one in chat instead.
    vault_use spends one, and always stops for your approval first, including under Full
    access: the question is not whether a turn may change files but whether it may act as you, and
    no permission level can answer that in advance.
  • How the secret actually travels: nowhere near the model. The unsealed value stays in
    Antimatter's main process — it is not sent to the window, to the bundled tool server, or into a
    tool argument, which is what the approval prompt quotes, what the transcript stores and what is
    replayed to the model on every later round of a turn. Antimatter sets it as an environment
    variable on the shell that runs the next command, not on the command line, because
    /proc/<pid>/cmdline is world readable on Linux and /proc/<pid>/environ is not. The model is
    told the variable's name and how to read it from standard input.
  • Bounded by the approval, not by the turn: one approval covers at most ten commands and five
    minutes, so a privileged step of two or three commands does not become a reflex of repeated
    prompts. The grant is dropped when the turn ends, when the Vault is switched off, and when the
    credential is edited — a replaced secret never stays armed in a run already under way.
  • Accidental leaks are masked: every tool result that passes the Vault, not only the shell's,
    is scanned and the granted value replaced with [vault:<tag> redacted] before the model or the
    transcript sees it. That covers env, a script that prints its own configuration, a file the
    secret reached and a delegated agent's report. It does not cover deliberate exfiltration — a
    model granted a secret runs commands that can encode it — which is why each use is a decision
    you make with the reason in front of you.
  • Its own card in the transcript: a Vault call does not render as an ordinary tool row. It gets
    a framed card with the vault mark, the credential's tag, the stated purpose in full, and a
    standing line saying the value is not in the card, was not sent to the model and is not in the
    transcript. There is no "show value" control because the window was never given one.
  • Never unattended: scheduled runs, orchestrated work and delegated sub-agents receive no Vault
    tools at all, catalogue included. There is nobody there to approve a use, and only the
    conversation you are watching can spend a credential.

Also fixed:

  • An unavailable Pensieve bundle no longer fails the turn it was attached to. vendor/pensieve/
    is gitignored apart from its manifest, because the corpus is not distributable — so a checkout
    routinely carries the Pensieve opt-in from an earlier run with no bridge.py to honour it. The
    runtime was attached on the strength of the setting alone, and every turn then died with
    Pensieve bundle unavailable: ENOENT …, on every model, since the bundle has nothing to do with
    which model answers. Enabling now requires the bundle to be reachable as well as the setting to
    be on; an unreachable one stands the experiment down and reports itself on the Experimental page,
    where the reason was already being displayed.

Antimatter v13 — previous release

Desktop v13 adds persistent per-project memory, a review workspace shared between you and
the agent, and one Code workspace that holds Ny and Matrix together. The compatibility build is
13.0.0; Android remains v1, with upgrade counter 10010.

  • Pensieve project memory, experimental and off by default: enable it under Settings →
    Experimental → Pensieve
    . Project conversations gain a persistent memory of NIL, Ny and Matrix
    references, observed results and verified repairs. Each canonical project root keeps its own
    store under <userData>/pensieve/projects/, is recalled into later conversations, and survives
    application restarts; turning Pensieve off preserves what it has saved. The model receives two
    tools: pensieve_recall for bounded references and evidence, and pensieve_check_project, an
    app-owned compile-only check that pins the SDK and verifies source identity before and after.
    The switch applies to this profile and does not change the selected model.
  • What the memory trial does not cover yet: interactive chat and Code in a confirmed project
    folder only — delegated and scheduled agents do not receive this runtime. The check needs a
    nil.project.json manifest and an SDK matching the pinned curriculum (395 entries at SDK source
    9e3341501ee697dd5150464a4d7ffc952644145b). Automatic checks cap source capture at 512 files
    and 4 MiB, with a 60-second deadline and 64 checks per turn. A passing check proves that the
    entry and its imports compile; it does not certify runtime or application behavior, so run the
    application and its acceptance cases as part of the workload. Learned evidence currently
    requires the same curriculum ID, and background consolidation stays disabled for the trial.
  • Code Review, shared between you and the agent: capture working changes or selected source
    lines into an immutable snapshot, so findings stay anchored as the code moves on. Attributed
    discussion, verification states and review decisions persist per workspace. Open Code Review
    on the tool stripe or Review code in the editor; Ask agent to review prepares a chat
    draft, and agents can create and annotate reviews through their own tools. Only you can resolve,
    dismiss, approve or request changes. Review annotations never stage files, change source, or
    publish to GitHub.
  • One Code workspace for Ny and Matrix: a new welcome screen starts a NIL Framework project
    with source, a build manifest and a runnable entrypoint — as a Ny application, a Matrix
    application, or a Matrix entrypoint with a Ny module — or opens an existing folder. Matrix joins
    Ny in editor highlighting and intelligence, with a reworked toolbar, console pane and framework
    project panel.
  • **Code folders now fol...
Read more