Skip to content

Guide

Multi-Agent OSRS Farm Management Guide for Teams

Distribute OSRS account operations across connected Windows and Linux agents with clear capacity limits and centralized account visibility.

Understand the Kovex agent model

A Kovex agent connects a machine to your dashboard so you can launch and control supported clients. Account records stay available through Kovex, while each connected agent provides its own operating capacity. This makes the agent the practical unit for planning concurrent workloads.

Free permits one concurrent agent, Standard permits two, and Premium permits unlimited concurrent agents. These limits describe connected agents, not the number of accounts stored in account management. Compare all included features at /pricing before expanding to additional machines.

Calculate capacity per agent

Automation concurrency is configured per agent. If two agents each have a maximum concurrency of 12, the combined operating capacity is 24 accounts. The limit is not a single shared pool of 12 across both machines.

Plan each agent according to the accounts and workflows assigned to it. Adding a second Standard agent can increase total capacity because both agents retain separate concurrency settings. Premium removes the concurrent agent limit when an operation requires more connected machines.

Set up Windows and Linux machines

For Windows, download Kovex.exe from Agent Setup and paste the displayed agent key into the application. The key is shown once. Repeat the documented setup for each machine that will run an agent. Linux installation guidance is available at /docs.

Windows supports RuneLite, DreamBot, TRiBot, InuBot, EpicBot, Detuks, and TwiLite. Linux supports RuneLite and DreamBot. New profiles default to TwiLite, so confirm the intended client when planning a mixed operating system environment. See /guides/runelite-twilite-dreambot-with-kovex for client guidance.

Coordinate automation stages

Standard and Premium plans can use automation rules built from a source category, configured stages, and a completion category. This keeps the account lifecycle explicit as work moves from its starting group to its completed destination.

Concurrency should be selected alongside the rule design. A well-defined completion category makes finished accounts easy to distinguish from accounts still moving through stages. For a focused example, read /guides/osrs-automation-rules-tutorial-island.

Monitor your own running accounts

The Free tracker supports account oversight. Standard and Premium add the live feed, where you can review running accounts, levels, quest points, GP, and screenshots. The /live page displays your own bots rather than a network-wide view.

Use /guides/osrs-proxy-and-live-telemetry for proxy and visibility planning. Review /docs for setup details and /pricing for agent limits, creation allowances, and plan cadence. When ready, sign in with Discord at /auth/login.