BlackSec Agent documentation

BlackSec Agent is the native Windows desktop client for this platform. It stores your conversations, configuration and tooling locally, and talks to the same OpenAI-compatible gateway that your API keys already use. Installing it does not change anything about your account, your keys or your plan.

The product is private and closed-source: there is no public repository, and the installer is distributed only from the download section. If you obtained an installer anywhere else, verify its digest before running it.

The currently published release targets Windows x64. Node.js is only relevant if you intend to use plugins; the agent itself does not require it.

1. 1

   Download the installer

   Get the latest .exe from the download section. It is served directly from BlackSec — there is no third-party mirror.

2. 2

   Verify the digest (recommended)

   Compare the SHA-256 of the file you received against the published digest before you run it.

3. 3

   Run the installer

   Open the file and follow the setup wizard. The agent installs to %LOCALAPPDATA%\BlackSec\Agent by default.

4. 4

   Launch and authenticate

   Open BlackSec Agent from the Start Menu. Sign in with your BlackSec account, or point it at a custom API provider.

5. 5

   Start chatting

   Pick a model, type your prompt, and press Enter. The agent talks to the gateway automatically.

The application is installed to %LOCALAPPDATA%\BlackSec\Agent by default. Recent releases install and uninstall through a native themed wizard rather than a script.

The download section publishes a SHA-256 digest and an exact byte size for the current build. Hashing the file you received and comparing it is the only way to know the bytes on your disk are the bytes that were released.

# Windows PowerShell — run in the download folder
Get-FileHash .\BlackSecAgent-Setup-<version>-x64.exe -Algorithm SHA256

Compare the output character-for-character with the digest shown on the verification section. Comparison is case-insensitive; the digits are not. A mismatch means the file is corrupted or altered — delete it and download it again rather than troubleshooting further.

Launch BlackSec Agent from the Start Menu. On first run you authenticate in one of two ways:

• ▸Sign in with your BlackSec account. The agent authenticates against the platform gateway and inherits your plan, model access and limits.
• ▸Configure a custom API provider. Point the agent at an OpenAI-compatible endpoint of your choosing instead of the platform gateway.

Your session token is kept in memory and in the operating system credential store. The installer and the application do not write it to disk in plaintext, and stored API keys are encrypted with AES-256-GCM.

The agent is built to be driven from the keyboard. The set is deliberately small so it stays in muscle memory.

When signed in through the platform, the model picker lists every model your plan can reach. You can switch models mid-conversation, which is useful when a task changes shape — a long reasoning pass on one model, then a quick edit on another — without copying context between windows.

Each request reports tokens, latency and cost, so you can see what a model choice actually costs as you work. Model availability and pricing per plan are listed on the model catalog.

The agent is extensible through MCP servers, custom skills and hooks, so you can wire it into your own tooling instead of copying results between applications. Plugin authoring is the one part of the product that expects Node.js 18 or newer to be installed on the machine.

Plugins run locally under your own account and authorisation. You remain responsible for what you point them at — see the Installer License for the exact terms.

The agent checks this site for new releases and can update itself in place. Each update package is verified by cryptographic hash before it is applied, and a failed verification aborts the update rather than installing unverified code.

Updates may add features, fix defects, or remove capabilities. Continuing to use the software after an update means you accept the updated software under the same licence. Release notes for the current build are shown on the download section.

Remove the agent through the uninstall entry it registers with Windows, or from Settings → Apps. Recent releases ship a native themed uninstall experience rather than a bare script. Local application data — settings, session cache and logs — lives under the install path and is removed with it.

Most installation failures fall into a small number of causes, and the first check resolves the majority of them.

Installer will not run

Verify the SHA-256 digest first. If it does not match the published value, the download is corrupted or altered and no amount of troubleshooting will fix it — re-download. Then confirm the machine is Windows x64, which is the currently published target.

Install fails partway through

A leftover installation marker from an interrupted earlier run can confuse a fresh install. Current releases include a stale-marker guard for this case; if you are on an older build, remove the previous installation first and retry.

Cannot sign in

Confirm the account is in good standing and that the machine can reach this site. If you configured a custom API provider instead, check the base URL and key on that provider side.

Terminal behaves oddly

Release 1.46.60 fixed the terminal conpty path. If you are on an older build, updating is the fix.

The agent is an uncensored client and does not filter model output. Review and validate generated code or instructions before you execute them.

The platform team is reachable on Telegram for installation, licensing and integration questions. When you report a problem, include the agent version shown in the title bar and the exact error text — it shortens the round trip considerably.