Skip to main content

Saggar documentation

Saggar keeps projects, sessions, and coding agents organized around one question: which session needs me right now?

Choose a path

Supporting promises

Knowing which session needs you is the central promise. These supporting promises connect the rest of Saggar to the work you want to do.

PromiseHow Saggar supports it
Show the agent what you meanImage annotations and file attachments on the initial task give the agent concrete context.
See what you're working withFile previews and links into your editor, plus image-placeholder previews, let you inspect what a session refers to.
Act when the thought occursQueued prompts, quick runs, and the command palette let you capture the next instruction or run a command while work continues.
Keep your place as work growsProject organization, monitors, session previews, and restoration keep the workspace together; attention cards bring decisions to you.
Stay involved away from the deskCompanion inspection and remote responses let you check in from your phone with the access you approve on the Mac. The Mac must be awake, online, and running Saggar.

Find an answer

The one question

A test can fail, a long command can finish, or an agent can wait on a permission prompt. The expensive part is usually not the wait but failing to notice. Saggar classifies each session, folds away what can wait, and builds one queue from everything that needs a decision.

The docs use the same vocabulary as the app: a project is a codebase, a session is one managed terminal session, and triage is the walk through sessions with a claim on you. Start with Status and triage when that vocabulary is new.