Download

Aura Wire AI Command Center for Windows. The installer can add the editor extension. Aura Terran Knowledge installers too. Free to try — no account, no card.

Aura Wire AI Command Center

v1.2.56

The Windows command center is the product. It runs the local Host for any IDE, CLI, SDK, or app, and Capture covers programs you switch on. The installer can also add the editor extension.

14-day full-pipeline trial starts with your first chat. No key, no card.

Download for Windows — free trial

Setup guide

Want chat inside an editor? The installer offers that, or download Visx from this site.

What installs, and how to remove it

What Aura Wire AI Command Center puts on your machine

A Windows application — AuraWire-Setup.exe installs the desktop command center, the local Host, and the wire CLI, and adds a Start menu shortcut. It can also add the editor extension to VS Code, Cursor, and Windsurf when those editors are already installed.
Capture — the installer registers a redirect service. Windows asks for administrator approval once. You approve a local certificate in the app before HTTPS from switched-on programs is inspected. Programs you do not switch on, including your browser, are not redirected. Only allowlisted AI provider hosts inside a switched-on program are inspected.
A VS Code extension — installed by your editor into its normal extensions folder, like any other extension. It adds chat, dashboards, and a sidebar to the editor. On Windows it is optional; on a Mac it is how you install Wire.
A local Host program — the extension downloads Aura.Wire.Host from our release feed the first time you open a chat, checks the file’s checksum, and stores it in your per-user data folder (%LOCALAPPDATA%\AuraWire\host on Windows, ~/Library/Application Support/AuraWire/host on macOS). It listens on 127.0.0.1 only and keeps running after you close the editor until you remove it.
Host data in that same AuraWire folder — settings, the provider API keys you enter (kept in a file in your per-user folder; not sent to Bitfield Creek Labs), your license or trial record, Host logs, a random install identifier, and the traffic database. That database holds sanitized metadata: provider, model, token counts, latency, and cost estimates — not prompt or response text.
Your chat history — the extension saves your conversations (including prompts and replies) so you can reopen them. They live in your editor’s extension storage under halosoftworks.aura-wire-vscode, not in the Host’s traffic database, and they stay on this machine.

What it does not do

The editor extension itself asks for no administrator rights, certificate, or driver. Those prompts belong to Capture on the Windows installer, and the certificate is not installed until you approve it in the app.
No changes to your browser, proxy, or system settings. Other programs are not affected.
No third-party programs are installed. The Host ships its own copy of Node.js and the Cursor, Claude, and Bitfield Ollama Agent SDKs it uses as libraries; they run only inside Wire. If you click Install on the Bitfield Ollama Agent provider card, a private copy of @bitfieldcreek/bf-agent is added under %LOCALAPPDATA%\AuraWire\bitfield-agent. The same runtime is also offered on its own as a free command-line tool.
The extension checks our release feed for a newer extension or Host when the editor starts (and about once an hour while it stays open). A newer Host under the AuraWire data folder is replaced automatically (no cleanup step). A newer extension build is offered in the editor and installs only when you accept it.
Prompts and responses are not sent to Bitfield Creek Labs. The extension does send a few de-identified events: that it was installed or updated, a once-a-day “still installed” ping, whether the Host started, and the result of an update check — each with the extension version, OS, a coarse editor label (VS Code, Cursor, other), and a random install identifier. No usernames, file paths, or project names. Details in the Privacy Policy.
The provider you pick for a chat (OpenAI, Anthropic, Cursor, Ollama, and so on) receives that request under its own terms. Wire does not change what you send them.

How to remove it completely

In the command center, turn off Route through Aura Wire and use the remove control under Settings → Setup → IDE for the redirect service. Remove the local certificate from Settings → Setup → Certificate. Then uninstall Aura Wire AI Command Center from Windows Settings → Apps.
In your editor open Extensions, find Aura Wire AI Command Center, and choose Uninstall. A few seconds later the extension removes the Host it downloaded, unless the desktop command center is installed or another editor on this machine still has the extension.
If a Host process is still running, end Aura.Wire.Host in Task Manager (Windows) or Activity Monitor (macOS).
Delete the data folder: %LOCALAPPDATA%\AuraWire on Windows or ~/Library/Application Support/AuraWire on macOS. This removes settings, provider keys, the license record, logs, the traffic database, and any private Bitfield Ollama Agent copy (bitfield-agent subfolder).
Delete chat history: in your editor’s user folder (VS Code on Windows: %APPDATA%\Code\User; Cursor: %APPDATA%\Cursor\User; macOS: ~/Library/Application Support/Code/User), remove the halosoftworks.aura-wire-vscode folders under globalStorage and each workspaceStorage\… entry. Your editor may or may not clear these on its own.
If you ran Aura Wire: Add Cursor rule pointing at chat history in a project, delete .cursor/rules/aura-wire-chat-history.mdc from that project.

After these steps nothing from Aura Wire AI Command Center remains on the machine.

Aura Terran Knowledge

v1.12.30

Local knowledge center: index project folders on your PC and serve them to agents over MCP and REST.

14-day full trial starts on first launch. No key, no card.

Download for Windows — free trial Setup guide

Digitally signed by Halo Softworks LLC · Microsoft Azure Artifact Signing

Windows installer only — this .exe will not run on Mac, Linux, phones, or tablets. Signed by Halo Softworks LLC, the legal name of Bitfield Creek Labs; confirm that publisher if Windows prompts you. Verify the signature and SHA-512 checksum below if you want.

Verify this download

Verify your Bitfield Creek Labs download

Bitfield Creek Labs Windows installers are digitally signed using Microsoft Azure Artifact Signing. The certificate is issued to Halo Softworks LLC — our registered company name — so that is the publisher Windows shows. A valid signature confirms that the installer came from us and has not been modified since it was signed.

If Windows shows a security prompt, confirm the publisher is Halo Softworks LLC before continuing.

Before running the installer, confirm the following details.

Product: Aura Terran Knowledge
Version: v1.12.30
Filename: AuraTerran-Setup-1.12.30.exe
Publisher: Halo Softworks LLC
SHA-512: 5c70e1b4bbab0b0cbb8b2fd411a3c19873b3be93f1d7eae7e3bc0216b0c32b9e6e35e469af9564fb77691dff1398d84124c6c6cce640d02d8b5fd3a15a4bb7d1
File size: 170 MB
Released: October 14, 2026

Check the digital signature in Windows Explorer

Right-click the downloaded installer.
Select Properties.
Open the Digital Signatures tab.
Select the Halo Softworks LLC signature.
Choose Details.
Confirm that Windows reports that the digital signature is valid.

Check with PowerShell

Get-AuthenticodeSignature .\AuraTerran-Setup-1.12.30.exe | Format-List *

Expected: Status: Valid and a signer/publisher of Halo Softworks LLC.

Check the SHA-512 checksum

Get-FileHash .\AuraTerran-Setup-1.12.30.exe -Algorithm SHA512

Compare the Hash value with the SHA-512 shown above (case-insensitive).

If Windows SmartScreen shows a reputation notice, select More info to reveal the publisher. Continue only when it reads Halo Softworks LLC and the installer came directly from the Bitfield Creek Labs website; otherwise delete the file. Bitfield Creek Labs does not recommend disabling SmartScreen.

Download security guide · User guide

What installs, and how to remove it

What Aura Terran Knowledge puts on your machine

A Windows application — a standard setup wizard (.exe or .msi) that shows the EULA, lets you choose the install folder (default %LOCALAPPDATA%\Programs\Aura Terran), and adds Start menu and desktop shortcuts.
Your knowledge bases and settings — indexed documents, embeddings, app settings, your license or trial record, a local request log, and a random device identifier live under %USERPROFILE%\.aura-terran. Documents are indexed on this PC and are not uploaded.
Embedding model files — the first time you index, the app downloads the on-device embedding model (a few files from huggingface.co) into %USERPROFILE%\.aura-terran\models. Only the model is downloaded; none of your documents are sent. After that, indexing and search work offline.
App cache and update files — the app framework keeps window state and cache under %APPDATA%\aura-context-hub (the app’s internal folder name) and downloaded updates under %LOCALAPPDATA%\aura-context-hub-updater.
Local network ports — the Management API (default 41800), inbound MCP (default 41801), and optional passthrough listeners listen on 127.0.0.1 only, with bearer-token authentication on by default, so tools on this PC can query your corpus.

What it does not do

No changes to your browser, proxy, or system settings. No driver, no certificate.
No third-party programs are installed; the app’s own runtime and search backend run only inside Aura Terran Knowledge. While running, the app checks our release feed about every four hours, downloads a new version in the background, and installs it when you close the app. Updates replace only Aura Terran Knowledge.
Your documents stay on this PC unless you turn on optional remote model providers, web search, or external tools — those send request text to the services you configure, under their terms.
The app sends a few de-identified events: install succeeded (from the installer), session start and end with approximate run time, and one uninstall notice — each with the app version, an OS label, and a random device identifier. Trial start and license activation send the product, that device identifier, the app version, and (for activation) your license key. Crash reports go out only if you click Send. None of these include documents, file names, or search text. Details in the Privacy Policy.
It edits another program’s settings only when you ask: the one-click MCP setup adds an aura-terran entry to Cursor’s ~/.cursor/mcp.json or Claude Desktop’s config file.

How to remove it completely

Open Windows Settings → Apps → Installed apps, find Aura Terran Knowledge, and choose Uninstall. The standard Windows uninstaller removes the program and shortcuts and sends the single de-identified uninstall notice mentioned above.
Delete %USERPROFILE%\.aura-terran to remove your knowledge bases, settings, license record, and the cached embedding model.
Delete %APPDATA%\aura-context-hub and %LOCALAPPDATA%\aura-context-hub-updater to remove the app cache and any downloaded update.
If you used the one-click MCP setup, remove the aura-terran entry from Cursor’s or Claude Desktop’s MCP config.

After these steps nothing from Aura Terran Knowledge remains on the machine.

Windows showed a SmartScreen prompt. What now?

Microsoft Defender SmartScreen warns about installers it has not seen often yet. It is a reputation notice, not a malware detection. Our installers are digitally signed by Halo Softworks LLC (the legal name of Bitfield Creek Labs); the certificate is new, so it has little download history.

Do not continue until you can see the publisher. Windows hides it until you select More info.
Confirm the publisher reads Halo Softworks LLC and that you downloaded the file from this site. If either is not true, delete the file and download again from this page.
If both check out, you can allow the installer to run. Optionally verify the signature and SHA-512 checksum first.

Bitfield Creek Labs does not recommend turning SmartScreen off. Verify the publisher instead.

Before you install

Installing accepts the End User License Agreement. Windows installers ask again before they finish.
Questions? Contact us or email contact@bitfieldcreek.com.