xBot Docs

Quickstart

Start with the recommended cloud worker or run a self-hosted xBot worker.

Trading needs a worker attached to the same Steam account as the Market Bot. Choose where it runs:

Cloud — recommendedSelf-hosted
Where it runsOn xBot infrastructureOn your Windows, Linux, or macOS machine
ProxyChosen during setup and hosted by xBotConfigured and maintained by you
Steam secretsStored in xBotStay on your machine
MaintenanceNoneYou run the process and replace the binary

Cloud worker — recommended

Recommended option

Choose a cloud worker unless you specifically need Steam credentials to stay on your own machine. There is no software to download, computer to keep online, or outbound proxy to configure manually.

What you need

  • A Steam account already added to xBot.
  • That account's Steam password, shared_secret, and identity_secret, or its .maFile.
  • A dedicated proxy: buy one in the chosen location or use one already added to xBot.

Start it

Create the worker

Open Workers → Add worker, choose the cloud type, and select the Steam account.

Choose the proxy

Buy a new dedicated proxy in the intended location or attach one you already have. xBot hosts the worker together with this proxy.

Add Steam credentials

Enter the password, shared_secret, and identity_secret. The two Steam Guard secrets can be imported from a .maFile instead of copied manually.

Confirm creation

Review the displayed price, create the worker, and enable it in the Workers list. Then create a Market Bot for the same Steam account.

Steam credentials and the selected proxy can be changed later from the Workers list.

Self-hosted worker

This option runs the worker from a regular folder on your machine. The launcher detects the operating system and architecture; when the matching binary is absent, it downloads the latest build and verifies its SHA-256. It never updates a binary that is already present.

What you need

  • Windows 10/11 or a current Linux/macOS system on amd64 or arm64.
  • A Steam account already added to xBot.
  • That account's Steam password, shared_secret, and identity_secret.
  • The API key of an xBot self-hosted worker.
  • Outbound HTTPS access to dl.xbot.gg, xBot, and Steam. No inbound port or public address is needed.

The launcher contains secrets

Once filled in, the file holds the Steam password, Steam Guard secrets, and the API key. Do not send it to anyone, commit it to Git, or leave the folder readable by other users.

1. Create a self-hosted worker

Open Workers → Add worker, choose Self-hosted, and select the Steam account. In the Workers list, use the regenerate-key action and save the key shown there immediately: the previous key stops working as soon as a new one is issued.

2. Download the launcher

Windows

Open Command Prompt in the folder where the worker will run:

mkdir xbot-worker
cd xbot-worker
curl.exe --fail --location --remote-name https://dl.xbot.gg/quickstart/start-worker.bat
notepad start-worker.bat

start-worker.bat uses the built-in reg, curl.exe, and certutil tools. It supports Windows amd64 and arm64 and remains a regular batch file.

Linux and macOS

mkdir -p xbot-worker
cd xbot-worker
curl --fail --location --remote-name https://dl.xbot.gg/quickstart/start-worker.sh
chmod 700 start-worker.sh

The launcher needs curl or wget to download files and either sha256sum or shasum to verify SHA-256.

3. Fill in the settings

Open the downloaded file and replace the values in its USER CONFIGURATION block:

VariableValue
XBOT_USERNAMESteam login exactly as the account is registered in xBot.
XBOT_PASSWORDSteam password.
XBOT_SHARED_SECRETBase64 shared_secret value from the .maFile.
XBOT_IDENTITY_SECRETBase64 identity_secret value from the .maFile.
XBOT_API_KEYAPI key of the self-hosted worker you created.
XBOT_PROXYOptional proxy for all Steam traffic.
XBOT_BACKEND_PROXYOptional proxy only for xBot and job downloads.

Proxy schemes may be http://, https://, socks5://, or socks5h://, optionally with user:password@host. An empty value means a direct connection. The worker ignores the system HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY variables; a configured proxy that fails never falls back to a direct connection.

Escaping rules are written next to the variables in both launchers. The .sh file uses single-quoted values; in the .bat file every literal % must be written as %%.

4. Run the worker

Windows:

start-worker.bat

Linux or macOS:

./start-worker.sh

The launcher derives the exact binary name, such as xbot-worker-linux-arm64. When that file is not next to the launcher, it:

  1. downloads the binary from worker/latest/ into a temporary file;
  2. downloads SHA256SUMS;
  3. verifies SHA-256;
  4. only then makes the binary executable and places it beside the launcher.

When the binary already exists, the launcher performs no download and never replaces it. To move to the latest version manually, stop the worker, delete the local binary, and run the launcher again.

On first run, the worker validates the configuration, signs into Steam, and connects to xBot. A successful Steam sign-in is logged as Steam login verified. Keep the process window open: the launcher starts the worker once and is not a background service or supervisor.

Troubleshooting

CodeMeaningAction
0Clean stopNone.
1Temporary Steam, network, or xBot failureCheck connectivity and proxies, then run it again.
10Steam rejected the credentialsCheck the login, password, and both Steam Guard secrets.
11xBot rejected the API keyRegenerate the key and replace XBOT_API_KEY.
12Invalid configurationFix the variable named in the error.
75The binary was replaced by built-in updatingQuickstart does not enable updates; if seen, run the file again.

If the expected binary name is unavailable or its download/hash check fails, the launcher exits before execution. Check access to https://dl.xbot.gg, free disk space, and the system clock.

Where state is stored

The Steam session, pending result journal, and status.json live under the user's configuration directory in xbot-worker-go/<Steam login>. Do not publish this directory. Removing the binary does not remove the saved Steam session.

Next

On this page