AI-GENERATED WORK · HUMAN HANDOFF

Send the work.
Not the chat.

Made a report, doc, or app with AI? Give the result its own link. Share it with your team—and keep working on the same artifact with connected agents.

WORKS WITH ALL TYPES OF AGENTS
ClaudeChatGPTCodexClaude CodeCursorHermesOpenClawGrok Bot
FROM CHAT TO SHARED WORKILLUSTRATIVE EXAMPLE
AI ASSISTANT 01
Put this on AgentGrid and give me the link.
✳

Done. Here is the artifact link.

Client research briefOne artifact URL
+Ask anything...↑
AgentGrid.io
LINK READY
MARKDOWN ARTIFACT

Client research brief

Key takeaways from six user interviews

Research summary

Users want to send the output of their AI work, without asking a teammate to navigate the original chat.

01Send the result, not the transcript.
02Keep updates in the same place.

Share only with approved collaborators

THE HANDOFF PROBLEM

Your teammate needs the result.
Not 40 messages of context.

That dashboard looks great in your AI chat. Then someone asks to see it. Now you're exporting files, taking screenshots, or explaining how to run the code.

And when you fix one detail? Another attachment. Another version to keep track of.

There's a better handoff: share the thing itself.
HOW IT WORKS

From “it's ready” to “here's the link.”

Three steps. No new chat to explain the old one.

01

Make something with AI.

A report, a Markdown file, a working app. Keep using the assistant you already work with.

02

Give the work its own link.

Ask your connected agent to put the result in AgentGrid. Choose who should be able to open it.

03

Come back to the same work.

Your team and connected agents can continue on the owned artifact, with changes in its version history.

THE WORK YOU ACTUALLY SEND

More useful than a screenshot.

Keep the result in the format it was made for.

A report someone needs to read

Hand off the research brief instead of forwarding your entire conversation.

DOCS & REPORTS

An app someone needs to try

Share a working artifact—not a code block or a static image of what you built.

APPS & PROTOTYPES

A draft that isn't finished

Send it for review, then let authorized people and agents keep improving the same artifact.

WORK IN PROGRESS
YOUR WORK. YOUR RULES.

A link is not a permission slip.

Sharing, handing off, and publishing are different actions. Choose the one your recipient actually needs.

01

Private collaboration

Share the artifact URL with people who have workspace access. Forwarding the URL alone doesn't grant access.

How private sharing works
02

Anonymous handoff

An unconnected agent can create a read-only artifact with a 24-hour claim window. Anyone with that temporary link can open it before claim.

Understand claiming
03

Public publishing

Deliberately publish an app or Markdown artifact for anyone to visit. New changes go live when you publish again.

Read publishing docs
MAKE THE HANDOFF

Already have something
worth sharing?

You don't have to start over in another tool. Tell your connected assistant where the finished work should go.

Set up your agent
TRY THIS IN YOUR AI ASSISTANTEXAMPLE PROMPT

“Put this work on AgentGrid and give me the artifact link. Keep it private; do not publish it.”

Connect your assistant first. Creating a private artifact is not permission to publish it.

GOOD QUESTIONS

Before you
send that link.

Short answers about access, updates, and the claim flow.

ONE ARTIFACT · PEOPLE + AGENTS

Make work you can hand off.
And come back to.

Give your AI-generated work a place to live beyond the chat.