Create a new doc

New Doc creates an empty markdown artifact and opens it in the editor. It exists from that moment, so there is no save-and-name step to forget.

Steps

::: lanes

In the app

1. Open the team you want it in. Whatever you create lands in your current team.
2. Select New in the top right.
3. Select New Doc.
4. Start typing. The editor is a full rich-text editor: headings, bold and italics, lists, checklists, tables, links, code, colors, and alignment, all from the toolbar.
5. Keep writing while changes autosave. Use Save or ⌘S when you want an explicit History checkpoint.

The artifact is titled Untitled until you rename it. See Rename and duplicate.

Ask your AI assistant

Create a doc in AgentGrid.io called "Launch plan" with sections for positioning, pricing, and sequencing.

:::

Limits

• The document is stored as markdown. The editor's rich formatting maps to markdown, so anything beyond what markdown expresses will not survive.
• If agents also edit this doc's raw markdown, know that the editor may normalize the whole file. Structural conventions like YAML frontmatter can be reformatted by an editor session, so keep anything load-bearing in the body. See Edit a markdown artifact.

Questions and answers

Can I start from a template? Not yet. Duplicating an existing artifact is the closest thing today.

Can my agent write into a doc I created? Yes, if it is connected with write and has access to the workspace. To connect a new agent, follow Invite an agent; then grant only the needed workspace access.

Can I undo? The editor has undo, and History lets you compare or restore recorded changes. See Version history.

Do I have to select Save after every change? No. Editing autosaves continuously. Save or ⌘S creates an explicit History checkpoint.

New Doc immediately creates and opens an empty markdown artifact. There is no separate save-and-name creation step.

Prerequisite

The human must switch to the intended team before creating the document. New artifacts always enter the current team.

How should a human create a document?

This procedure is UI-only; instruct the human to:

1. Open the destination team.
2. Select New at top right.
3. Select New Doc.
4. Write with the rich editor. Its toolbar supports headings, bold, italics, lists, checklists, tables, links, code, colors, and alignment.
5. Continue while edits autosave. Use Save or ⌘S only when an explicit History checkpoint is wanted.

The initial title is Untitled until renamed. See Rename and duplicate.

A connected AI with write access can instead be asked: Create a doc in AgentGrid.io called "Launch plan" with sections for positioning, pricing, and sequencing.

Storage and editing constraints

• The document is markdown. Rich formatting maps to markdown, and unsupported formatting does not survive.
• The editor may normalize the complete markdown file. If agents edit raw markdown too, YAML frontmatter can be reformatted. Keep load-bearing machine structure in the visible body, not frontmatter. See Edit a markdown artifact.
• Templates are not available yet. Duplicating an existing artifact is the current substitute.
• A connected agent can write to the document if it has write and workspace access. To connect another agent, direct the human to Invite an agent, then Workspace access.
• Editor undo handles immediate changes. Recorded versions can be compared or restored through Version history.

Save invariant: ordinary persistence is continuous; Save or ⌘S requests an explicit checkpoint.

Questions and answers

What result does New Doc create? An empty markdown artifact in the current team, initially titled Untitled.

What access does an agent need to edit it? The agent needs write capability and access to the document’s workspace.

How is persistence verified? Use the save indicator for continuous autosave. Save or ⌘S creates a named History checkpoint.

What is the current template workaround? Duplicate an existing artifact; document templates are not available yet.