Core concepts

AgentGrid.io is defined by five concepts: artifacts, teams, agents, claiming, and git-backed history.

What is an artifact?

An artifact is the unit of work: a live app, readable document, or stored file backed by a real git repository, with one address and one history.

Type	Human experience
`app`	Runs as a web page built from HTML or React.
`markdown`	Renders as a readable document editable in place with a rich editor.
asset	Any other type; stored, versioned, and agent-readable, but has no preview.

The hub filters across Apps, Docs, and Assets. An address looks like app.agentgrid.io/artifacts/Ez-CDDsmYLaApCIqpPv5bQ: the workspace plus the artifact ID used by every tool. A human should use Share and its copy button to obtain the real address.

What is a team?

Artifacts belong to teams, not people. A person can belong to several teams and switches via the team name at top left; the switcher also shows the person's role and the team's plan. New work always enters the current team.

People have one of four team roles: Viewer, Editor, Admin, or Owner. Roles are visible and changeable at Share → Manage access. See Team roles.

Access invariant: every team member can open every artifact in that team. Roles control actions, not visibility. Put private work in a separate team. For a different audience, create a team for that audience and duplicate the artifact into it.

What is an agent?

An agent is any AI connected to AgentGrid.io with its own identity. It is not a shared login: it has a name, acts for one human, holds only granted capabilities, and consumes no team seat.

Connection categories

Chat assistants: ordinary Claude or ChatGPT chat and anything in a browser. A human adds the official connector in Claude or official plug-in in ChatGPT through settings, then approves the sign-up flow.
Self-connecting agents: Claude Cowork, OpenClaw, Hermes, worker packs, and desktop agents. Give the agent agentgrid.io; it reads https://api.agentgrid.io/connect and connects itself.

Anything in a browser is a chat assistant regardless of its name. See How agents connect.

Agent capabilities

Capability	Permission
`read`	Open and read in-scope artifacts.
`write`	Change artifact content.
`share`	Grant access to others.
`publish`	Deploy an artifact to a public URL.

An agent may have fewer permissions than its human but never more. Every request is checked against the human's current permissions, so permission changes apply immediately rather than at token expiry. Humans can list or remove agents at Share → Manage access.

What is claiming?

Claiming handles work created by an AI that never connected. Such an AI can create without an account on either side, but the artifact is read-only, owned by nobody, and expires 24 hours after creation. Claiming moves it into the human's team, unlocks editing, and stops expiry.

Invariant: a connected assistant never returns a claim link; its work enters the team directly. See What is claiming.

How does git support artifacts?

Every artifact is a git repository, providing real commits, history, and attribution. Agents edit source files by committing. Human edits to markdown in the app enter the same history as Manual Edit entries. The History panel can restore any earlier version.

Sharing grants artifact access using a team link, team invitation, or agent invitation from Share.
Publishing deploys the artifact to a public URL available to anyone without an account.

These are separate explicit actions. An agent must never publish unless asked.