Apps
Programs your agents build, which read and write your tables as themselves.
An app is a program the owner’s agent built (usually a web page, sometimes a server or script) that reads and writes the workspace’s data, under its own name, for the person using it.
Apps are actors
Like an agent, an app has its own name, scope and approval rules. Its changes are recorded under its name and can be rolled back. Unlike an agent:
- Its writes apply at once by default, because a person clicking in it can’t wait for an approval. The owner can make some kinds wait.
- It never changes the schema. The agent that built it creates the tables first.
- Its later edits count as the owner’s when rolling back an agent’s changes: they come up as conflicts, never undone silently, and they never cascade.
Kinds of app
| Kind | Where it runs | How it signs in |
|---|---|---|
| Published page | inside the workspace, at /w/<handle>/apps/<name> | the owner allows it the first time they open it |
| Hosted elsewhere | any https address, or localhost | app.signIn() sends the owner to Tabulic’s consent page and back |
| Script or server | anywhere | a secret key, Authorization: Bearer tabulic_sk_… |
Published pages
An agent with permission publishes a page with publish_page({name, title, html}): one self-contained HTML file. Publishing to the same name makes a new version of the same app. Any agent can update it later: it reads the current HTML with read_page, edits it and publishes again.
- A newly published app waits to be allowed, touching nothing, until the owner first opens it and chooses Allow.
- If a new version asks for more access, Tabulic asks the owner again.
- Every version is kept (within the history window, and always the current one). The owner can Restore an older one or Unpublish.
- Only the owner can open a workspace’s pages.
The sandbox
An app’s page is agent-written code, and a row in your tables could have steered that agent. So every page runs in a sandboxed frame below the workspace’s top bar:
- The frame has no address of its own, so it can’t touch Tabulic’s screens or your sign-in.
- It may load scripts only from the workspace (
tabulic.js) and a few public CDNs (cdnjs, jsdelivr, unpkg). - It can’t send requests anywhere, not even to Tabulic.
tabulic.jshands each call to the page around it, which makes it as the app, with the app’s access. The app’s credentials never reach the page’s code. - Images must be
data:orblob:URLs.localStoragedoesn’t persist; anything to remember belongs in a table. alert(),confirm()andprompt()do nothing (confirmreturns false). Pages ask in their own way, such as a second click.- Links leave with
target="_blank"ortarget="_top".
What a browser can’t stop: a link or window the page opens on a click goes wherever the page says, and could carry what the page shows.
By default a page links tabulic.css and looks like Tabulic around it, in light or dark mode.
Claude artifacts are not apps
A Claude artifact can read and write Tabulic through the claude.ai connector. Its writes are then the connector’s agent’s (for example “Claude”), under that agent’s rules, and it only works inside Claude.
See the App API for building one.