Contact Sales

Braiins Manager Agent - Management

Overview

Agent management differs based on the version you are using:

  • Agent v4.0.0+ includes a built-in Graphical User Interface (GUI) for convenient configuration and control directly from the desktop.
  • Agent v3.x is managed via the command line using PM2 process manager commands.

Refer to the appropriate section below based on your installed agent version.

Agent Management

Update Agent ID & Secret Key

If you need to reassign the agent to a different location or reconfigure its credentials.

Stop Agent Service

Use the State toggle in the GUI to temporarily stop the agent. You can reactivate it later using the same switch. Activation and deactivation are persistent. Make sure to reactivate the agent when needed.

Disable Autostart

Toggle Autostart off in the GUI to prevent the agent from starting automatically on system boot. For a good experience, we do not recommend disabling it.

Download Logs

Click the Download Logs button in the GUI to export a ZIP archive containing the agent's logs for diagnostic purposes.

Agent Auto-Update

If a newer version of the agent is available, the GUI will notify you. Click the Update button to download and apply the latest version.

See more in the Upgrade & Uninstallation Guide.

Commands Concurrency

Starting with Agent v4.3.0, you can fine-tune how many commands are processed in parallel to optimize speed and stability.

What is Concurrency?

Concurrency controls how many commands the agent executes simultaneously. Adjusting these values helps balance:

  • Fast execution (higher concurrency)
  • Gradual execution (lower concurrency), useful for staged resumes or reducing power spikes

Default Values

pause_concurrency: 250     # For pause commands
resume_concurrency: 50     # For resume commands
concurrency: 250           # For all other commands

These defaults work well for up to 5,000 miners in typical environments.

Configuring Concurrency

To customize, edit the agent's daemon.yml config file and add the commands section:

commands:
  pause_concurrency: 250
  resume_concurrency: 50
  concurrency: 250

Estimate Execution Time

Where:

  • N = number of miners
  • k = concurrency
  • X = average execution time (ms)
  • T = estimated total duration (seconds)

Example: For 5,000 miners, 1s per command, and resume_concurrency = 50:

Or calculate needed concurrency

If you want to determine the concurrency required to complete execution within a target time T:

Quick Reference

ConcurrencyExecution Time (5,000 miners @ 1s)
50100 s
10050 s
25020 s
50010 s
10005 s

Best Practices

  • Stick with defaults unless specific use cases require tuning.
  • Lower resume_concurrency for smoother, but slower, startup.

Was this helpful?