> 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-on-a-server.md).

# Install on a server

The agent on a Linux server you reach by SSH, with its service, its console and your wallet, step by step.

A server runs the agent day and night, and the daily pilot plays its day whether your computer is on or not. What changes from your own computer: the server has no screen and no webcam, so the pages that ask your wallet to sign are shown on **your** computer, through the service's console and an SSH tunnel, and the service comes first.

{% hint style="info" %}
**What you need.** A Linux server (Ubuntu or Debian do well) you reach as an ordinary user with `ssh`; your own computer, with a browser; and the wallet that signs for the account: your phone with [Locker Vault](https://doc.lockerprotocol.com/hyper-agentic-trader/get-locker-vault.md), the safest, with a webcam on your computer, or else your browser extension or your mobile wallet ([below](#with-a-browser-extension-or-a-mobile-wallet)). Nothing runs as root. No server of your own? A small rented Linux machine does the job: a VPS with 1 vCPU and 1 GB of memory running Ubuntu 24.04, a few euros a month at any host, which you reach with `ssh` as an ordinary user, and the installer puts everything in that user's home. The whole way took about ten minutes when we timed it, with the Vault.
{% endhint %}

{% stepper %}
{% step %}

### Install, with the service, in an SSH session you type in

On the server:

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

The installer downloads Node.js if the server has none recent enough (checked against a SHA-256 written in the script), puts `lpa` in `~/.lpa` with no administrator rights, then sets up the service and asks a **console password**, twice: it is the password of the small web page through which you will reach the server from your computer. About half a minute in all.

```
Downloading Node.js v24.21.0 (linux x64) from https://nodejs.org/dist...
Checked: SHA-256 6e1db87e...
Installing @locker-protocol/agent-wallet-hyperliquid-trader@latest ... in /home/you/.lpa/lib...
added 112 packages in 14s

Installed: lpa <the version published>, in /home/you/.lpa.
Next: Log out and back in (or run: export PATH="/home/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.
...
Setting up the service: the guardian around the clock, with its console...
Console password (10 to 1024 characters, not the agent key's):
Once more:
Service installed (/home/you/.config/systemd/user/lpa.service).
It runs, locked: `lpa unlock`, or the console, gives it the key, which it then holds until the agent ends, ...
No account is set up yet: `lpa setup` sets everything up, its pages shown through the console from your own computer.
Linger is off: the service would stop with your last SSH session. Run once: sudo loginctl enable-linger $USER
Console: http://127.0.0.1:7717/ , to open in your own browser once this SSH tunnel runs from your computer:
  ssh -L 7717:127.0.0.1:7717 <the user@host you connect with>
  or once for all, under this machine in ~/.ssh/config: LocalForward 7717 127.0.0.1:7717
If port 7717 is taken on your computer, give another on the left (-L 7718:127.0.0.1:7717) and open http://127.0.0.1:7718/ instead.
```

If it says **Linger is off**, run the line it gives once (`sudo loginctl enable-linger $USER`): without it, the service stops with your last SSH session. From a provisioning script or a command handed to `ssh`, with no terminal to ask the password in, `lpa` is installed all the same and the installer says the step left: `lpa service install`, in a session you type in.

What to check: `systemctl --user is-active lpa.service` says `active`, and `lpa service status` says "Service installed, running. Locked". Log out and back in, so that the shell knows `lpa`.
{% endstep %}

{% step %}

### Reach the console from your computer

On **your** computer, open a tunnel to the server's console and keep it open:

```sh
ssh -L 7717:127.0.0.1:7717 you@your-server
```

Then open `http://127.0.0.1:7717/` in your browser and sign in with the console password. If `lpa` also runs on your own computer, port 7717 is taken there: give another on the left (`-L 7718:127.0.0.1:7717`) and open `http://127.0.0.1:7718/`. To keep it for good, under the server's entry in `~/.ssh/config`: `LocalForward 7717 127.0.0.1:7717`.

What the console shows: the service, locked for now, the list of the pages the commands on the server open, each as a link, and a place to ask the assistant in plain words once a model is set up ([below](#asking-in-plain-words-from-the-console)).
{% endstep %}

{% step %}

### Run the setup on the server

In the SSH session:

```sh
lpa setup
```

```
No screen here (this terminal is reached over SSH): the phone's pages go through the service's console, so the service comes first.
Step 1 of 9 · This computer
Node 24.21.0, ~/.lpa mode 700, api.hyperliquid.xyz answers in 499 ms; clock drift 774 ms.
Step 2 of 9 · Round the clock: done. The service runs. Console on http://127.0.0.1:7717/.
Step 3 of 9 · Your model
```

The steps are the ones of [Set up in a few steps](https://doc.lockerprotocol.com/hyper-agentic-trader/set-up-in-steps.md), the service second; the account's step asks how it signs, Locker Vault first. Each step that opens a page (the settings page for the model, the ceremony pages for the account, the deposit, the trading key, the mandate) says so in the terminal and waits:

```
No browser opens here: this terminal is reached over SSH. On your own computer, open:
  http://127.0.0.1:7717/    (then "Settings" in its list)
```

The page appears **in the console, in your browser**: refresh the console if the link is not there yet, and click it.
{% endstep %}

{% step %}

### The model, through the console

Step 3 explains the model and asks to open the settings page. The simplest on a server is the model included with your plan, which asks for no key: connect the server to your account first, with `lpa hyperkeel login --code`, which prints an address and a code you type on any device, your phone included; then say yes, open **Settings** from the console, and in the Assistant card choose **Hyper Agentic Trader** and `hat-fast`, **Use this model**, **Done**. See [Plans and credits](https://doc.lockerprotocol.com/hyper-agentic-trader/plans-and-credits.md).

With a provider of your own instead: say yes, and open **Settings** from the console. In the Assistant card, press **Edit**, choose the provider, paste the API key and press **Save key**.

Through the console, the page asks the **console password** once more before it keeps a key: a yellow box appears at the top of the window, "Type it, then save again". Type it, press **Save key** again: the list of models fills, the recommended one first with its price (`claude-sonnet-5 (recommended) · $2 in, $10 out`, about $0.09 a day). Choose it, press **Use this model**, then **Done** at the top of the page. The terminal goes on.

If you pressed Done before the key was kept, the terminal says "Nothing was chosen on the settings page" and setup goes on without a model: `lpa config` opens the same page again, when you want.
{% endstep %}

{% step %}

### The account, the funds, the key, the mandate

Steps 4 to 8 are your wallet's. This step follows Locker Vault; the two other ways are [below](#with-a-browser-extension-or-a-mobile-wallet). For each, the console lists **Ceremony with Locker Vault**: the page shows a QR for the phone to read with its camera, the card the phone must show, and the webcam of **your computer** reads the phone's answer. Hold the phone to your computer's webcam, lower it when the page says **Read: you can lower the phone**.

* **Your account**: the answer to how it signs (a yes to Locker Vault), then the Vault's sync QR, from Accounts, Extension Sync, Show the sync QR. Read in a few seconds.
* **Some funds**: USDC sent straight to the account on Hyperliquid, or USDC and a little ETH on Arbitrum One; setup waits for either and says what the daily pilot asks of the account. An account that already holds funds goes straight on: the same ceremony asks the password and the trading key, and the terminal says so.
* **Your password and the trading key**: a password of ten characters at least, typed twice in the SSH session, then the approval signed on the phone, and the service fee (skipped, and said, when this account authorized it before).
* **Your limits**, kept with a yes in the terminal.
* **The limits you sign**: the mandate, for the agent key's life, read row by row on the phone; then one question, whether the phone explained what "pilot" allows.

None of this needs the service unlocked: your wallet signs, the server keeps. The sealed key is only needed to sign orders for real.
{% endstep %}

{% step %}

### The daily pilot, in simulation first

The last step opens a simulation account of $1,000 and asks whether the service may play the daily pilot every day at the charter's time, saying what leaves the machine, what a day costs and what the account must hold:

```
Have the service play the daily pilot every day at 00:30 UTC (02:30 on this computer's clock), in simulation? [y/N] y
The service plays the daily pilot every day, on a simulation account of $1000: nothing of your real account moves.
Setup complete.
The daily pilot is scheduled in simulation: `lpa pilot status` says where it is, `lpa live` shows it think.
```

If today's time has already passed, the service plays today's day within the minute, in simulation, **locked as it is**: a simulation day signs nothing. Half a minute later `lpa pilot status` says it:

```
The daily pilot is scheduled in simulation: one day every day at 00:30 UTC (02:30 on this computer's clock), and the follow of what it holds every hour.
Last day played by the schedule: 2026-10-06 03:31 UTC, no-trade (No trade: 1 said none.).
Next day: 2026-10-07 00:30 UTC (02:30 on this computer's clock).
```

Each day plays the strategy the charter names, `ladder-long` until you put another in use: `lpa pilot strategy list` on the server says which, and [The strategies](https://doc.lockerprotocol.com/hyper-agentic-trader/strategies.md) says what the others do.

When you have seen it work, give the service the key and move the days to your real account:

```sh
lpa unlock
lpa pilot schedule --on --live
```

`lpa unlock` asks the key's password and hands it to the service, which keeps it for the agent's whole life, until `lpa lock` or a restart of the server. Live days need it: a locked service says so in `lpa pilot status` and tries the day again every fifteen minutes, four times.
{% endstep %}

{% step %}

### After a restart of the server

The service starts locked after every restart, since the key is never kept open on disk. Simulation days go on. For live days nothing is signed until you unlock it, and `lpa pilot status` says a day that could not start. Unlock it from the console, or in an SSH session:

```sh
lpa unlock
```

The clock then tries the day again at its next look if the charter's time has passed on this UTC date.
{% endstep %}
{% endstepper %}

## With a browser extension or a mobile wallet

The same steps, signed elsewhere. Choose the way at the account's step (a no to Locker Vault, then a yes to the one you want), or at once with `lpa setup --with browser` or `lpa setup --with mobile`.

* **Your browser extension** (MetaMask, Rabby) signs on the ceremony page, which the console carries to your own browser through the SSH tunnel: open it from the console's list, connect your extension there, and approve each request in it. The server holds no key and opens no browser.
* **Your mobile wallet** is reached by the server itself: its outbound connection to WalletConnect's relay (`relay.walletconnect.org`) carries the requests, end-to-end encrypted. The pairing QR is printed in the SSH terminal (*Scan this QR with your mobile wallet (it expires in five minutes)*) and shown on the ceremony page in the console; scan it once, then approve each request on the phone. The link lasts seven days, extended at each signature, and `lpa signer forget` closes it.

Either way, the account is proven first by one signature that moves nothing, checked on the server and sent nowhere, and a deposit is sent by your wallet, which the server reads back on Arbitrum before it says it went.

## Asking in plain words, from the console

The console of the service carries the session's assistant, so a question you would type in the terminal can be asked in the page instead. It answers as it happens: its reasoning, its text, each command it calls and what that command answered.

| What                         | How it behaves                                                                                                                                                                                                                                                                                 |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A question                   | 1 to 2000 characters. **One conversation at a time**: a second question while a turn is running is refused, never queued                                                                                                                                                                       |
| A question that does not end | it is stopped when its page is closed, when the application asks it to stop, and after ten minutes, with a sentence that says which. The call to the model under way is cancelled, no command starts once it is stopped, no order is sent nor asked, and the next question is answered at once |
| An order it proposes         | the page asks you, and waits **120 seconds**, the life of a quote. Your yes carries the console's password, checked on its own; past those seconds the order is refused as a stale quote, and a page closed while an order waits cancels it, with nothing placed                               |
| What it may say              | it names no command you could not type on that machine, says simulation where the older words said paper, and reads the simulation account while simulation mode is on                                                                                                                         |
| Who may use it               | only the console of the service, only a session signed in with the console's password, and only from the console's own page                                                                                                                                                                    |

Its state is on the page too: the conversation, whether a turn is running, what the day has spent on the model, the model itself, and the most steps a turn takes. A turn that stops on a refusal ends on that refusal, with its code and the way out.

## What "it worked" looks like

* `lpa status`, on the server, names your account, an agent with 179 days left, a mandate in force, the service running, and the key: locked in simulation, held by the service once you unlocked it for live.
* `lpa pilot status` says the daily pilot is scheduled, the last day played and the next day's hour in UTC.
* The console, from your computer, shows the service and the last activities.

## If something goes wrong

{% hint style="warning" %}

* *`command not found: lpa`* right after the installer: log out and back in, or `export PATH="$HOME/.lpa/bin:$PATH"`.
* *The console does not open*: the tunnel is not there, or its port is taken on your computer (`-L 7718:127.0.0.1:7717`, then `http://127.0.0.1:7718/`).
* *`Linger is off`*: run once `sudo loginctl enable-linger $USER`, or the service stops with your last SSH session.
* *`LOCKED`* after a restart: `lpa unlock`, or the console's Unlock card.
* *Save key answers nothing, or "Type the console password again"*: through the console, changing a key, the limits or the simulation mode takes the console password once more; type it in the yellow box, then save again.
* *The ceremony page will not read the Vault*: more light on the phone's screen, hold it still in front of your computer's webcam, raise its brightness. Lower it once the page says **Read**.
* *The terminal says the ceremony page was closed*: open it again from the console; the command waits.
  {% endhint %}

## Learn more

* [lpa service and lpa console](https://doc.lockerprotocol.com/hyper-agentic-trader/commands/service-and-console.md)
* [Set up in a few steps](https://doc.lockerprotocol.com/hyper-agentic-trader/set-up-in-steps.md)
* [Go live under the mandate](https://doc.lockerprotocol.com/hyper-agentic-trader/go-live.md)
* [The strategies](https://doc.lockerprotocol.com/hyper-agentic-trader/strategies.md)
