Install and connect

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

Install the CLI, start Gimmer, and open your private link on a computer or phone. No desktop or display server required.

1. Install the CLI

On the computer or server that will run Gimmer, use the command for your system. No administrator access needed.

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. Your processor is detected automatically.

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

These commands download and execute an installer. You can review the shell or PowerShell script first, or use direct downloads. The installer verifies SHA-256 and does not start the server or any bots.

After installing, open a new terminal.

2. Run Gimmer

gimmer-cli start

If this installation has no accounts yet, Gimmer starts the server and prints your invitation URL automatically. No Mobile commands or CLI login needed.

Keep this terminal open. The server stays available after pairing or after the invitation expires.

Already have an account on this host? No new invitation is created automatically. Use another-device setup if needed. Previously running bots may resume according to their saved state; review it before starting. Do not run Desktop and the CLI against the same database together.

3. Open your link

Copy the URL from your terminal. It is a plain link, not a JSON object. Open it in a browser on your other computer or phone, complete pairing, then create, restore, or sign in to your account.

Keep the link private. Invitations are single-use and expire within 5 minutes. Need a new one? Open another-device setup below. Pairing does not bypass account authentication.

No router port forwarding or public inbound firewall rule is needed. Both devices need internet access; Mobile uses outbound HTTPS/WSS on port 443.

More options and help

Connect another device or replace an expired link

Keep Gimmer running. Open a second terminal on the same host, or a second SSH session, and run:

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

This also works with an existing account or after Mobile setup fails. No local account login is needed to create an invitation. Change Work laptop to your device's name; automatic first-run invitations use My computer.

Copy the new URL. Connection updates appear separately. Add --json only when a script needs invitation metadata. Expiry affects the invitation, not a device already paired.

--yes confirms the requested action, not a login. Stopping Mobile access and revoking a paired device still require account authentication.

Create an account in the terminal

Prefer not to use the browser? Keep the server running and open a second terminal:

gimmer-cli --yes auth register

Enter your username and password when prompted. Store the wallet recovery words securely, then paste the full phrase when the CLI asks you to confirm it. Registration signs you in. Never put passwords or recovery words in commands, shared logs, chats, or support tickets.

Keep Gimmer running on a server

Closing its terminal or SSH session can stop it. For unattended operation, configure an operating-system service under the same dedicated user and data directory. Keep one runtime per database, prevent sleep, and maintain internet access.

To start without automatic invitations, use gimmer-cli server start. Running gimmer-cli without arguments or gimmer-cli --help only shows help; neither starts a server.

Check runtime activity after reconnecting. A connected browser does not prove that every bot or exchange order is healthy.

Update or fix a connection problem

Situation	Next step
Update the CLI	Review running bots and pending orders, stop the server, rerun the installer, then restart. Account data is preserved.
Command not found	Open a new terminal. Check the installation path printed by the installer.
No URL, or an expired link	Use another-device setup in a second terminal.
`start` is not recognized	Update to Gimmer CLI v3.0.442 or later using the installer above. Stop the running server before updating, then reopen your terminal.
Browser cannot connect	Keep the server running and check outbound HTTPS/WSS on port 443 on both devices.
Database is locked	Close the other Gimmer runtime using that database, whether Desktop or another server.

For more commands, use gimmer-cli --help or gimmer-cli mobile --help. Remove invitations, wallet material, and credentials from shared diagnostics.