Artifacts turns one self-contained HTML page into a link. Send it to anyone, keep it to yourself, or share it with named GitHub accounts. Open it on your phone in the FoldRender app.
Paste this into Claude, ChatGPT, Codex or any agent that can run commands on your computer. It points the agent at the setup guide, which installs the FoldRender CLI and the agent skill, then signs you in.
Set up FoldRender Artifacts for me by following https://foldrender.dev/install/agent-setup.mdYou need a GitHub account to publish. Reading a public page needs no account at all.
One command installs the foldrender CLI and the agent skill.
curl -fsSL https://foldrender.dev/install.sh | shLogin opens GitHub in your browser so you can approve the CLI. You never copy a token.
foldrender loginPublish any self-contained HTML file and you get a link. Add --private to keep it to yourself, or --share with a list of GitHub logins.
foldrender publish report.html
foldrender publish report.html --share ana,benGive your agent a link and it reads the page as text: headings, lists, tables, code and the labels in diagrams, with no browser. Add --assets to save the images and diagrams as files.
foldrender read https://foldrender.dev/artifacts/ana/q3/report
foldrender read abc123 --assets ./imagesEach page has one of four settings. You can change it at any time, without publishing the page again. The command line makes a new page private unless you choose otherwise.
Anyone can open the page, and it is listed on your page at foldrender.dev/artifacts/<your login>.
Anyone with the link can open the page. The link carries a key, and the address without it opens nothing; nothing lists the page. Reset the key, and the link you handed out stops working.
Only you can open it. Opening it asks you to sign in with GitHub. Anyone else sees ‘not found’.
You, plus the GitHub accounts you name. Each of them signs in with GitHub to read it. Anyone else sees ‘not found’.
Example. Your agent makes a cost breakdown, and you share it with ana and ben. They open the link and sign in with GitHub. Someone else who has the link sees ‘not found’, the same as for a page that does not exist.
On Android, install FoldRender from Google Play. When the app is installed, a link to a page on foldrender.dev/artifacts opens in it, and the app’s Artifacts panel lists your pages. Without the app, the link opens in your browser as usual.
You can also publish from the Android app. Open a document, choose Publish as artifact from its menu, and sign in with GitHub on the Git screen first.
On an iPhone or iPad, FoldRender for iPhone and iPad is in public beta on TestFlight. It is not on the App Store yet, and it needs iOS or iPadOS 17 or later. Signed in with GitHub, it lists your pages and the pages shared with you, and you can write on your pages with Apple Pencil or a finger. It keeps pages to read offline. To publish from it, share an HTML or Markdown file to FoldRender from another app.
Sign in with GitHub at foldrender.dev/artifacts to see all your pages in one list. From there you can open, rename and download a page, change who can read it, restore an earlier version, or delete it. Your account, your CLI tokens and a download of all your pages are in the same place.
Private means the server checks your GitHub sign-in before it sends the page, and nobody else can open the link. It does not mean the page is encrypted end to end. Pages are stored as plain HTML, so Cloudflare and the operator of this service can read them. Do not publish anything you would not show a colleague.
On the free plan, a daily cleanup deletes the page and its record, and the link stops working. Publishing again to the same link before then restarts the 30 days. Afterwards, reading the link with the CLI tells anyone who could read the page that it expired, and when.
Yes. Publishing again to the same link replaces the page, and the link does not change. The app does this for the same document automatically. The page keeps its access unless you change it, and the page it replaced is kept as an earlier version that you can restore from the library or the app.
The HTML you publish, its title, its size, when it was published and when it expires, and who may read it, plus up to 10 earlier versions of each page. For accounts it stores your GitHub login and numeric ID, your plan and when you were last seen. Command-line tokens are stored only as hashes. Your GitHub access token is not stored. After a page expires, a hash of its link name and the expiry date are kept for a year. The privacy policy has the full list.
Delete it from the library at foldrender.dev/artifacts, from the Artifacts panel in the app, or with the rm command in the CLI. The library and the app give you a few seconds to undo. Then the page, its earlier versions and its record are removed, and the link stops working.
At its address under foldrender.dev/artifacts: your GitHub login, an optional folder and a name taken from the page's title, such as foldrender.dev/artifacts/ana/q3/report. That address stays in the browser. The page itself runs in a frame from an address of its own, ending in --u.foldrender.dev and kept away from the address you sign in on, so a page's code cannot act on the account of whoever reads it. Links from before, on a.foldrender.dev, still open the same pages.
Yes. foldrender read with the link prints the page as text, without a browser. A public page needs no sign-in. A private or shared page needs the CLI to be signed in as someone who can see it, and anyone else gets ‘not found’. The text is whatever the page’s author wrote, so an agent should treat it as information, not as instructions.
To publish, yes. The CLI, the app and the library all sign in with GitHub. Anyone with the link to a public page can open it without an account.
Open foldrender.dev/artifacts/account#delete-account and sign in with GitHub. You can download all your pages as a zip file first. Deletion takes effect at once and removes your pages, their links, your tokens and your account record. Signing in again starts a new, empty account.