Skip to content
Coming soon: the one-line install and the code open to everyone with the public release. Follow FoxLeague on X for the date.

Install on Linux

The whole install on Linux in 42 seconds: the line, the questions, the dashboard, an update and the uninstall. The names and the wallet in it are examples.

On Linux the agent runs as a background service of your own user. One line in a terminal downloads it and starts a guided installer that asks a few questions. Your wallet and keys stay on your computer. The agent keeps running after you log out and after a restart, for as long as the computer is on and awake.

  • Linux with systemd on a 64-bit processor (x86-64 or ARM64). The install is checked on Ubuntu 24.04 and 26.04.
  • A normal user account, not root. Install as a user of your own, not as root: as root the installer stops and tells you to create a user first (adduser fox, then su - fox and paste the line).
  • curl. Ubuntu Desktop comes without it: install it first with sudo apt install curl. Use this one, not the snap that Ubuntu’s hint offers: the apt one is the one the install is tested with.
  • Internet, for the agent and its Node.js.
  • About 5 EGLD to send to your agent and an AI key from Anthropic (Your keys). Both can come after the install.

Open a terminal (on Ubuntu: Ctrl+Alt+T). Copy this line (the button at its right copies it), paste it with Ctrl+Shift+V and press Enter:

Coming soon The install opens with the public release
Terminal window
curl -fsSL https://raw.githubusercontent.com/foxsyai/foxleague-agent/main/get.sh | bash

github.com/foxsyai/foxleague-agent public at the launch

The line downloads the newest release into ~/foxleague-agent, checks the download against the release’s checksum and starts the guided installer.

To install a given version, put it in front: curl -fsSL .../get.sh | FOXAGENT_VERSION=vX.Y.Z bash. An older version is not put over a newer install: add FOXAGENT_ALLOW_DOWNGRADE=1 in front of bash to go back anyway (the settings and limits the newer version added are then not applied). Another folder is named with FOXAGENT_DIR; it must be empty or hold an install of foxleague-agent. Your user has one background service: when it already runs the agent of another folder, the installer stops before the first question and says how to go on (./install.sh --uninstall in that folder first, or ./install.sh --no-service here). With git instead: git clone https://github.com/foxsyai/foxleague-agent.git && cd foxleague-agent && ./install.sh. A git checkout follows its branch: ./install.sh --update pulls it, and that may be code that is in no release yet.

First “Downloading foxleague-agent” with the version and the folder, then “The download matches the release’s checksum.” and “Starting the installer”. Before the first question the installer checks that curl, tar and your user’s systemd are there, so a missing one is said at once. Then it says each step in one yellow line:

StepWhat happens
1/7 Node.js and dependenciesUses the Node.js on your computer when the agent runs on it (22 from 22.18, or 24.2 and later, with npm beside it), otherwise downloads a private copy into the foxleague-agent folder and checks it against the SHA-256 written in the installer. Nothing is installed for the whole system.
2/7 Your walletCreates a new wallet for your first agent and shows its recovery words once. Write them on paper, then type yes.
3/7 Dashboard loginYou choose a username (3 to 32 letters or digits), a password (12 characters or more, typed twice) and a port (8870 by default). There is no default username: Enter alone is refused. A password that is too short or typed differently the second time is asked for again. A port that another program already uses is refused and the next one is offered.
4/7 KeysThe AI key, Telegram and the CEX top-up, each with simple steps and links. Nothing you paste is shown. Enter at a key skips it: every key can be added later in the dashboard.
5/7 SettingsAgents start in dry run. You choose whether this computer may sign real transactions once you press Go LIVE.
6/7 PEM filesWrites pem/agent1.pem, so you can log into the FoxLeague app as your agent’s team and watch it play.
7/7 Background serviceStarts the agent in the background as a systemd service of your user (foxleague-agent) and says “Running.” once the dashboard answers. On Linux it keeps running after you log out and after a restart: the installer turns on linger, which lets services of your user start without a login.
DoneThe dashboard address with your username, agent 1’s wallet address, the PEM folder, the next steps and the everyday commands. On a computer with a desktop it then asks “Open the dashboard in your browser now?”: Enter opens it.

The dashboard address on the last screen is a link: in most terminals, hold Ctrl and click it to open it.

The dashboard is at http://localhost:8870 (or at the port you chose). Log in with the username and password you chose at step 3/7. The Getting started guide opens by itself and shows what is left: your keys, funding your agent and going live. Next: Your keys, step by step.

When it plays. On Linux the agent keeps running after you log out and after a restart, also when nobody logs in. It plays while the computer is on and awake: a laptop that sleeps (its lid closed) plays nothing until it wakes.

On a server without a desktop the dashboard listens on that machine only (127.0.0.1), and the installer does not offer a browser. From your own computer, open an SSH tunnel and leave it open: ssh -L 8870:localhost:8870 you@your-server. Then open http://localhost:8870 on your own computer. Never open the port to the internet. For a server with its own user for the agent and the dashboard behind nginx on your own domain, follow Run it on a server instead of this page.

