Skip to content

About

A multi-model AI coding workspace for local inference and hosted providers.

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

37 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Antimatter

Antimatter is a multi-model AI coding workspace for local inference and hosted providers. It combines conversations, project tools, code review, terminals, previews, and agent orchestration in an Electron desktop application. A native Android companion connects to a paired desktop host.

Use OpenAI Responses, Anthropic Messages, OpenCode Zen, or an OpenAI-compatible endpoint through the source-scoped Model Library. Local inference is optional: using a hosted provider does not require a local model download or access to a particular development network.

Project status

Current release: v23 (compatibility package 23.0.0).

Use the GitHub Releases page for published binaries, manifests, and checksums. Release builds pass source/history audits, dependency and license verification, and standalone packaging checks before publication. The source tree's version label alone does not establish matching binary availability.

Linux x86_64 is the packaged desktop target. The Android companion remains a preview; this release retains its unsigned build separately pending production signing and device verification. Experimental features are opt-in and have explicit limits; availability in the interface does not imply support for every model or device.

Features

  • Rust/C++ projects with build, test, run, language services, LLDB debugging, and a visual source board.
  • Cluster vitals, workspace security reports, and feature flags with a native C and Matrix SDK.
  • Optional Comms and Email plugins with configurable provider sign-in and project-specific agent permissions.
  • Private chat notes, idle compaction, nested project groups, complete themes, shortcuts, and a saved-reply pad.

See native development tools, Comms and Email setup, dashboards, and the Feature SDK for setup and current limits.

  • Multi-provider conversations: one model library for local engines, hosted providers, model prompts, runtime limits, and agent routing.
  • Coding tools: workspace-aware editing, permission-gated commands, an inline terminal, previews, code review, and per-project instructions.
  • Agent orchestration: delegated agents, visible progress, approvals, steering, cancellation, scheduled workflows, and isolated issue workspaces.
  • Work tracking: a Goetic board inside the window, worked by the same agent that writes the code, through a scoped and revocable Goetic credential.
  • Prompt Studio: an editor for the prompt itself, with spellchecking, fillable {{fields}}, checks for placeholders and vague wording, attachments, a saved prompt library, Reinterpret into an agent-ready brief, and a new-chat name, project and pin that apply when it starts one.
  • Conversation navigation: chronological tool activity, alternative transcript views, project grouping, pinned conversations, and reviewable chat imports.
  • Personalization: dark and light themes, accent colors, spellchecking, a draggable desktop avatar, profile settings, and editable project/user memory.
  • Remote workspaces: QR pairing, pinned HTTPS, and an Android client that leaves inference, credentials, tools, and project files on the desktop host.

Commands and generated changes require review. Full-access mode is not an operating-system sandbox. Remote pairing is an explicit LAN/VPN workflow, not an Internet relay.

Install a release

Obtain a complete artifact set from the project's GitHub Releases page when available, or from a release feed provided by a trusted distributor. Copy the files to a local directory, verify their checksums, read the included release notes, then run the installer as your normal desktop user:

chmod 755 ./install.sh
./install.sh --skip-model

The Linux installer targets Ubuntu 22.04+, Debian 12+, or another GNU/Linux distribution with glibc 2.34+. It does not require root. --skip-model installs the application without downloading a checkpoint; configure a provider or an existing local source in Model Library.

Omit --skip-model to provision the pinned Qwen3-Coder 30B A3B Instruct Q8_0 model. Its download is approximately 30.25 GiB and is verified against a pinned size and SHA-256. Check memory and storage requirements before choosing this option. See the release guide for the full asset list, integrity boundary, installation paths, and uninstall behavior.

Local inference

The package's standard Beholdd source is the CPU path. The temporary llama.cpp compatibility (Vulkan) source provides GPU offload and requires a working system Vulkan driver. Drivers, firmware, kernel modules, and ICD configuration are not bundled. The compatibility service starts lazily when the first request is sent; performance depends on available memory and offload.

The HAG runtime experiment uses a separate Beholdd executable and a pinned Qwen3 0.6B checkpoint. Its current package targets supported AMD GFX1151 systems and a bounded text-only preview. It is not a general replacement for the CPU/Vulkan paths. Read the hardware and request limits before enabling it.

Updates

