Skip to main content
You can answer an agent’s question or approval in the Little Spaces inbox, or in the agent’s own session, and either way the ask closes in Little Spaces. Review and merge asks close through GitHub, or when you resolve them or the agent withdraws them. This page covers both, how an answer travels back to the session, and how GitHub closes review and merge asks by itself.

​
Answer in Little Spaces

Open the thread in the inbox. Each open question is a card, such as “Question 1 of 3”, with the ask, any “Stopped” or “Holds up” line, and the agent’s recommendation.
  • A question: pick one of its options (the one the agent recommends is marked Recommended), or choose Other… and write your own answer. A question without options has an answer box.
  • An approval: choose Approve or Decline.
  • Skip: sets one question aside without answering it. The agent is told not to wait on it.
  • A review or merge ask: its card links its pull requests and has Resolve. It can’t be skipped or set aside.
Your picks across all the cards, and any words for the whole session, go back in one Send, all or nothing. Questions you leave alone stay open, unless you skip them or tick Set aside the N unanswered, which sets them aside in the same reply. An answer, with your words, can be at most 2,000 characters. Other actions on a thread:
  • Mark read (e): done without answering. It sets aside every question and approval still waiting, so the agent is told not to wait, and offers Undo for a few seconds. Review and merge asks stay open.
  • Archive: hides the thread until the agent writes again.
  • Looks good: tells the agent you saw its latest report, with no reply needed. It is offered only when nothing in the thread waits on you.

​
Follow your answer to the session

After you send, the line under your answer says where it is:

​
How the answer gets there

Each app’s hooks bring answers to the session in the way the app allows. The supported agents page lists the route for each app. In short:
  • Woken when idle. Claude Code’s hooks wake a session that has ended its turn, when your answer comes within 15 minutes of the turn’s end. Pi’s and OpenCode v2’s plugins are built to wake an idle session with an answer that comes up to two hours after its turn ended, but this hasn’t yet been seen working in a real session.
  • At the end of a turn. In apps such as Codex, Cursor and Gemini CLI, the hook that runs at the end of a turn waits a few minutes (five by default) while a question or approval is open, and continues the turn when your answer arrives.
  • With your next message. In apps whose hooks see your messages, an answer not yet delivered is added to your next message to the session.
  • When the agent checks. Agents without hooks that hand over answers, and agents connected only over MCP, fetch answers themselves when they next run or check.
An answer is handed to a session once. Until the agent acknowledges it, it may be shown again, marked as already delivered.

​
Answer in the session

An agent connected through hooks is told to state each ask in full in its reply to you: the question, the options, its recommendation, what it holds up and any links. So you can answer in the session itself. When you do, the agent acts on your answer and reports it to Little Spaces. A question or approval closes there at once (review and merge asks don’t close this way), marked “answered in the session”, with your reply in one line under it and the app it was answered in. This is the agent’s account of your reply, not an answer from you in Little Spaces, and it grants nothing beyond what you said. If you answer in both places, the first to arrive wins. Once the agent reports you answered in the session, the inbox refuses a second answer to that ask. In apps whose hooks see your messages, each message you send reminds the session of its questions and approvals still open, so it can tell whether your message answers one.

​
When an agent waits without asking

Sometimes an agent ends its turn with a message that waits on you, such as “Shall I merge it?”, without raising an ask, so the inbox would show nothing. In Claude Code and Codex, the hooks catch this:
  1. Nudge. The first time, the hook asks the agent once to report the ask properly, or to reply that it isn’t waiting on you.
  2. Fall back. If the session stops that way again with still no ask, it shows in your inbox as waiting for you (“Stopped waiting for you”) until its next signal or report.
The check runs on your computer. Nothing from the agent’s message is sent to Little Spaces.

​
GitHub closes review and merge asks

When you link the Little Spaces GitHub App from the GitHub section of the Agents page, Little Spaces follows the state of the issues and pull requests that reports link to:
  • A review or merge ask closes once every pull request it names is merged or closed, and comes back if one reopens.
  • A question or approval about a pull request that has since merged or closed says so on its card, and moves to No longer waiting once all its pull requests have.
  • Pull requests that GitHub reports as ready to merge appear in your inbox under Waiting on you, unless an agent’s ask already covers them.
  • Pull request events, such as pushes, merges and failed checks, appear in the workstream that links the pull request, labelled “From GitHub”.
The GitHub App is read-only, and each link covers only the repositories your own GitHub account can access.