> features / productivity

Projects: Backlog, Context and Session

Every project with its backlog, its context, its files, its own Claude Code session and its servers, next to your terminals.

The Projects tool lists the user's projects in groups, each with its icon, color, figures (open, in progress, in review, blocked, specialists, its session) and a progress bar. A search box finds projects by name, group or the text of their backlog. A click opens the project in a tab, one per project. Its menu has Open, Edit, Access, Set Remote Hosts, Browse (the folder of its session), New Project Here and Delete.

The tab has the project on the left and, on the right, the pane chosen with the buttons of its header. The header shows its icon, name and progress, then Repository (the folder its session and its agents work in), Supervisor, Specialists (the agents with tasks in it) and Remote (its hosts). The buttons are Context, Assets, Session, Supervisor and Remote, those that apply.

Context is the markdown of the project (notes.md), edited in place, with Preview; agents and sessions read it. Assets are its files. Session is a Claude Code session of its own, in its repository, with its Extended Prompt; it keeps its conversation, and the Session button beats green while it works or waits for an answer. Supervisor is the chat with its supervisor and its instructions. Remote is an SSH session of the project on one of its hosts.

Under the header is the backlog. A task can be sent to the session of the project (Prompt ▸ Session) and becomes the user's; from then on the comments the user writes on it, and moving it out of Working or Review, reach the session as prompts (their wording is in Settings, Session). Deleting a project archives its folder.

What it does

  • Grouped projects with figures and progress bars; search across names and backlogs.
  • Header: repository, supervisor, specialists, remote hosts.
  • Panes: Context (markdown), Assets, Session (Claude Code), Supervisor, Remote.
  • A Claude Code session per project, told of the user's comments and moves.
  • Backlog with states, priorities, groups, categories, sort and archive (see Tasks).

How it behaves

  • Context is saved a second after the last change; a change made outside (by an agent) shows at once.

Why it matters

  • Keep the backlog of a deployment next to the servers it touches, and an AI session that knows it.