> For the complete documentation index, see [llms.txt](https://doc.lockerprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.lockerprotocol.com/hyper-agentic-trader/install.md).

# Install lpa

Put the lpa command on your computer, then check it with lpa doctor.

`lpa` is the engine of Hyper Agentic Trader as a command you run in a terminal. The application installs it for you, on this computer or on a machine you reach over SSH, and most people never type it: see [The application](https://doc.lockerprotocol.com/hyper-agentic-trader/application.md). This page is for a terminal of your own, a server or a script. There are two ways to install it: a one-line installer that also fetches Node.js if your machine has none, or npm if you already live in Node.

{% hint style="info" %}
**Never opened a terminal?** On a Mac, press Command and Space, type `Terminal`, press Enter: a window opens where you type commands. On Linux, open your terminal from the applications. On Windows, open PowerShell. Paste the line below into it and press Enter. The installer talks while it works, and ends by telling you the one thing to do next.
{% endhint %}

## What you need

* A computer with a terminal: macOS, Linux or Windows.
* **Node.js 22.13 or later**, which the one-line installer downloads for you when it is missing. That version is the first that can read the record `lpa` keeps of what it does, without a special flag.
* For a real account: a wallet that signs for it. [Locker Vault](https://doc.lockerprotocol.com/hyper-agentic-trader/get-locker-vault.md) on an offline phone or tablet, with a webcam on the computer, is the safest and the one we recommend; your browser extension (MetaMask, Rabby) or your mobile wallet can sign instead ([Three ways to sign](https://doc.lockerprotocol.com/hyper-agentic-trader/agent.md#three-ways-to-sign-for-your-account)).
* For trading in simulation: nothing else. No key, no wallet, no money.

## The one-line installer

The installers are served by [hyperagentictrader.com](https://hyperagentictrader.com), the product's own site, and nowhere else.

{% tabs %}
{% tab title="macOS and Linux" %}

```sh
curl -fsSL https://hyperagentictrader.com/agent-wallet-install.sh | sh
```

On a server, to install the guardian as a service in the same go:

```sh
curl -fsSL https://hyperagentictrader.com/agent-wallet-install.sh | sh -s -- --service
```

{% endtab %}

{% tab title="Windows (PowerShell)" %}

```sh
irm https://hyperagentictrader.com/agent-wallet-install.ps1 | iex
```

On Windows the guardian has no system service. `lpa agentd --service` in a terminal you leave open does the same job. The MCP launcher is `%USERPROFILE%\.lpa\bin\locker-mcp.cmd`.
{% endtab %}
{% endtabs %}

Everything lands in `~/.lpa`, with no administrator rights:

* `~/.lpa/lib`: this package and the MCP server, `@locker-protocol/agent-wallet-hyperliquid-trader-mcp`, one copy and one version for both.
* `~/.lpa/bin`: two launchers, `lpa` and `locker-mcp`.
* `~/.lpa/node`: Node.js, **only** when the machine had no Node 22.13 or later. It is downloaded from nodejs.org and checked against the SHA-256 written into the script.

Running the installer again updates. The installer also checks that `locker-mcp` answers at the same version as `lpa`.

When it ends it says what comes next, and where:

```
Installed: lpa <the version published>, in /Users/you/.lpa.

Next: Open a new terminal window (or run: export PATH="/Users/you/.lpa/bin:$PATH"), then type:
    lpa setup
It walks the whole way, step by step: your AI model, your phone with Locker Vault, some funds, your limits.
No phone or no money yet? lpa setup --paper opens a simulation account instead. lpa status says where you are.
A model is included with your plan: lpa hyperkeel login connects this terminal to your account, and lpa setup recommends it.

For AI assistants (optional), the MCP server: /Users/you/.lpa/bin/locker-mcp (Claude Code: claude mcp add locker -- /Users/you/.lpa/bin/locker-mcp)
```

**Open a new terminal window first**: the one you installed from does not know `lpa` yet (it would answer `command not found`). On a server, log out and back in instead. With `--service` and no terminal to ask the console's password in (a provisioning script, a command handed to `ssh`), `lpa` is installed all the same and the installer says the step left: `lpa service install`, in a session you type in.

## With npm

```sh
npm install -g @locker-protocol/agent-wallet-hyperliquid-trader@latest
```

This installs the `lpa` command alone. An MCP client can then fetch the server with `npx` at `@latest`, which is the newest release at each start. Run the same line again when a version comes out, so that `lpa` follows.

{% hint style="info" %}
**Keep the two sides at the same version.** A guardian signs nothing for a program of another version: the order answers `VERSION_MISMATCH` and tells you what to do (`lpa lock`, then `lpa unlock`; for a service, `lpa service restart`). The one-line installer's launcher never has this problem, because it updates both at once. An MCP client started by `npx` at `@latest` takes a new version at its next start: when one comes out, run the installer again, then `lpa service restart` (or `lpa lock`, then `lpa unlock`).
{% endhint %}

## Check the install

```sh
lpa --version
lpa doctor
```

## lpa doctor

`lpa doctor` checks the setup and signs nothing. Each line reads `ok`, `FAIL` or `-` (not set up yet), and the last line is the one step to take next. It exits with code 1 when a check fails, so a script can rely on it.

```
ok  node         Node 24.21.0
ok  home         /Users/you/.lpa mode 700
ok  config       config.json mode 600
ok  files        9 kept private
ok  record       13 lines, 0.26 MiB, schema 2
ok  journal      0.0 MB; rotates past 64 MB, one older part kept
ok  hyperliquid  api.hyperliquid.xyz answers in 180 ms; clock drift 42 ms
ok  account      0x3f5CE5FBFe3E9af3971dD833D26bA9b5C936f0bE (m/44'/60'/0'/0/0)
ok  agent        0x8c1f3B0Ad6E3fD2b6e9C1A4c2f0B7b9d3e5A9a2e, 179 days left
-   mandate      none: the local policy alone bounds the agent (lpa mandate sign signs one on the phone)
ok  setup        complete
ok  funds        equity $55.78
ok  guardian     a terminal, unlocked until 2026-09-30T16:40
-   service      not installed: nothing runs once this terminal closes (lpa service install)
-   console      no password yet: lpa service install asks for one (lpa console password)
ok  policy       $100 an order, 3x, the main dex, 20 orders a day, no end
ok  assistant    anthropic claude-sonnet-5, its key in the keys file
-   hyperkeel    not connected, and optional: lpa hyperkeel login
-   paper        no simulation account (lpa paper init --budget 1000)
Everything that is set up works.
Next: Nothing to do: 'lpa' opens the session, and 'lpa journal' says what was done.
```

What each check looks at: Node's version; the `~/.lpa` folder at mode 700 with every file at 600; the record of what it did (`activity.db`), and whether it reads whole; the journal's size on disk; Hyperliquid reachable, with your clock within 10 seconds of its own (it refuses orders whose timing is too far off); your account; an agent left half-approved by an interrupted setup; the agent as Hyperliquid lists it, and whether it has expired; the mandate and its standing; the last signature of the setup; funds on Hyperliquid; the guardian, locked or unlocked, and its version; the service and its console; the policy; the assistant's model and where its key comes from; hyperkeel; the plugins installed and whether their files are the ones you approved; the simulation account.

{% hint style="warning" %}
**A clock that drifts breaks trading.** Hyperliquid refuses orders timed too far from its own clock. If `doctor` complains about drift, turn on automatic time on your computer.
{% endhint %}

## Remove it

* Installed by the one-line installer: `lpa uninstall` removes `~/.lpa/node`, `~/.lpa/lib`, `~/.lpa/bin` and the line it added to your shell's startup file. `lpa uninstall --all` removes your settings and the sealed agent key too.
* Installed with npm: `npm uninstall -g @locker-protocol/agent-wallet-hyperliquid-trader`.
* To wipe the local state but keep the program: `lpa reset`.

The agent stays approved on Hyperliquid until its date, whatever you remove. `lpa agent revoke` retires it now, with your wallet.

## Next

{% content-ref url="/pages/nRfL9FELnOtsSvqYFtmu" %}
[Set up in a few steps](https://doc.lockerprotocol.com/hyper-agentic-trader/set-up-in-steps.md)
{% endcontent-ref %}
