FAQ

Getting started

How do I get started?

Follow the Quick Start — it walks you from registration through a launched bot in about five minutes.

What does Pitchfork actually do?

It's a control plane: account storage, agent orchestration, client launching, script scheduling, ban tracking, and bulk operations. It does not replace your bot client — you still bring DreamBot, RuneLite, etc. Pitchfork manages how and when those clients run.

Does Pitchfork run on Windows / macOS / Linux?

The web UI runs in any modern browser. The agent (the small binary that connects to Pitchfork and launches your clients) runs on Windows, macOS, and Linux. You'll need a JRE installed (8 for most clients, 11 for RuneLite-based clients) and Google Chrome installed for any features that drive browser flows.

Do I need a server, or does it run locally?

Pitchfork itself is a hosted SaaS — there's no server to run. You register at getpitchfork.com, and you only run agent binaries locally on the machines that should host bot clients.

Accounts

How do I import accounts?

Three options: paste them as login:password lines (with optional OTP, PIN, group, and proxy fields), upload JSON for Jagex Launcher accounts, or POST to /api/accounts/import. Full reference: Importing.

My accounts show as "stopped" but I just launched them — what gives?

Most likely the agent hasn't reported status back yet. Check the Agents page — the agent should show as "Connected" with a recent last-heartbeat. If it's offline, restart the agent binary.

How do I move an account between groups?

Multi-select on the Accounts page → Move to Group. Programmatic: PATCH /api/accounts/{id} with the new group_id. Automated: a move_to_group trigger action.

What's a "group" for?

A bag of accounts you want to act on together — for filtering in the UI, scoping triggers, batch tool runs, and continuous-launch loops. Accounts can belong to one group at a time.

Agents

My agent won't connect.

Walk through:

1. The agent prints its WebSocket target on startup — make sure that's the URL of your Pitchfork instance.
2. Check the Agents page in Pitchfork — does the agent appear at all? If yes, it's connecting but failing handshake (usually a stale agent token; recreate the agent in the UI).
3. If it doesn't appear, your firewall or NAT may be blocking outbound WebSocket. Try from a different network.
4. Logs: see the Agent TUI doc for filtering by service.

Can I run multiple agents on the same machine?

Yes, but they each need a unique agent name and their own ports for the clients they launch. There's no benefit to doing this unless you're isolating different client types — one agent can run dozens of clients in parallel.

How do I stop an agent without killing in-flight scripts?

Currently, no graceful drain. Stop bots first (UI multi-select → Stop, or a stop_bot trigger), wait for them to wind down, then quit the agent.

Clients and scripts

Which client should I use?

DreamBot has the deepest Pitchfork integration. If you're starting fresh and don't have a strong preference, use DreamBot. See Client Support for the full status table.

How do I launch a script?

Accounts page → select account(s) → Launch Script → pick the script, agent, and client. See Quick Start step 6.

Can I pass arguments to my script?

Yes. The format depends on the client — DreamBot expects param=value pairs space-separated; RuneLite-based clients use whatever flags your fork accepts. Set them under Script Activities so they apply automatically every launch.

Bans and safety

Will Pitchfork itself get my account banned?

Pitchfork doesn't interact with the OSRS game client or Jagex's anti-cheat — it only orchestrates the bot client you choose. Ban risk comes from the script and client you run, not from Pitchfork. That said, sloppy operational hygiene (same proxy on hundreds of accounts, identical break patterns, no membership rotation) is detectable independent of the client.

Does Pitchfork detect bans automatically?

Yes — ban detection rolls up from the client wrapper. When a ban event fires, Pitchfork records it on the account, fires any account_banned triggers, and (if deleteAccountOnBan is set on the DreamBot client config) optionally removes the account.

Should I use a proxy?

If you're running more than a few accounts from one IP, yes. Proxies are configured per-account or per-group. Pitchfork passes them to the client automatically.

Triggers and automation

How fast do triggers fire?

Event triggers (ban, status change) fire near-instantly. Metadata triggers (level, wealth, runtime) check on a polling cadence — expect up to a few minutes of latency.

Can a trigger fire only once?

Use a one_time trigger for a specific instant. For a recurring trigger that should only fire once per account per condition, the trigger system tracks executions in trigger_execution_history; combine with a condition that mutes after firing (e.g. move_to_group to a group the trigger doesn't watch).

Can I write my own automation logic outside the trigger system?

Yes — use the webhook trigger action to POST to your own service, or skip triggers entirely and call the Public API from a cron job.

Billing and policy

How much does it cost?

Nothing right now. Pitchfork is in open beta and free for everyone — no paywall, no trial limits, no credit card. Paid tiers will be introduced when we leave beta; existing users will get advance notice and a transition path.

Will I have to pay later?

Probably yes, eventually — Pitchfork takes real infrastructure to run. But not during the beta. You'll know well before any pricing change.

Do you store my OSRS credentials in plaintext?

No. Credentials and 2FA secrets are encrypted at rest. They're decrypted in-memory only when the agent needs them to launch a client.

Still stuck?

Join Discord and ask in #support — both the team and the community hang out there.