Workspace
How a Sundial workspace maps one text thread to shared files, history, runtime, and review links.
A workspace is the durable home for one iMessage/RCS thread. Sunny reads the thread, edits workspace files, and sends a diff link back whenever the file state changes.
Workspace model
Each workspace has chats, files, tasks, history, secrets, connected apps, and runtime state. Files are stored as collaborative documents so Sunny and humans can work in the same document.
Files and history
The file tree shows user-facing files first and de-emphasizes heavy or generated folders. The History tab and document rail show time-bucketed edits, authorship, and reviewable chunks.
Editing modes
Documents support editing, suggesting, and viewing modes. Suggested edits stay reviewable before they become final document text.
Runtime and local agent
The Connect local agent flow lets a local Sundial MCP process join the workspace. Cloud turns run through the sandbox runtime and keep the workspace document store synchronized.
# Project Context
Keep user-visible notes concise.
Prefer editing workspace files over dumping long drafts into chat.
When code changes, link the relevant files and summarize the diff.AGENTS.md remains the workspace instruction file. It is user-editable and is read by the runtime when Sunny works in the workspace.GitHub
Connect GitHub from the GitHub tab to import a repository. Sundial clones it into the sandbox, materializes text files into the workspace document store, and exposes pull, commit, and push controls backed by the same runtime path Sunny uses.