§ 02 · Studio

# For everyone
on the team.

Studio is the room inside Grove where non-coders join the AI workflow. Upload assets. Edit project memory. Review artifacts as they land. Sketch ideas the agents can read. No terminal. No git. Still shipping.

$ install grove → Next: Anywhere →
FIG. 01 Studio — the room where non-coders meet the AI team.
§ 01 RESOURCES

## Give the agents
everything they need.

Drop in assets, wire up shared files, and let the AI team work with the same inputs you do. Studio tracks artifacts as they're produced and renders them inline — diagrams, previews, images, all without leaving Grove.

Shared Assets

### Upload once. Every agent sees it.

Drag files into Studio's asset manager. They sync across worktrees via hard links so every task has immediate access, without duplicating storage.

- Full file manager — upload, organize, rename, delete
- Artifact sync — agent outputs surface here automatically
- Cross-platform links (junctions on Windows, symlinks on Unix)

FIG. 02 Assets live where everyone can see them.
Inline

### D2 diagrams

D2 files render inline with a source/preview toggle. Draw architecture, get diagrams.

Inline

### Mermaid

Mermaid fenced code blocks render as interactive diagrams in preview and chat.

Inline

### SVG & images

PNG, JPG, WEBP, GIF, SVG — all preview inline. Click for fullscreen lightbox with scroll-zoom.

Live

### Artifact refresh

While an agent is busy, the artifact preview panel auto-refreshes. Watch the output appear.

§ 02 MEMORY

## What the agent
remembers, you control.

Project Memory and Workspace Instructions are the context your agents read at every turn. In Studio they're first-class editable panels, not hidden markdown files. No CLI required.

FIG. 03 Edit once. Every agent, smarter.
Editors

### Markdown, made humane.

Split view, preview mode, auto-save on navigation. The kind of editor a product manager or a designer can open without googling markdown syntax.

- Project Memory — per-project context the agent reads every turn
- Workspace Instructions — global preferences across all projects
- Edit / preview toggle, auto-save, no "save button" ritual
- Merges into Studio so memory, assets, and artifacts live together

§ 03 SKETCH

## Draw it.
The agent reads it.

Grove ships a first-class Excalidraw panel. Every sketch is stored in the task's workdir, synced across clients in real time, and exposed to agents through dedicated MCP tools. Show the agent what you mean.

Excalidraw integration

### A canvas per task.

Open a Sketch panel in FlexLayout like any other. Create multiple named sketches per task, right-click tabs to rename or delete, draw on a real Excalidraw surface.

- First-class panel in FlexLayout — drag, split, maximize
- Multi-client live updates over WebSocket
- Per-task storage under the task workdir — versioned alongside code
- Lazy-loaded bundle — zero cost if you never open one

FIG. 04 Draw the flow on Monday. Ship it on Tuesday.

### MCP tools agents see

reference

### `grove_sketch_read_me`

One-time format reference. The agent calls this once per conversation to learn element syntax and the Grove pseudo-elements.

read

### `grove_sketch_list`

List every sketch in the current Studio task with created/updated timestamps.

read

### `grove_sketch_read`

Read a sketch by name — returns a rendered image (when fresh), element summary, and a fresh checkpoint_id.

write

### `grove_sketch_draw`

Create or modify a sketch. Checkpoint-driven — one tool handles both, with `restoreCheckpoint` pseudo-elements for incremental edits.

## You don't need to know git.
You can still ship.

Grove's bet: the next decade of software is built by teams where not everyone codes. Studio is how Grove keeps the door open.