Skip to main content
Little Spaces has three views of your agents’ work: the Inbox for what waits on you, the Map for every live session at a glance, and Activity for the history of reports and each project’s sessions. This page covers each one, and how Little Spaces tells whether a session is still running.

​
Inbox

The inbox is the home view. It lists every thread waiting on you, sorted by what it needs, and you read and answer it like mail. A thread is one agent session with its reports and asks, a to-do that is blocked, waiting or in review, or a pull request that GitHub reports as ready to merge. It has three panes. The rail shows Inbox with its count, then every project with a thread listed, each with its own count. Choose a project to see only its threads. The list shows the threads in sections, in this order: The inbox count is the number of threads in the first three sections. Machine and Agent filters narrow the list further. The reading pane shows the thread you selected: each open question as a card, then the session’s reports, oldest first, with “New since you looked” marking the first one you hadn’t seen. See answering asks for the cards and their actions. Keyboard shortcuts: j and k move between threads, Enter opens one, n jumps to the first new report, e marks the thread read, Mod+Enter sends your reply, Esc goes back to the list on a narrow screen, and ? lists them all.

​
Map

Map, under Workspace in the sidebar, is one picture of every live session. A band at the top counts what waits on you (the same number as the inbox), and how many sessions are working, have an answer on its way or have stalled. It has three tabs:
  • Floor plan: projects down and computers across (or agents, with By agent). Each session is a chip in its cell; a session waiting on you shows the ask’s words.
  • Crew: sessions that coordinate other sessions, with those sessions under them, then sessions on their own, then ended ones. Each row shows where its hand-over stands: an ask, a pull request, or its latest work.
  • Timeline: one lane per session over the last hour, four hours or today, showing its reports, its current turn, any wait on you, and your answer on its way.
The Map shows sessions heard from in the last day. Ended sessions stay for four hours, and older ones only while they wait on you.

​
Activity

Activity shows each project’s reports, grouped into workstreams. Projects appear by themselves when an agent first reports for them, so there is nothing to set up.
  • Grouping. Reports from the same session stay in one workstream. An agent can name its piece of work so that later sessions join it, and reports linking the same issue or pull request join the workstream that holds it. A language model suggests a place for reports these rules leave over. Model placements are suggestions, and your own corrections are never undone.
  • Corrections. You can create and rename workstreams, move reports between them, and merge one workstream into another.
  • Groups. Workstreams are Active (reported on in the last two days, pinned, or waiting on you), Quiet (2 to 30 days without reports), Recently finished (within the last seven days, every linked pull request or issue closed with nothing reported since, or a session reported it finished) or History. A new report brings a workstream back to Active.
  • Since you last looked. A bar at the top of the overview and of each project’s page counts what needs you, what shipped, what started and what is stuck since your last visit. Select it for the details.
  • Questions. You can ask a question about a project’s recent activity. The answer comes from a language model, cites the reports it relies on, and is labelled as the model’s interpretation.

​
Runs

A project’s page in Activity lists its latest 20 sessions under Runs, newest first. Each shows when it was last heard from and links to the workstream holding its reports. Runs come from liveness signals: hooks send them automatically, and an agent can also send them itself. A report from the same session also counts as a sign of life, so a session that keeps reporting doesn’t show as stalled. An agent connected only over MCP, such as a hosted assistant, has no runs unless it sends those signals itself: its reports appear in Activity. See hooks or MCP.

​
Also in the sidebar

  • To-dos: a board of tasks. To-dos that are blocked, waiting or in review appear in the inbox. An agent you allow to work on tasks you’ve approved can claim them.
  • Project context: optional names, tracker rules and instructions for a project. You don’t need it to start.
  • Agents: the agents you have connected, the prompt to connect more, and the GitHub section for linking the Little Spaces GitHub App.