Skip to main content
This guide connects the coding agents on one computer to Little Spaces with a single prompt, then checks that an answer from you reaches a session. You approve once, and it takes a few minutes.

​
Before you start

  • Access to Little Spaces. It is in early access, and access is by invitation. You sign in with GitHub.
  • A Mac or Linux computer with a coding agent that runs shell commands, such as Claude Code, Codex, Cursor or Gemini CLI.
  • curl, and sha256sum or shasum, to download the client and check it.
You don’t need Node.js installed. If the computer has no Node.js 22.12 or later, setup downloads the official release, checks it, and keeps a private copy for the hooks. It never uses sudo and never changes the system’s Node.js.

​
Connect your agents

1

Sign in

Open littlespaces.dev and choose Continue with GitHub. Little Spaces opens on your inbox.
2

Copy the prompt

In the sidebar, open Agents. Under Connect your agents, copy the prompt.The prompt names no app, so it works in any coding agent that runs shell commands. The Works with table below it lists the agents setup connects, what works in each, and any one-time step. If you would rather run the command yourself, open Or run the command yourself and copy it from there.
3

Paste it into an agent

Paste the prompt into a session of any coding agent on the computer. The agent runs one command, which:
  1. downloads the Little Spaces client and its installer to a temporary folder;
  2. checks their checksums, and moves them into ~/.local/share/little-spaces/ only once both pass;
  3. runs setup, which signs in, finds the agents on the computer and installs their hooks.
Each step runs only if the one before succeeded. Setup waits up to 10 minutes for your approval.
4

Approve the connection

The agent shows you a link and an eight-letter code. Open the link, check that the page shows the same code, and choose Allow.The approval page names the apps setup will connect on this computer, and says that they send no prompts, code or transcripts. Allowing is your consent to install them, so the agent doesn’t ask you again. The agent’s name defaults to “Hooks on” and the computer’s name; you can change it.
Codes expire after ten minutes. If yours has expired, ask the agent to run the prompt again.
5

Read the summary

Setup prints a line for each app: connected, and what works, or not connected, and why. It then lists any one-time step, such as Codex asking once to trust new hooks.If setup could tell which session it is, the session you pasted the prompt into now shows under Runs on its project’s page in Activity, and the test question below arrives. If not, the summary says so: start a new session of a connected app, and it shows under Runs. On the Agents page, the new agent’s card changes from “Waiting for its first session” to “Working”, with when its first session arrived.
6

Answer the test question

When setup connects the session you pasted the prompt into, that session raises a test question: “Little Spaces is connected. This is a test question: reply here to check that your answers reach this session.” It appears in your inbox under Waiting on you, and holds up no work. If setup told you to start a new session instead, ask the new session to raise a test question in Little Spaces.Pick an option or write anything, and choose Send. The session tells you when your reply arrives:
  • Claude Code is woken by a reply that comes within 15 minutes of the session’s last turn.
  • Other apps get the reply with your next message to the session.

​
What happens next

From now on, every session of a fully connected agent on that computer reports by itself. Each session shows under Runs, is told at its start how to report milestones and raise asks, and gets your answers back. Setup’s summary says what works for each app. If it says an app is connected only in part, its line names what is missing, and only that part doesn’t work. You don’t need a config file, token or checkout. To connect another computer, paste the prompt into an agent there too. Each computer gets its own sign-in, named “Hooks on” and that computer’s name.

Answering asks

How your answers reach a session, and what each delivery state means.

Troubleshooting

What to do when a session doesn’t show under Runs, or setup stops.