The current updater reads a trusted local or mounted release feed selected in Settings → Updates. It verifies artifacts and waits for active work and unsaved buffers to clear before restarting. Discovered feeds are informational until you explicitly select a trusted folder; discovery never authorizes an installer to run. No particular server, account, VPN, or share is required to run Antimatter. A public HTTPS/GitHub automatic-update transport is not implemented; GitHub release downloads and the mounted-feed updater are separate workflows. See Updates.

Build from source

Use Node.js 22.20+, 24.12+, or 25+, matching the repository's packaging requirements.

npm ci
npm run typecheck
npm test
npm run dev

The tracked Displacer token snapshot is sufficient for typechecking and renderer development. The desktop can use a separately configured inference source. Preparing redistributable local backend binaries is a separate step: scripts/deps.json defines source repositories, optional source-directory overrides, exact pins where required, and artifacts to verify. Do not assume that every optional companion dependency is already public or available on a fresh machine.

For a new packaged release, both Beholdd CPU and HAG binaries must be rebuilt from their clean public-history source pins using ANTIMATTER_BEHOLDD_SOURCE and ANTIMATTER_BEHOLDD_HAG_SOURCE. Existing checked-in binary manifests and license inventories remain historical evidence; they do not qualify those binaries for this source release. Full Displacer source refreshes require a separate reviewed checkout; ordinary renderer development uses the tracked MIT-licensed token snapshot. See maintainer assembly and development and validation.

For Android, configure JDK 17+ and Android SDK 36.1, then run npm run android:verify. The Android guide distinguishes local debug builds, production signing, and physical-device checks.

Goetic work tracking

Goetic is a project tracker built for human and AI contributors, and Antimatter is one of those contributors. The Goetic tool window shows a project's boards and lifecycle work beside the conversation, and the agent reads and changes the same board through the same machine API — so the person steering and the agent doing the work share one state and one phase vocabulary instead of a chat here and a browser tab there that disagree by a refresh.

Antimatter authenticates to Goetic as an agent identity with its own bearer token, scoped per board and per action by whoever administers the Goetic workspace. It acts as itself: every card it files or moves is attributed to that identity in the card's history, including the panel's own writes, because that is whose credential carried them.

Point it at a Goetic instance in the panel's Settings tab, or with GOETIC_URL and GOETIC_TOKEN. The credential is stored 0600 in ~/.antimatter/goetic.json, stays in the main process, and is never handed to the renderer. A plain-HTTP address that is not loopback is refused rather than putting a long-lived token on the wire.

Antimatter cannot mint, rotate or re-scope a Goetic credential. Those are browser-only operations in Goetic, so an agent cannot promote itself; ask whoever administers the workspace to admit an identity and pass on the token Goetic prints once. What the tools can do is bounded by that credential's scopes, which the Settings tab lists.

The tools are goetic_status, goetic_universes, goetic_board, goetic_cards, goetic_card and goetic_card_history (reads), and goetic_create_card, goetic_update_card, goetic_move_card, goetic_archive_card and goetic_restore_card (writes). Goetic owns the rules: phase gates, work-in-progress limits and stale-write conflicts are enforced there and reported in Goetic's own words. Archiving is how a card is deleted — history is preserved and it can be restored.

What an agent records on a card is that agent's own assertion. It is not independent verification, and nothing here authorizes a release or a deployment.

Documentation

Keep credentials, personal conversations, private project instructions, and machine-specific configuration outside the repository. Sanitized examples should use placeholders and documentation-only hosts rather than real accounts or internal infrastructure.

Versioning

Antimatter uses Execute's rolling release scheme: v1 → v2 → v3. VERSION is authoritative; npm run release:version performs the mechanical increment and synchronizes package metadata. A default-branch change earns a new rolling version, committed with that change. Do not manually change one version field in isolation.

Packages, filenames, manifests, and existing updaters retain the compatibility form N.0.0. The v<N> and v<N>.0.0 tags identify the same release commit, not separate release lines. Component and plugin API compatibility versions remain independent.

Support the project

Antimatter is built by Execute Software and its community. See CONTRIBUTORS.md for the core team and contributor credits.

You can support Execute Software's work through Ko-fi. Contributions are optional and do not change provider fees or grant access to a maintainer's private infrastructure.

For enterprise licensing and support, contact admin@executesoftware.com.

License and publication

Antimatter is licensed under the MIT License. Third-party components and models retain their own licenses and notices. See the publication checklist for the remaining source, history, dependency, and artifact review gates.

About

A multi-model AI coding workspace for local inference and hosted providers.

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages