Get Aura Wire AI Command Center

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

1. 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.
2. 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.
3. If a Host process is still running, end Aura.Wire.Host in Task Manager (Windows) or Activity Monitor (macOS).
4. 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).
5. 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.
6. 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.