Skip to main content
Most Little Spaces problems show up in one of three places: signing in, a session that doesn’t appear under Runs, or an answer that doesn’t reach a session. Find the symptom below. Commands are written as spaces <command>; see running it.

​
Signing in and setup

Little Spaces is in early access, and access is by invitation. If your GitHub account hasn’t been given access yet, sign-in is refused and no account is created.
Codes expire after ten minutes. Check the code, or ask the agent to run the Agents page prompt again for a new one. Setup itself waits up to 10 minutes for your approval, so give the agent’s command a long timeout or let it run in the background.
The command checks the download with sha256sum or shasum. If neither is installed, it stops with “Install sha256sum or shasum to check the download.” and runs nothing.
Without Node.js 22.12 or later, setup downloads the official release for macOS or Linux, on x64 or arm64. On any other system, install Node.js 22.12 or later yourself. The official Linux builds need glibc, so on Alpine Linux, install Node.js yourself too.
A stored sign-in installs only the apps its approval named. When setup finds a new app on the computer, it says so (“this login is not yet approved to connect Cursor”, for example) and asks for a new approval that names every app it will install. Choose Same agent reconnecting on the approval page to keep the same agent. If you decline, nothing new is installed and the apps already connected carry on.
Setup installs only for OpenCode v2. For OpenCode v1, or a version it can’t tell, it installs nothing and says only OpenCode v2 is supported.
Setup still connects every agent it found. For the one it doesn’t know, it points to spaces connect --help, a guide the agent can follow to connect itself, in its own user-level files, after showing you the change.

​
A session doesn’t show under Runs

Some apps load new hooks only when a session starts. Setup’s summary names the one-time step for each app, such as starting a new session or running /reload in Pi. See supported agents for each app’s step.
Codex asks once to trust new or changed hooks. Approve them when it does, or Codex sessions won’t show under Runs. Don’t bypass the check.A Codex without lifecycle hooks is connected through its notify setting instead. Its sessions then show under Runs from finished turns only, and aren’t told how to report or given your answers. If your config.toml already runs a notify program of your own, setup leaves it as it is, says Codex is not set up, and prints the line to add to your program.
Devin loads no hooks in Restricted Mode, so its sessions show under Runs only outside it. Cline runs hooks only while its Enable Hooks setting is on, under Feature Settings.
These apps have no automatic hooks. Their instructions tell each session to start a run, report and fetch your answers, so a session shows under Runs only once it has followed them. Its reports still appear in Activity.
That’s expected. Runs come from liveness signals, which hooks send automatically. An agent connected over MCP shows its reports in Activity, and appears under Runs only if it sends its own liveness signals (signal_run).
Stalled means no signal or report for more than two hours, without the session ending. A session still marked Waiting for you stays waiting instead, until you dismiss the wait. A session that closed without its app reporting the end, or that sits idle, stalls this way.

​
Reports and the sign-in

Run spaces whoami. It shows the server, the agent identity and its permissions, which credential is in use, and any signals still waiting to be sent.
Reports and signals are saved on your computer before they are sent, and ones that couldn’t be delivered wait there. Later hooks retry waiting signals; run spaces flush to send waiting reports and signals now. Don’t send a report again with a new ID.
A sign-in renews by itself, but if it goes 30 days without renewing, or you disconnected the agent, it needs a new one. Run spaces login, or paste the Agents page prompt again. Signals queued meanwhile are kept and sent once you sign in again as the same agent.
Nothing updates by itself in the background. Run spaces update to bring the client and the installed hooks up to date. It doesn’t sign in again.

​
Answers

The session is in the middle of a turn. It gets the answer when the turn ends.
The session hasn’t fetched it yet. Depending on the app, it arrives at the end of a turn or with your next message to the session; see how the answer gets there. An agent without hooks gets it only when it next checks.
The session ended before it fetched your answer. A session resumed with the same run can still fetch it.
A plugin tried to wake the session with your answer, and Little Spaces can’t tell whether it arrived. Ask the agent to check, or choose Deliver again, accepting that it may see the answer twice.
An ask can be answered only while it is open. If the agent replaced, retired or withdrew it, or reported that you answered it in the session, or you resolved it, the inbox refuses the answer and says why.

​
Removing Little Spaces

Run spaces uninstall to remove what the installer wrote, for every app, or spaces uninstall --app ID for one. Add --dry-run to see what it would remove first, and --logout to sign out too. It never changes a file with nothing of Little Spaces’ in it, and leaves its backups in place without copying them back.