FAQ

Questions and answers

The topic groups below answer common questions about using AgentGrid.io.

Getting started and plans

What is the fastest way to start? Connect the AI you already use. Browser assistants use their official connector or plug-in; an agent with a shell can run npx @animaapp/cli@latest login. See How agents connect.

What does AgentGrid.io cost? You can start on Free without a card. Paid plans are Lite, Pro, and Business. Billing is per team and agents do not consume seats. See Plans and usage and the live pricing page.

How many URL or Figma imports are free? A Free team gets five successful imports total across both methods, not five of each. Deleting an import does not return it to the allowance. See Limits and quotas.

Teams, workspaces, and private access

What is the difference between a team and a workspace? A team contains members, workspaces, one billing plan, and one agent list. A workspace is a place inside the team that contains artifacts and has its own access list. See Workspace overview.

Can everyone on a team see every artifact? No. Visibility follows workspace access. A person or agent sees artifacts only in reachable workspaces.

Does an artifact link grant access? No. It identifies the artifact. The signed-in account or connected agent must also have workspace access. See Request access to a private artifact.

Where do I add people or agents? Use team management for the team roster, which is the list of members. Use workspace access controls for workspace grants; each grant gives access to one workspace. Use agent administration for invitations, accountability, capabilities, and revocation. A capability allows an agent action such as read or write. Do not use the artifact Share panel as a team or agent roster. See Team management, Workspace access, and Invite an agent.

Can an artifact move between workspaces? Use the artifact move workflow when you have the required source and destination permissions. Moving between workspaces is different from duplicating between teams. See Rename, move, and duplicate.

Artifacts and editing

Do I have to save every Markdown edit? No. Markdown edits autosave continuously. The save indicator reports the current state. Save or Command-S creates an explicit history checkpoint; it is not required for routine persistence. See Edit a Markdown artifact.

Can several people edit at once? Yes. Live collaboration shows presence and remote selections where available. If a reconnect or conflict produces an unwanted saved result, use History to inspect and restore.

Can I undo a saved change? Yes. Open History, preview an earlier version, and restore it. The restore creates a new history entry.

Are folder and ZIP imports supported? Yes. Import one folder or .zip, up to 50 MiB and 1,000 files. Include source and assets; omit dependencies and build output. See Import a folder or ZIP.

Why is an imported app blank? It may be missing an entry point, such as index.html, or may have been imported as the wrong artifact type. Markdown imports need .md files. Correct the source and create a new import.

Are URL and Figma imports synchronized with their source? No. Each creates an editable AgentGrid artifact; later source changes are not pulled automatically.

Sharing and publishing

What is the difference between sharing and publishing? Sharing controls access to an artifact inside AgentGrid.io. Publishing creates a public URL. Publication is explicit and can expose content to anyone on the internet. See Share an artifact and Publish to a public URL.

Can Markdown be published? Yes. Publishing supports Markdown as documented on the publish page.

How do I update or unpublish a site? Publish the current artifact state to update it, or unpublish to take the public site offline without deleting the artifact. Agents need publish and must act only after an explicit human request.

Agents and CLI

Does connecting an agent give it my password or consume a seat? No. It gets a separate identity, never receives your password, and does not consume a seat.

What determines what an agent can see? Its workspace grants, capabilities, and the current permissions of the person or team accountable for it. A personal agent is accountable to one human. A team agent is accountable to the team. Workspace access is separate from this accountability. See Agent identity and stewardship.

How does an agent find workspaces? Run npx @animaapp/cli@latest workspaces. Use the returned workspace ID with list --workspace, create --workspace, or duplicate --workspace. See The Anima CLI.

What happens if no workspace is supplied when creating? It works only when the agent can create in exactly one workspace. With several writable workspaces there is no default, so the ID is required.

Why did an agent invite connect nothing? Creating an invite is only advance consent. Copy and deliver the one-time link; the agent must redeem it.

Can an agent publish on its own? It may publish only when it has publish and a human explicitly asks. A capable agent should offer publishing as a follow-up, not assume consent.

Claiming and support

Why did my AI send a claim link? It created anonymously before connecting. Claim within 24 hours of creation or the content is removed. See What is claiming.

How do I contact a person? Email [email protected]. Include the artifact, team, workspace, time, and exact error, but never credentials. See Contact support.

Questions and answers

Use the topic groups below to retrieve operational answers and route to the detailed procedure.

Scope model

What governs visibility?

Workspace access. A team contains members, workspaces, one billing plan, and one agent roster. A workspace contains artifacts and has its own access list. Team membership does not imply visibility of every artifact. An artifact link is an identifier, not an access grant. See Workspace access.

How should a private-artifact denial be handled?

Verify identity and reachable workspaces. If the workspace is absent, stop and request human approval. Do not infer owner, recipient, membership, or artifact existence. See Request access to a private artifact.

Where are people and agents administered?

Team membership belongs in team management; workspace grants belong in workspace access controls; agent invitation, stewardship, capabilities, and revocation belong in agent administration. Never direct a human to old artifact Share administration routes.

CLI and agents

How do I verify connection and scope?

Run:

npx @animaapp/cli@latest workspaces --json

Then use a returned workspace ID. list without --workspace spans all readable workspaces; with it, results are filtered.

What happens when create or duplicate omits --workspace?

Omission is allowed only when create access exists in exactly one workspace. With multiple writable workspaces there is no default. Never guess a destination.

What can duplication copy?

Code, assets, and supported database content. It excludes chat and custom domains. Duplication is non-idempotent, which means repeating it may create another artifact. After a timeout or lost response, list recent destination artifacts before retrying.

Does an agent receive a password or consume a seat?

No. It receives a separate identity and consumes no team seat. Access remains limited by workspace grants, capabilities, and live governing permissions.

May an agent publish?

Only with publish and an explicit human request. Verify the returned public URL. Sharing an artifact link is not publishing.

Why did an invite connect nothing?

The link must be delivered and redeemed. Creation alone only records advance consent.

Artifacts

Is Markdown autosaved?

Yes. Routine edits autosave continuously. Save or Command-S creates an explicit history checkpoint. Use History for unwanted saved results or conflict recovery. See Edit a Markdown artifact.

Are folder and ZIP imports live?

Yes. Accept one folder or .zip, up to 50 MiB and 1,000 files. Apps require an entry point; Markdown requires .md files. Imports create new artifacts and do not synchronize with local sources.

How should a blank app be handled?

Check the artifact type and entry point. Correct invalid source structure and create a new import.

Are URL and Figma imports separate Free allowances?

No. A Free team has five successful imports combined across both. Quota and artifact capacity are separate; deletion does not refund an import. See Limits and quotas.

Sharing and publishing

How do sharing and publishing differ?

Sharing governs AgentGrid access. Publishing produces a public site. Markdown publishing, published updates, unpublishing, and custom-domain plan requirements are covered by Publish to a public URL.

Can an artifact move?

Workspace moves are supported when source and destination permissions allow them. Cross-team duplication creates an independent copy. See Rename, move, and duplicate.

Plans and support

Plans are Free, Lite, Pro, and Business. Billing is per team and agents consume no seats. The live pricing page is authoritative.

An agent must not email support as a human. Produce a privacy-safe handoff for [email protected]. This means using only authorized identifiers and not revealing hidden owners, recipients, workspace names, or artifact existence. Include the workspace, exact error, time, and retry classification. See Contact support.