Troubleshooting

The machine is awake, an issue is queued, and nothing starts.

1. 1Look at the runner's chip in the top bar, or the This machine card at the foot of the sidebar. Runner off means the switch is off: turn it on there. Only an action on the machine itself does.
2. 2Holding new runs means the runner is on and something holds new runs; the chip's tooltip and the This machine sheet say what. It can be your schedule, Leave room for me at your reserve line, a usage limit until it resets, Pause while I share my screen, or Start new runs only on power.
3. 3A queued run that would start while you are away waits until you are back. See Work while nobody is at the machine.
4. 4Start now, on a held run in Runs, starts it at once, past every hold but the runner switch.
5. 5Runner not set up means the machine was never set up: press Set up on the This machine card. It takes about two minutes.

In the dashboard preview, a machine in this state shows as engine paused, and the project's Overview says the engine is stopped.

Runs work only while the desktop app is open and the computer is awake. In the dashboard preview, a machine that has not checked in for about 90 seconds shows as asleep, and the Overview lists it as machine offline.

1. 1Wake the computer and open Splitterm on it.
2. 2Check it is signed in to the same account, in Settings > Account.
3. 3Check its runner is on, on the This machine card.

To keep a machine available, turn on Open Splitterm at login in Settings > General, and Keep this PC awake while running in the This machine sheet. With the runner on, closing the window keeps Splitterm in the tray.

Runs use your own Claude Code and its sign-in, so they share its usage limits with everything else you do in Claude Code. Once a limit is reached, Claude stops working until it resets.

1. 1Check the usage chip in the top bar. It shows once your runs have reported your limits; click it to see each limit, how much is used and when it resets.
2. 2New runs wait for the reset by themselves, and the This machine sheet says when they start.
3. 3Or sign Claude Code on that computer in to another Claude account. That is done in Claude Code itself, not in Splitterm.

Leave room for me, in the This machine sheet, keeps a share of each window free for you, and At once caps how many runs work together, which spreads usage out.

A project needs the Splitterm GitHub App to receive pull requests and check results in the dashboard.

1. 1Open the project's Settings and find GitHub.
2. 2If the controls are disabled, ask a project owner: only owners can connect.
3. 3Press Connect GitHub and, on GitHub, pick the repositories the project works on.
4. 4You land back on the project's settings, connected.

Signing in with GitHub does not connect repositories; it is only a login. If Settings says the Splitterm GitHub App is not registered yet, nothing is wrong with your project or account: the connection is not available yet.

On the desktop, an approved run opens its pull request with the GitHub CLI signed in on that machine, which does not need the App.

An agent has stopped to ask a question or for permission, or its plan waits for your approval. Its run stays where it is until you answer.

1. 1Find it: the bell in the top bar counts what waits in Needs you. A terminal of yours where Claude Code waits is counted on the sidebar's Terminals entry.
2. 2Open it from Needs you, or open the issue: the question is in its sheet, and in Runs. For a terminal, click its row in the sidebar, or press Ctrl+Shift+P, type @ and its name.
3. 3Answer there. The run goes on with the same issue.

Desktop notifications for this are on by default and fire while the Splitterm window is not focused. Change them in Settings > Notifications. Quiet hours, in the This machine sheet, hold them; Needs you keeps everything.

An issue sits in In progress and nothing seems to happen. Open its run in Runs and read its Activity first. The usual causes:

It waits on you

See An agent is waiting on a question.

It is held

A held or queued run says why on its row. See The runner is off or holding runs.

Claude hit a usage limit

See Claude usage limit reached.

It needs a hand

The run stopped on a problem it could not get past, and its sheet says what. Retry it, or stop it.

To recover:

1. 1While it works, send it a message from Runs. It arrives at its next step.
2. 2Take over to work with it in a terminal of yours, then hand it back.
3. 3To abandon the attempt, Stop it. Its branch and worktree stay, and the issue can run again later.

When Runs says the runner keeps stopping, press Restart the runner. Runs are kept safe on disk.