An artifact is an app, game, tool or page Gluon builds for you, such as a grocery-bill
splitter, a revision quiz, a trip planner or a birthday invitation. It opens beside the chat
and beside your library in Artifacts, and keeps its own saved data.
Some artifact features, such as publishing to everyone, are still rolling out and may not be
available to you yet.
- “Build a chore chart for the kids where they can tick off tasks each day.”
- “Make a quiz from the biology chapter I uploaded.”
- “Create a page comparing these three phones, with a chart.”
- “Make a shared shopping list app for our family group.”
Gluon writes the app in its workspace, builds it and shows it as a
card in the chat; your private chat opens it in the side panel. Ask for changes the same way:
“make the buttons bigger” or “add a dark mode”. If something breaks, use Fix on the app.
The card shows the app’s screenshot, its title and a line saying what that build added or
changed. Below them it says “Created · v1” for a new app, or which version an edit moved from and
to, such as “Edited · v1 → v2”. Open opens the app in the side panel, or on its own page
where the chat has no panel.
While Gluon works, the steps above its answer name the artifact by its title. If a build
fails and Gluon fixes it in the same reply, the failed attempt folds into Worked for… with
the other steps; only a build that still failed stays on show, with its errors.
For a one-off answer, Gluon shows a card
instead. Ask for an artifact when you want something to use, keep or share.
Every change saves a new version. In the open artifact’s header you can open the history,
switch between versions and Restore an older one as the newest; saved data is kept. Make a
copy, in the header’s menu, copies one version into a new private artifact without its history
or data.
Gluon can read the source of every saved version of your artifacts in a read-only
/artifacts folder of its workspace, so you can ask about one from
any chat: “Which of my apps uses a countdown timer?” or “What does my habit tracker save?”
- What it shows. In your private chat,
/artifacts holds your own artifacts. In a group,
it holds the group’s artifacts and the ones members have shared with the group. From your
private chat, Gluon can also look in the /artifacts of any group you’re in.
- What’s inside. Each artifact has a folder named after its title, with one folder per
version holding its code, images and other files, and a summary of its versions, notes and
sharing. Saved data isn’t there.
- Up to date. A deleted artifact disappears at once, and so does one that stops being
shared with the group.
- Editing. To change an artifact, even one from an earlier chat, Gluon copies a version
from
/artifacts into /workspace, edits it there and rebuilds it as a new version; it
can’t change anything in /artifacts itself. If someone saved a newer version in the
meantime, the rebuild is refused, so it never undoes their change. An artifact a member
shared with a group stays theirs: the group’s Gluon can read it, but only they can change it.
The Artifacts permission under Sandbox turns this off; see
Permissions.
- Artifacts in the main navigation shows every artifact you can open. On a computer they
fill the page as a grid of cards; on a phone, as a list. Each shows its screenshot and
version, its group or Public badge, its title, and its description or when it was last
updated, after the creator’s name when someone else made it. Search above them, and use the
chips All, Created by me and Shared with me, with their counts; a chip that
wouldn’t narrow what you see, such as Shared with me when nothing is shared with you, is
hidden. The filter button beside the search chooses one chat or group, who can open them
and the order (last updated, date created or name). Your filters stay in the address, so
going back keeps them.
- New artifact, the main button at the top of Artifacts, starts a new private chat with
“Build an artifact: “ in the message box, for you to say what to build. Discover sits
beside it.
- Choose an artifact to run it, with the list of your artifacts beside it so you can switch
between them. Its header shows the title once, then the version, who can open it, who made
it with a From chat link to the chat it came from, and its description. The header also
holds the version history, Share, Full screen and a menu with Reload, Make a copy,
Download source and Delete. On a phone, the list and the artifact are separate pages;
Back returns to the list. Every artifact you open, from Discover, a chat or a link,
opens here.
- Ask Gluon to change this artifact, at the foot of an artifact you can open, shows the
artifact as a chip with its title and says where Gluon will reply; your request is sent with
that chip, so Gluon changes that artifact and no other. It continues in the chat that built
it when you can open that chat: your own private chat, or the group’s chat as an @Gluon
mention. Otherwise, such as for an artifact shared with you or one whose chat was deleted, it
starts a new private chat with the request already sent.
- The side panel’s library lists the current chat’s or group’s artifacts.
- An artifact made in your private chat belongs to you; one made in a group belongs to the
group, and every member can edit it.
- Deleting a chat keeps its artifacts. Deleting the artifact, or the group that owns it,
removes it.
To share an app with your family or friends, share it with your group; everyone in the group can
then open it. The group chat shows “ shared the artifact “” with the group”, and
“stopped sharing” when you stop.</p>
<table>
<thead>
<tr>
<th>Option</th>
<th>Who can open it</th>
</tr>
</thead>
<tbody>
<tr>
<td>Private (the default)</td>
<td>You, or the group that owns it</td>
</tr>
<tr>
<td>Shared with a group</td>
<td>Members of one of your groups</td>
</tr>
<tr>
<td>Published</td>
<td>Anyone signed in to Gluon, from Discover or the link; they can remix it</td>
</tr>
</tbody>
</table>
<p>Widening who can see an artifact shows everything in it to them, so Gluon warns you first.</p>
<div class="sl-heading-wrapper level-h3"><h3 id="publishing-and-remixing">Publishing and remixing</h3><a class="sl-anchor-link" href="#publishing-and-remixing"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Publishing and remixing”</span></a></div>
<p>Publishing makes one chosen version public, with a public title, description and credit.
Later edits don’t change what’s published until you publish a newer version. Published
artifacts appear in <strong>Discover</strong>, opened from the top of Artifacts beside <strong>New artifact</strong>, under Trending, New and Top,
with search. Trending ranks what was published in the last 30 days by its stars and remixes,
favouring newer work, and refreshes every 15 minutes. Anyone signed in can <strong>Star</strong> one, or <strong>Remix</strong> it, which copies it into a new chat of
their own; remixes stay theirs after you unpublish. Visitors can <strong>Report</strong> a published artifact.
<strong>Artifacts</strong> at the top of Discover takes you back to your library. While nothing is published
yet, Discover lists a few of your own unpublished artifacts; choose one to open it at its
<strong>Share</strong> menu’s publish step. With no artifacts at all, it offers <strong>New artifact</strong> instead.</p>
<p>To get a profile, choose a handle in <strong>Settings → Account</strong>. It shows your name and the
artifacts you publish, with their remixes and stars, and your name on your artifacts links to it;
your email stays private.</p>
<p>A group artifact’s publisher chooses the credit: their own name, or the group’s name
“published by” them.</p>
<div class="sl-heading-wrapper level-h3"><h3 id="ask-in-a-chat">Ask in a chat</h3><a class="sl-anchor-link" href="#ask-in-a-chat"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Ask in a chat”</span></a></div>
<p>In a private chat, your Gluon can change who sees your artifacts and manage your Discover
profile:</p>
<ul>
<li>“Publish my chore chart to Discover” or “Unpublish the quiz”</li>
<li>“Share the shopping list app with the Sharma Family group” or “Stop sharing it”</li>
<li>“Set my public profile handle to asha-makes”</li>
<li>“Star this artifact” with its link, or “Delete my old quiz app”</li>
</ul>
<p>Publishing, sharing and your profile always ask you first and show exactly what changes,
before and after, such as how the artifact will look in Discover. Deleting asks too unless
you change its permission. These changes run only when you approve them in a turn you
started; a scheduled task can’t make them. The same rights apply as
in the open artifact’s header: for a group’s artifact, only its creator or the group owner can
publish or delete it.</p>
<div class="sl-heading-wrapper level-h2"><h2 id="saved-data">Saved data</h2><a class="sl-anchor-link" href="#saved-data"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Saved data”</span></a></div>
<p>Artifacts can save data:</p>
<ul>
<li><strong>Personal data</strong> follows each person across their devices: up to 5 MiB per person per
artifact.</li>
<li><strong>Shared data</strong> is seen by everyone the artifact is shared with, such as a family’s
shopping list: up to 20 MiB per artifact. People opening it by link or as a published
artifact get personal data only. Changing which group an artifact is shared with clears its
shared data.</li>
</ul>
<div class="sl-heading-wrapper level-h2"><h2 id="artifacts-that-use-your-connections">Artifacts that use your connections</h2><a class="sl-anchor-link" href="#artifacts-that-use-your-connections"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Artifacts that use your connections”</span></a></div>
<p>An artifact can show live data from your <a href="/features/connectors/">connectors</a>, such as a family
dashboard of everyone’s steps or a page of your portfolio. Each version lists the servers and
tools it uses, and reads nothing of yours until you allow it. It reads each account live
whenever it loads, so the data is never copied into its code. These calls are free.</p>
<div class="sl-heading-wrapper level-h3"><h3 id="allow-it">Allow it</h3><a class="sl-anchor-link" href="#allow-it"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Allow it”</span></a></div>
<p>When a version asks for your connections, Gluon shows a banner over it, ““<title>” wants to read
data from your connections.”, with <strong>Not now</strong> and <strong>Review</strong>. <strong>Review</strong> opens “Let “<title>”
read your data?”. Gluon draws the banner and the dialog; the artifact can’t change them. The
dialog shows:</p>
<ul>
<li>Each server it uses, with your connection to it. If you have more than one, choose which one
it uses. Without one, <strong>Connect</strong> opens <strong>Add server</strong> on <strong>Connectors & tools</strong> with that
server’s address filled in; come back to the artifact once it’s connected. A connection that
isn’t ready, such as one that needs you to sign in again, shows no tools until it is.</li>
<li>Each tool as your own server describes it, never as the artifact does, with the level you
give it: <strong>Allow</strong>, <strong>Ask</strong> or <strong>Off</strong>. It starts at the artifact’s suggestion, within your
limits: only a read tool you allow yourself can be Allow, any other tool goes no further than
Ask, and a tool you turned Off stays Off.</li>
<li>Who will see what it reads: “Only you” for your own private artifact, or “Everyone in
<group>, including future members” for a group’s artifact or one shared with a group.</li>
</ul>
<p>Choose <strong>Allow</strong>, and the artifact reloads with your data. Your own
<a href="/features/connectors/#permissions">permissions</a> keep applying: if you later turn a tool Off,
the artifact can’t use it either.</p>
<div class="sl-heading-wrapper level-h3"><h3 id="sharing-it-with-a-group">Sharing it with a group</h3><a class="sl-anchor-link" href="#sharing-it-with-a-group"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Sharing it with a group”</span></a></div>
<ul>
<li><strong>Sharing it with a group</strong> opens the dialog for you straight away, for the group. The group
chat gets a card naming the artifact, each connector and its tools, with <strong>Review</strong> and <strong>Not
now</strong>, so each member decides for their own account. Once you’ve allowed it, your card shows
<strong>Allowed</strong>.</li>
<li>What you allowed for yourself on a private artifact doesn’t carry over: you decide again for
the group. It applies again once you stop sharing.</li>
<li>An artifact made in a group posts no card; its members allow it from the banner.</li>
</ul>
<div class="sl-heading-wrapper level-h3"><h3 id="what-others-see">What others see</h3><a class="sl-anchor-link" href="#what-others-see"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “What others see”</span></a></div>
<ul>
<li>On someone else’s account an artifact only runs the read tools they set to Allow. It can never
place an order or send a message as anyone but the person viewing it.</li>
<li>Without that connector you still see the data of everyone who allowed it.</li>
<li>Only current members’ data shows: someone who leaves the group no longer adds theirs.</li>
<li>When someone’s connection needs them to sign in again, the artifact can show “<Name>’s
<connector> needs them to sign in again.” in place of their data. Gluon sends them one
notification, “Sign in to <connection> again”, linking to that connection’s page, however
many people open the artifact meanwhile. Their data shows again once they reconnect.</li>
</ul>
<div class="sl-heading-wrapper level-h3"><h3 id="actions-on-your-own-account">Actions on your own account</h3><a class="sl-anchor-link" href="#actions-on-your-own-account"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Actions on your own account”</span></a></div>
<p>On your own account, an artifact can also use tools you left at Ask, such as adding a task.
Each call asks you first: Gluon shows “Let “<title>” use <tool>?” over the artifact, naming your
connection, the tool’s description from your server and the exact input. <strong>Deny</strong> is chosen
first, and <strong>Allow</strong> works only after a moment, so a double click can’t approve the next one.
Only your <strong>Allow</strong> runs it; the artifact never sees or answers this dialog. A tool you keep at
Auto, even a read tool, asks the same way. If you turn the tool Off while the dialog waits,
<strong>Allow</strong> still refuses it.</p>
<div class="sl-heading-wrapper level-h3"><h3 id="new-versions">New versions</h3><a class="sl-anchor-link" href="#new-versions"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “New versions”</span></a></div>
<p>When a new version uses tools you haven’t decided on, the banner says ““<title>” now also wants
<tools>.” and the dialog marks them <strong>New</strong>. Until you decide, only those tools fail for you;
what you already allowed keeps working. Tools a version no longer uses are ignored.</p>
<div class="sl-heading-wrapper level-h3"><h3 id="withdraw">Withdraw</h3><a class="sl-anchor-link" href="#withdraw"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Withdraw”</span></a></div>
<p>Choose <strong>Your connections</strong> in the artifact’s <strong>More actions</strong> menu, or the plug button on a
published artifact’s page, then <strong>Withdraw</strong>. It stops new reads at once, on every server the
artifact used. Anything the artifact already saved stays until the artifact or its data is
deleted. You can also withdraw from the connection’s own page; see
<a href="/features/connectors/#used-by-artifacts">Used by artifacts</a>.</p>
<p>Your consent also ends when:</p>
<ul>
<li>you leave the group or are removed from it, or the group is deleted;</li>
<li>you remove the connection;</li>
<li>the artifact is deleted;</li>
<li>the artifact is shared with another group or stops being shared. Sharing it with your group
again asks you again.</li>
</ul>
<div class="sl-heading-wrapper level-h3"><h3 id="published-artifacts">Published artifacts</h3><a class="sl-anchor-link" href="#published-artifacts"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Published artifacts”</span></a></div>
<p>A published artifact can use connections too: the publish dialog and its card in Discover show
“Uses: <connector> › <tools>”. Someone who opens it from Discover allows it for themselves only
and sees only their own data; nobody else’s reaches them, and theirs reaches nobody. A member of
the group it belongs to or is shared with still sees it as the group does, with the
group’s data. Publishing again doesn’t undo anyone’s
consent. A remix uses the same connections but starts with nobody’s consent.</p>
<div class="sl-heading-wrapper level-h2"><h2 id="artifacts-that-use-ai">Artifacts that use AI</h2><a class="sl-anchor-link" href="#artifacts-that-use-ai"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Artifacts that use AI”</span></a></div>
<p>An artifact can call an AI model, for example to generate quiz questions. Each person who uses
it pays for their own calls, from their own credits, after agreeing once per version. Calls are
limited to $1 a day per person across all artifacts.</p>
<div class="sl-heading-wrapper level-h2"><h2 id="limits">Limits</h2><a class="sl-anchor-link" href="#limits"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Limits”</span></a></div>
<ul>
<li>Up to 100 builds a day per person or group, two at a time.</li>
<li>Source up to 4 MiB; images and other assets up to 25 MiB each and 100 MiB per artifact.</li>
<li>Artifacts have no server of their own: no backend, database or server code beyond saved
data and AI calls.</li>
</ul>
<div class="sl-heading-wrapper level-h2"><h2 id="storage-cost">Storage cost</h2><a class="sl-anchor-link" href="#storage-cost"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Storage cost”</span></a></div>
<p>Each artifact’s storage is charged daily to its owner: yours to you, a group’s to the group’s
owner. Sharing an artifact with a group doesn’t move its cost, and a copy or remix is charged
to whoever made it. Your usage lists it as <strong>Artifact file storage</strong> (the app’s code, built
files, images and screenshots, each stored file counted once however many versions use it) and
<strong>Artifact database</strong> (its versions and saved data, including the personal data of everyone
who opens it), priced in <a href="/reference/prices/">Prices</a>. Deleting an artifact stops its charge
at once. See <a href="/features/credits-and-usage/#who-pays">Credits and usage</a>.</p>
</div><footer class="sl-flex astro-rfnougcp"><div class="meta sl-flex astro-rfnougcp"></div><div class="pagination-links print:hidden astro-m3la6hmq" dir="ltr"><a href="/features/browser/" rel="prev" class="astro-m3la6hmq"><svg aria-hidden="true" class="astro-m3la6hmq astro-6hfrxd4l" width="16" height="16" viewBox="0 0 24 24" fill="currentColor" style="--sl-icon-size: 1.5rem;"><path d="M17 11H9.41l3.3-3.29a1.004 1.004 0 1 0-1.42-1.42l-5 5a1 1 0 0 0-.21.33 1 1 0 0 0 0 .76 1 1 0 0 0 .21.33l5 5a1.002 1.002 0 0 0 1.639-.325 1 1 0 0 0-.219-1.095L9.41 13H17a1 1 0 0 0 0-2Z"/></svg><span class="astro-m3la6hmq">Previous<br class="astro-m3la6hmq"><span class="link-title astro-m3la6hmq">Browser</span></span></a><a href="/features/notifications/" rel="next" class="astro-m3la6hmq"><svg aria-hidden="true" class="astro-m3la6hmq astro-6hfrxd4l" width="16" height="16" viewBox="0 0 24 24" fill="currentColor" style="--sl-icon-size: 1.5rem;"><path d="M17.92 11.62a1.001 1.001 0 0 0-.21-.33l-5-5a1.003 1.003 0 1 0-1.42 1.42l3.3 3.29H7a1 1 0 0 0 0 2h7.59l-3.3 3.29a1.002 1.002 0 0 0 .325 1.639 1 1 0 0 0 1.095-.219l5-5a1 1 0 0 0 .21-.33 1 1 0 0 0 0-.76Z"/></svg><span class="astro-m3la6hmq">Next<br class="astro-m3la6hmq"><span class="link-title astro-m3la6hmq">Notifications and Needs you</span></span></a></div></footer></div></div></main></div></div></div></div></div><script type="module">var e=class extends HTMLElement{constructor(){super();let e=matchMedia(`(min-width: 50em)`),t=()=>{this.popover=e.matches?null:`auto`};t(),e.addEventListener(`change`,t),this.addEventListener(`toggle`,e=>{let t=e.newState===`open`;for(let e of document.querySelectorAll(`.main-frame, .sl-skip-link`))e.toggleAttribute(`inert`,t)})}};customElements.define(`sl-sidebar-pane`,e);</script></body></html>