Quickstart for people

1. Choose the team and workspace

Sign in at app.agentgrid.io, select the correct team, then choose a workspace you can access. Teams own billing and membership; workspaces decide which people and agents can see the artifacts inside them.

Every team has General. Create an additional workspace when a project needs a different audience. See Workspace overview.

2. Create or import work

Use the app's creation flow and select the destination workspace. Current routes include a new Markdown document, file upload, folder or ZIP import, website URL import, Figma import, and Knowledge Base creation.

Folder and ZIP imports allow one folder or archive, up to 50 MiB and 1,000 files. Free teams receive five successful imports total across website URL and Figma imports. See Plans and usage.

3. Connect your AI

Browser chat assistants use the official AgentGrid.io connector or plug-in. Coding and autonomous agents can follow https://api.agentgrid.io/connect; the Anima CLI supports workspace discovery and selection.

Grant only the workspaces and capabilities the agent needs. A capability is permission to read, write, share, or publish. A reachable workspace is one the agent has permission to access. A connected agent creates directly there and does not need a claim step.

4. Edit and verify

Markdown edits autosave continuously. Watch the save indicator to see whether your edits reached AgentGrid.io or need a retry. Use Save or ⌘S when you want a named checkpoint in History. Use History to restore an unwanted saved result.

After creation or import, verify the artifact appears in the intended workspace and opens at the returned URL.

5. Share or publish

Use artifact Share for the artifact link and privacy controls. Manage people and the agent roster at team level; manage workspace grants from workspace access controls. Publishing is separate and creates a public URL.

If work seems missing

Check the selected team, then the workspace. An agent may be able to reach only some workspaces. Do not repeatedly retry an access denial; review Workspace access.

Questions and answers

Where will a new artifact be visible? In the selected workspace, to people and agents that have access there. Team membership alone is not enough.

How do I know an edit or import succeeded? Wait for the saved indicator when editing, and confirm a created or imported artifact opens in the intended workspace.

Can sharing a link make the artifact public? No. Share handles the private artifact link; publishing separately creates a public URL.

What should I check when work seems missing? Verify the active team and workspace, clear any relevant filters, and review workspace access instead of repeatedly retrying.

Human decisions required

Before creating, confirm the target team, workspace, source material, and whether the result should remain private or be published. Do not choose a workspace or make work public without the human's direction.

UI route

Instruct the human to sign in at app.agentgrid.io, select the correct team and a reachable workspace, then use the appropriate creation or import flow. A reachable workspace is one the current identity has permission to access. The human must verify the result in that workspace.

Agent route

1. Read https://api.agentgrid.io/connect.
2. Authenticate by the documented route.
3. Discover reachable workspaces; do not assume General or another default.
4. Use the selected workspace ID for creation or import when supported.
5. Return the artifact URL and verify it can be read in the intended scope.

The CLI's anima workspaces lists reachable workspaces and capabilities. A capability is permission for an agent action such as read, write, share, or publish. anima create --workspace <id> selects a destination. If the agent can create in more than one workspace, a workspace is required because there is no default.

Current limits

Folder and ZIP import accepts one folder or .zip, up to 50 MiB and 1,000 files. Free URL and Figma imports share five successful imports total. Quota and authorization refusals are terminal for that attempt; relay the upgrade or access path rather than retrying.

Saving and collaboration

Markdown autosaves continuously. Explicit Save or ⌘S creates a history checkpoint. If synchronization is interrupted, preserve the content, wait for reconnect/retry, and use History to recover an unwanted saved result.

Access boundaries

Team role, workspace grant, agent capability, and steward permission all apply. Team membership alone does not expose every workspace. Artifact Share controls links and privacy; it does not administer team members, workspace grants, or agents.

Never publish without an explicit human request.

Questions and answers

Which decisions must come from the human? The target team and workspace, source material, and whether the result stays private or is published.

How should destination scope be selected? Discover reachable workspaces and use the chosen workspace ID. When more than one is writable, never assume a default.

What counts as successful creation or import? Return the artifact URL and verify the artifact can be read in the intended workspace.

Which failures should not be retried? Authorization and quota refusals are terminal until a human changes access or plan state.