Docs
Troubleshooting
Most problems come down to a computer that is offline, an agent that is not signed in, or a device waiting for approval. Here is how to tell which, and what to do.
The computer is offline
When the app shows a computer as Offline, its daemon is not connected to the relay. A computer that sleeps is offline until it wakes. On the computer, ask the service:
$ slashcode service status| It says | Do |
|---|---|
Running (pid …). | The daemon runs: see below. |
Not installed. | slashcode service install |
Installed but not loaded | Run slashcode service install again. |
Loaded but not running | Read the end of the log it names; see Logs below. |
slashcode service is macOS only. On Linux, check that slashcode daemon still runs where you started it. Commands that need the daemon say so when it is not running: the daemon is not running (no …/control.sock); start it with `slashcode daemon`.
If the daemon runs and the computer still shows offline, check the computer's network, then the end of its log: the daemon reconnects on its own, waiting at most 30 seconds between tries.
An agent is not signed in
A harness signed in to nothing can do nothing. The app marks it Not signed in when you start a session, and a session that hits it says so. Either way the app offers to sign it in, on the computer, from your device:
- Through a link. The computer starts the harness's own sign-in and passes you the page to open, Open sign-in page, sometimes with a code to confirm there, or a field to paste one back.
- With an API key. You type it once; it is kept on that computer for that harness alone and never comes back to a device.
A harness that offers neither says it can only be signed in from a terminal on the computer. A sign-in left without a step for 10 minutes closes; start it again.
If a harness shows not installed in slashcode agents though you installed it, see harnesses: the service needs reinstalling from a shell that finds it.
A device waits for approval
A phone or browser that only signed in to your account sees none of your computers until a trusted device or the computer lets it in. On a device you already use, answer Allow in Allow a new device?, or find it in Settings › Devices. On the computer:
$ slashcode devices3f9a0c… Safari on Mac web waiting for approval$ slashcode devices approve 3f9a0c…
With no trusted device at hand, pair this one with a code instead: a device paired with a code is trusted at once. See why devices wait.
Pairing fails
| Message | What it means |
|---|---|
| Code expired / Code expired or unknown | The 15 minutes are up, the code was used, or it was mistyped. Run slashcode pair again. |
| Code burned after 5 failed attempts | Five wrong tries closed it. Run slashcode pair again. |
| Codes are 8 letters and digits | What was typed is not a pairing code: check it against the terminal. |
| This computer is paired to another account | A computer has one account. Remove it from the other account's Settings › Computers first. |
| Free pairs one computer. Go Pro to add up to three. | Your plan's computers are all paired. See plans. |
| Can't reach the relay | The device is not connected to the relay: check its network. |
| Your computer did not answer | The daemon did not reply in time: check that it runs. |
A session won't start
- Your plan runs 2 sessions at once means this computer keeps as many sessions as your plan allows, idle ones included. Delete one, or see how limits apply.
- New branch… with the name of a branch that exists is refused: pick it under A branch instead.
- A branch that is neither local nor on
originfinds nothing: check its name, and that it was pushed. See its own copy.
Pull requests and issues stay empty
The git panel reads GitHub through gh on the computer, on the repository's origin. When gh is missing or not signed in, the panel says what to do. On the computer:
$ gh auth status$ gh auth login
The same goes for failed-CI notifications: without a working gh, they stay silent.
Logs
The daemon writes its log to ~/.slashcode/logs/daemon.log. It never grows past 10 MB: halfway, the file becomes daemon.log.1 and a new one starts, so the two together stay under 10 MB.
$ tail -n 50 ~/.slashcode/logs/daemon.logOn macOS, what the service prints before that log opens lands in ~/.slashcode/daemon.log. The apps keep their own log the same way, capped at 10 MB, and send it only with a report.
Report a problem
Shake your iPhone or iPad, or open Settings › Report a problem in the app or the web app. Say what went wrong and what you were doing; you need to be signed in.
Include the app's log is on by default: it attaches the end of the app's log, which lists connections and requests with their timings, and errors, which can quote a command's output. The report also says which device it came from. Your conversations are never sent.
We read every report; the answer shows up in the app under Settings › Your reports.
Automatic error reports
When something breaks on its own, a crash or an internal error, each computer sends it to Slashcode with the end of its log, secrets masked. Never anything from a conversation. A computer holds a few while the relay is away, and the relay files at most 20 an hour from each; a repeat of the same error counts instead of adding another.
$ slashcode incidents offError reports are off. `slashcode incidents on` sends this machine's errors and crashes to Slashcode.
The switch applies at once, without a restart. The apps have their own: Send error reports in Settings.