Run Gimmer on a server. Use it in your browser.

1. Install the CLI

Run the matching command on the host that will run Gimmer, as your regular user. The installer needs no administrator access, checks the official release asset's SHA-256 digest, and installs the command as gimmer-cli. It does not start the server or any bots.

Windows x64

Open PowerShell:

irm https://gimmer.com/install/cli.ps1 | iex

Ubuntu / Linux x86_64

Open a terminal. Linux ARM is not currently supported.

curl -fsSL https://gimmer.com/install/cli.sh | bash

macOS, Apple silicon or Intel

Open Terminal. The installer detects your processor and selects the native macOS CLI build.

curl -fsSL https://gimmer.com/install/cli.sh | bash

These commands download and execute an installer. You can read the shell script or read the PowerShell script first. For direct downloads, including separate Apple silicon and Intel files, use the CLI download section.

Open a new terminal after installation so the updated command path is available, then check:

gimmer-cli --help

2. Start the headless server

In your first terminal, run:

gimmer-cli server start

Leave this terminal running. The CLI does not open a Wails window, load GTK, or require a display server. Do not run the desktop app and the headless server against the same account database at the same time.

3. Create your Mobile access URL

Open a second terminal on the same host, or a second SSH session to it. You do not need to sign in to a Gimmer account to enable Mobile access and create an invitation locally.

gimmer-cli --yes mobile start
gimmer-cli --yes mobile invite --name "Work laptop" --watch

1. Copy the URL. Find the url field in the invitation output. Keep this link private: it contains a one-time pairing secret.
2. Open it on the other device. Use its browser. Mobile access also works from another Windows computer or Mac; it is not restricted to phones.
3. Complete pairing. Follow the browser's pairing steps and complete any approval shown. The --watch command reports connection updates in your terminal.
4. Sign in in the browser. Create, restore, or sign in to your Gimmer account there. Pairing a device does not bypass account authentication.

Invitations are single-use and expire within 5 minutes. If the link expires, run the invitation command again and use the new URL. A paired device is separate from its expired invitation.

Mobile connects through outbound HTTPS/WSS on port 443. You do not need to expose Gimmer's local API, forward a router port, or add a public inbound firewall rule. The host and browser still need internet access; this is not an offline connection.

--yes acknowledges command confirmations for this action. It does not disable authentication or remove account and trading protections. Stopping Mobile access and revoking a paired device still require account authentication.

Optional: create an account in the terminal

You can create your account through the paired browser instead. If you prefer the terminal, run:

gimmer-cli --yes auth register

Follow the prompts for your username and password. Store the wallet recovery words securely, then paste the full phrase when the CLI asks you to confirm it. Registration signs you in when completed. Never paste a password or recovery phrase into a shell command, shared terminal log, chat, or support ticket.

Keep your host available

The foreground server must stay running for Mobile access and bot execution. Closing its terminal or SSH session can stop it. For unattended operation, have your server administrator configure an operating-system service under the same dedicated user and data directory. Do not launch a second server against the same database.

Prevent sleep, keep outbound connectivity available, and check runtime activity after reconnecting. A connected browser is not evidence that every bot or exchange order is healthy.

Update or troubleshoot

For the commands available in your installed version, use gimmer-cli --help and gimmer-cli mobile --help. Redact invitations, wallet material, and credentials before sharing diagnostic output.