Skip to main content

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, 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.

i
Workspace instructions (“these instructions apply to every chat here”) live on the workspace settings tab. They’re stored on the project itself and injected directly into Sunny’s system prompt on every turn — no file in the tree, no round-trip through the doc store.

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.

Next steps

Assistants
Sunny identity, models, and thread routing.
Security
Secrets, sandboxing, and review boundaries.