Skip to main content

Workspace

One place for the documents that steer your agents: files, tracked changes, review, history, and the people and agents working in them.

A workspace holds files, chats, history, secrets, and connections. Files are collaborative documents: you, your teammates, Sundial Agent, and any connected agent edit the same live document, and every edit is attributed to whoever made it.

Workspace model

Files

Markdown is the first surface: a rich editor with a raw-source toggle, slash menu (headings, tables, callouts, math blocks, images), inline $…$ math, and [[wiki links]]. LaTeX is first-class too: the PDF compiles beside your source as you type, \cite autocompletes from your project's .bib files, SyncTeX jumps between source and PDF, and compile errors come with a “Fix with Sundial Agent” button. Code files open in a full code editor, CSVs open as editable tables, and images and PDFs preview inline.

Editing modes

Documents support editing, suggesting, and viewing. In suggest mode, changes render as tracked changes in the document: insertions and deletions you accept or reject one by one, or all at once. The chat composer has the same control, so you decide per chat whether an agent edits directly, suggests, or only reads.

Review and history

The Review panel batches pending changes across the whole workspace. Filter by file, folder, chat, author (you, Sundial Agent, a connected agent), or time, then work through the diffs in one pass. From any change you can hand back to chat: revise it, ask about it, or restore.

History is kept at edit granularity, not commit granularity. Compare any two points, open a past version read-only, and pin checkpoints to name the states you care about. Each agent turn also posts a diff card in the chat, so you can review from either side.

Multiplayer and comments

Workspaces are live: you see collaborators' cursors, and connected agents appear as ghost cursors while they work. Comments are threaded and anchored to text (Cmd+Option+M), in both the markdown and code editors. Commenters can suggest and discuss without being able to write final text.

i
Workspace instructions (“these instructions apply to every chat here”) live on the workspace settings tab. They're injected into the agent's system prompt on every turn. For instructions you want every connected agent to read as a file, keep an AGENTS.md at the workspace root instead.

GitHub

Connect GitHub through the Sundial GitHub App and link repositories per workspace. Clone, pull, commit, and push from the workspace, with commits authored as you. Write the plan next to the code it describes, and let the agent read both.

Overleaf and Google Docs

Bridges keep a workspace in sync with the tools your collaborators already use. An Overleaf project syncs two-way with a workspace folder; a Google Doc syncs two-way with a single markdown file. Conflicts pause the sync until a human resolves them.

Desktop and local folders

The desktop app (macOS) opens any folder on your machine as a project: plain files, same editor, same tracked changes, review, comments, and history. Everything stays on your machine until you explicitly share a file, folder, or project to the cloud. Starter packs scaffold a research paper, a literature review, a writing pipeline, a book.

Sharing and roles

Invite people by email as editor, commenter, or viewer, or make the workspace public with a link-level access of view, suggest, or edit. On a suggest link, every visitor's change arrives as a tracked change, the same way agent edits do.

Next steps