Skip to content

Copy from the Library

When you copy a setup from the Library, you get real objects in your own account. They are yours to change. Nothing links them back to the author.

Example: you copy Mia’s habit tracker. You get a Habits collection, its views, its card design, its presets and its “streak on tick” automation. You rename “Status” to “Mood” and delete two sample habits. Mia never knows, and her later edits never reach you unless you take an update.

What you see before you copy

  • A live preview, drawn in a sealed frame (a separate little page that cannot reach the app or your data), filled with made-up sample entries.
  • What it can do and what it can see: which collections a script reads and changes, which websites it calls, what it sends. The app works this out from the code, never from the listing’s own words.
  • For anything that sends data out, a plain sentence: “sends data from Workouts to api.example.com”.

When you copy a hub

A hub in the Library holds no one’s data, so your copy shows yours.

Example: you copy a Training hub. Its author had three tabs: This week’s workouts, Fitness and My training notes. Your copy has two:

Tab in your copy What you get
This week’s workouts the same view, showing your workouts
Fitness a new dashboard in your Dashboards collection, made from the listing’s layout preset and filled with your data
  • View tabs come as setups. They show your own entries.
  • Dashboard tabs come as a layout: a preset of the Dashboards collection with the same Chart, View and HTML blocks. The copy makes a new dashboard from it. The preset stays in Dashboards, so you can make more dashboards like it.
  • Tabs that pointed to the author’s entries, such as My training notes, never came. They stayed behind when the author published.
  • The hub’s name, icon and quick options come too. Rename or change anything: it is yours.

What starts on and what starts off

Part of the copy On arrival
Collections, properties, views, presets, hubs on
Themes, card designs and looks (after the safety checks) on
A button’s change, links, AI questions inside a design off until you switch each on
Everyday automations off until you switch them on
Scripts and HTML blocks off until you approve them
An agent’s or a skill’s scripts off until you approve them

Approving a script, an automation or an HTML block that runs a script is a change only you can make. You do it in the app, after a fresh check.

Why looks can be on: a Library design cannot reach the internet, and your data never travels to its author. So a fake form inside a card has no way to send anything back.

Updates are offered, never forced

Your copy stays on the version you took. When the author publishes a new version, you get an offer with a before and after view. Your own changes stay.Listing v3Listing v4Your copyv3 + your changesOffer: update to v4before and after viewyour changes stay
Nothing changes in your copy until you accept the update.
  • Your copy stays on the version you took.
  • When the author publishes a new version, you get an offer with a before and after view.
  • A copied design remembers its base and keeps your changes apart. When you take an update, your changes stay on top.
  • An update never installs by itself. If it would let code read, change or send more, you approve it again.

If a listing turns out to be bad

You can report it. If we find it harmful, we switch off its code and its actions on every device that copied it. Your collections and entries stay.