Local brain (bma-dsh-acp)

@beeos-ai/bma-dsh-acp is the BMA build of the DeepSeek Harness (DSH) brain, served as an Agent Client Protocol (ACP) agent on stdin/stdout. The executor of your computer starts it and drives it: the brain thinks, and every tool it calls runs on your computer through the executor, so the hands are the same as for a platform brain. Sessions, events and approvals stay on BMA: you still send messages with /v1, and approvals reach every client of the session.

Install and run

npx --yes @beeos-ai/bma-dsh-acp@0.1.0                  # one-off
npm install -g @beeos-ai/bma-dsh-acp@0.1.0             # or install once; the bin is `bma-dsh-acp`
BMA_DSH_ACP_HOME=$HOME/.bma-dsh-acp bma-dsh-acp        # ACP (newline-delimited JSON-RPC) on stdin/stdout

Node.js 24 or later. Tested on Linux x64 and macOS arm64; Windows is untested.
BMA_DSH_ACP_HOME is required: the directory for the agent’s state (sessions are kept there for later loads). stdout carries ACP only; logs go to stderr.
DSH is not bundled. npm installs the official @deepseek-ai/* packages, whose versions @beeos-ai/bma-dsh-adapter pins exactly, including the transitive ranges DSH leaves open. One package version therefore always installs the same DSH (0.1.0 carries DSH 0.2.2-rc.1, reported by initialize as _meta.bma.dsh). Do not install with --omit=optional: the native file-lock addon is installed as an optional dependency for your platform.
Pin the version. npx @beeos-ai/bma-dsh-acp without a version takes the newest release; use @0.1.0 (the two packages @beeos-ai/bma-dsh-acp and @beeos-ai/bma-dsh-adapter always share one version). Upgrade by changing the pin.

Start it from the executor SDK

In the Go SDK (bma-executor-sdk 1.3.0 or later), ACPAgent starts the brain and serves BMA turns with it. The SDK never looks the command up on PATH, so Command[0] must be an absolute path:

agent, err := bmaexecutor.NewACPAgent(ctx, bmaexecutor.ACPAgentOptions{
    // installed once with `npm install -g @beeos-ai/bma-dsh-acp@0.1.0`:
    // the `bma-dsh-acp` bin of the npm prefix (see `npm prefix -g`)
    Command: []string{"/usr/local/bin/bma-dsh-acp"},
    // or fetched on first use: slow first start, the npm cache keeps it afterwards
    // Command: []string{"/usr/local/bin/npx", "--yes", "@beeos-ai/bma-dsh-acp@0.1.0"},
    StateDir: stateDir, // becomes BMA_DSH_ACP_HOME
    Core:     core,
    Upstream: bmaexecutor.ACPModelUpstream{BaseURL: "https://api.example.com/v1", Model: "my-model"},
})

npx and node are commands too: write their absolute paths (command -v npx), not bare names. The model endpoint comes from Upstream.

How it differs from the packaged forms

	npm package (this page)	Single-file bundle
Meant for	Developers, CLI tools, a local brain on your own computer	BMA Desktop and the BMA sandbox machine templates
DSH	Official npm packages, exact-pinned, installed by npm	Inlined into `bma-dsh-acp.mjs`, sha256-pinned by the template
Needs	Node.js 24 or later; network access to npm at install	Node.js 24 or later (`.mjs`) or nothing (SEA executable)
Updates	You change the version pin	Ships with the application or the machine template

Sandboxes use the bundled form and need nothing from you. Use the npm form only on a computer you run an executor on.

Executor Protocol

Roles, connection and deployment shapes

Agent capability

Bring your own agent loop instead

Get started

Concepts

Executor & brains

Install and run

Start it from the executor SDK

How it differs from the packaged forms

Executor Protocol

Agent capability

​Install and run

​Start it from the executor SDK

​How it differs from the packaged forms

Executor Protocol

Agent capability

Install and run

Start it from the executor SDK

How it differs from the packaged forms