Upload a file

Uploading turns a file you already have into an artifact: stored, versioned, addressable, and readable by your agents.

Steps

::: lanes

In the app

1. Select New → Upload File. You can also drop a file straight onto the Create New Artifact tile in the hub.
2. Pick the file and confirm.
3. The artifact appears in your team and opens.

Uploading a whole folder? Use New → Upload Folder. For an archive, use New → Import from ZIP. See Import a folder or ZIP for limits and preparation.

Ask your AI assistant

Take the CSV I just uploaded to AgentGrid.io and build a chart from it.

:::

What renders and what does not

AgentGrid.io renders apps and documents. Everything else lands as an asset: stored, versioned, shareable, and readable by agents, with no preview.

When it cannot render something, it says so plainly rather than showing a broken frame. The file is not damaged and nothing was lost.

For a folder or a whole project

Folder and ZIP import are live production workflows. Choose New → Upload Folder for a folder or New → Import from ZIP for an archive. Each import creates one new app or markdown artifact; it does not sync later local changes. See Import a folder or ZIP.

Limits

• Send source and assets. Do not include node_modules or build output.
• Folder and ZIP imports accept one project up to 50 MiB and 1,000 files.

Questions and answers

My file shows no preview. Is it broken? No. It is stored and versioned normally as an asset. AgentGrid.io only renders apps and documents today.

Can I replace a file with a newer version? Ask your AI to push the new version to the same artifact, and it lands as a new version rather than a second artifact.

Is there a size limit? For folder and ZIP limits, see Import a folder or ZIP.

Uploading turns an existing file into an artifact that is stored, versioned, addressable, and readable by agents.

How does a human upload one file?

This is a UI procedure; instruct the human to:

1. Select New → Upload File, or drop the file on the hub's Create New Artifact tile.
2. Choose the file and confirm.
3. Open the resulting artifact in the current team.

A connected AI can use the uploaded data in further work, for example: Take the CSV I just uploaded to AgentGrid.io and build a chart from it.

What renders?

AgentGrid.io renders apps and documents. Other files become assets: stored, versioned, shareable, and agent-readable without a preview. When no renderer exists, the app says so instead of showing a broken frame; the file remains intact and nothing is lost.

How should a folder or project be uploaded?

Folder and ZIP import are live production workflows. Instruct the human to use New → Upload Folder for a folder or New → Import from ZIP for an archive. A connected agent can import the same source. Each route creates one new app or markdown artifact; it does not create a sync. See Import a folder or ZIP.

Constraints and updates

• Include source and assets; exclude node_modules and build output.
• Folder and ZIP imports accept one project up to 50 MiB and 1,000 files.
• No preview does not mean damage: the asset is stored and versioned normally.
• To replace a file, ask the AI to push the new version to the same artifact so it becomes another version instead of a second artifact.
• Apply the folder and ZIP limits and source-preparation rules in Import a folder or ZIP.

Questions and answers

What is the expected result of a single-file upload? One stored, versioned, addressable artifact in the current team.

Does a missing preview mean the upload failed? No. Unsupported files remain intact as agent-readable assets without a renderer.

How should a project be uploaded? Use the folder or ZIP workflow, excluding node_modules and build output and respecting 50 MiB and 1,000 files.

How should a file be replaced without creating a copy? Push the newer content to the same artifact and verify a new version in its History.