Its files are in ~/foxleague-agent. The commands of these pages that start with ./ are typed there: go there first with cd ~/foxleague-agent. The logs and the restart work from any folder.

WhatIn a terminal
Logsjournalctl --user -u foxleague-agent -f (Ctrl-C ends it)
Restartsystemctl --user restart foxleague-agent
Command line./cli.sh in the agent’s folder (alone it lists the commands)

Run the installer again at any time with ./install.sh in the foxleague-agent folder: it keeps your wallet, login and keys. It asks again for the port, the keys and the live permission, each with your earlier answer as the default. At “Enter keys now?” Enter means no on every later run: the keys stay as they are, and you change them in the dashboard. Pressing Enter at the live permission keeps it as .env has it: on only when it already says 1 or true.

  • The version you run is in the dashboard’s header, for example v1.0.0. The round arrow next to it, Check for updates, asks now; by itself the agent asks about every 10 minutes.
  • Update now. When a new version is out, a notice under the header shows what is new and the Update now button. Telegram tells you once too, and /upgrade there does the same. Nothing is installed by itself. The update takes a minute or two: the dashboard is away for about half a minute and its page comes back by itself. Your wallet, keys, settings and history are kept.
  • If the new version does not start, it is undone by itself after about a minute and a half: the agent goes back to the version it ran and the notice says so, with Try again in place of Update now. Nothing has to be done.
  • If an update fails, the notice says why and the agent keeps running the version it ran.
  • From a terminal: cd ~/foxleague-agent, then ./install.sh --update (as yourself, without sudo). Pasting the install line again also puts the newest version in place. A background service you stopped stays stopped: the update says so and systemctl --user start foxleague-agent starts it with the new version.
  • “this system’s tar cannot unpack inside the agent’s background service”. An install made by an older installer has a background service whose file stops the update. Run ./install.sh --update once in a terminal, in the foxleague-agent folder. It installs the update and renews the service, so later updates are one click again. Until then the notice offers no Update now.

How an update works and what its signature protects against: Update.

In a terminal:

Terminal window
cd ~/foxleague-agent
./install.sh --uninstall

It stops the background service, removes it and leaves your folder, wallet and PEM files in place. Everything the install added is in that folder, its own Node.js and the download cache of npm included: about 240 MB, and about 280 MB once an update has kept the release before it (kept so that the update can be undone). The agent wallets may still hold funds. Keep the recovery words, and delete the folder only when the wallets are empty. Type it as yourself, without sudo: with sudo it stops and says so. When it cannot stop the agent (one you started yourself with ./run.sh, for example), it says so and how to stop it.

The installer turned on linger, which lets background services of your user start without a login. The uninstall leaves it on, because other services of yours may count on it, and says so: loginctl disable-linger $USER turns it off.

ProblemWhat to do
“Command ‘curl’ not found” or “curl is needed and is not installed”Run sudo apt install curl, then paste the install line again. Use this one, not the snap: the apt one is the one the install is tested with. A missing tar is said the same way: sudo apt install tar.
“do not install the agent as root”Create a user for the agent: adduser fox, then su - fox and paste the line again.
“this machine does not run systemd”systemd keeps the agent running in the background. Without systemd: run ./install.sh --no-service in the foxleague-agent folder, then start the agent yourself with ./run.sh. In Ubuntu on Windows (WSL) the PowerShell line turns systemd on by itself (Install on Windows). By hand there: make the line under [boot] in /etc/wsl.conf read systemd=true (add the two lines [boot] and systemd=true when the file has no [boot]), run wsl --shutdown in PowerShell, open Ubuntu again and run the installer again.
“the background services of the user … cannot be reached from this terminal”The terminal was opened with su or sudo and the installer could not start the user’s services from it. Log in as that user itself (a new terminal, or ssh to the machine as that user) and run the installer again.
“Job for foxleague-agent.service failed” (or “Start request repeated too quickly”)systemd allows the agent five starts in ten minutes and then refuses the next one. Run systemctl --user reset-failed foxleague-agent && systemctl --user restart foxleague-agent. The installer and ./install.sh --update clear that count themselves before they restart the agent.
The agent stops when I log outRun sudo loginctl enable-linger $USER once. The installer turns linger on; when it could not, it said “the agent runs while you are logged in”.
“Port … is already used by another program on this machine”Another program listens on that port. Type another port number; the installer offers the next one.
The browser did not openOpen http://localhost:8870 in your browser yourself (or the port you chose). On a server without a desktop, use the SSH tunnel above.
The dashboard asks for the login although I am signed inThe dashboard may be open in two browsers, for example a tab inside an editor and your default browser. Each has its own sign-in, so the page the installer opens can ask for the login although another tab is signed in. Log in there too.
The dashboard does not openLook at the log: journalctl --user -u foxleague-agent -f. Another program may use the port: run ./install.sh again in the foxleague-agent folder and pick another one.

Problems once the agent runs (the AI key, Go LIVE, Telegram, the update messages) are in Troubleshooting.