Runs: several at once, and leaving it unattended

The Runs page is where you put Klaudius to work. The way to get the most from it is to let it work on several businesses at once and leave it running.

Why several at once

A single conversation that works through business after business fills up its working memory and has to compress what it knows partway through a job, which can disrupt whatever it's doing. Run Klaudius avoids that: it runs a pool of sessions side by side, each taking one business from start to finish (find, build, deploy, pitch), and starts a new one every time one finishes. It all runs on your existing Claude or ChatGPT subscription, with no extra billing.

Starting a run

On the Runs page, set the number beside Run Klaudius to how many businesses to work on at once, then press Start. Under Where to work you can name a kind of business and a town; leave both empty and Klaudius picks the next town worth working. To work on just one business, use Run the pipeline: one full cycle, then it stops.

How many at once

• Start with ×2 or ×3. Three is the sweet spot for most operators: enough throughput that you're not babysitting, not so many that you burn through your usage limits.
• On the cheaper plans, start with ×2. That means Claude Pro, ChatGPT Plus, or a Standard seat on Claude Team or ChatGPT Business. Every session draws from the same allowance, and three at once will use up these plans' limits mid-run.
• The picker goes up to ×10. Each one is a full session, so more at once uses your plan faster.
• On a Linux computer with 4 GB of memory or less, there's no picker. Klaudius works on one business at a time, to leave the computer enough memory: start another run once the one going has finished. Daily follow-ups wait for it too.

Watching and stopping

Everything in flight is listed under Running now, with anything that finished in the last hour. Click any entry to watch it work. Older runs live in Conversations.

• To stop one business, open it and press Stop. The pool shrinks by one.
• To stop the whole run, open its Run Klaudius ×3 entry (or whatever number you chose) and press Stop. The sessions it started stop too.

Any business a stopped session was holding goes back into the pool for a later run.

When a run stops or pauses by itself

A pool keeps going until you stop it, with a few exceptions. When you reach your usage limit it pauses, says when it will resume, and carries on after the reset, so a run left going keeps working across resets. It also holds off while your internet connection is down, and stops if it isn't back within 2 hours. It stops after three failures in a row (a build error, unusable photos and so on), or when your Claude or ChatGPT sign-in runs out.

The pool's entry under Running now always says why. Troubleshooting says what to do in each case.

Leaving it unattended

Runs need the Klaudius app open, though not its window: close the window and Klaudius keeps working in the background. On Linux, closing the window quits Klaudius (it asks first if runs are going), so leave it open while it works. While work is in flight it keeps your computer awake (the screen can still turn off), but closing a laptop lid still puts it to sleep. On a Chromebook, ChromeOS's own power settings decide when it sleeps, even while runs are going.

Quitting the app stops every run, so Klaudius asks first. Runs don't pick up again on their own after a quit or a restart: start Run Klaudius again when you're back, or send a stopped conversation a message. Open Klaudius when I log in, in Settings, reopens the app after a restart so your daily follow-ups still happen, but doesn't restart a pool.

When an app update is ready while runs are going, choose Later: it installs the next time you quit (on Linux, see Updates). Restart now stops anything running first.

Replies are handled separately

A pool finds, builds and pitches. Checking for replies and drafting follow-ups is a separate job: press Start on Follow-ups, or have the app prepare them each day with Daily follow-ups.