Pages

Ask an agent to build a small tool that saves its data in workspace files.

View Markdown
On this page

An .html file opens as a working page in Cabane. Ask an agent to create one when you need an interface for a tracker, dashboard, form or calculator.

Ask for a page that saves

Keep the interface and its data in separate files. That lets you change the page without replacing the information people have entered.

Example prompt

Build a reading tracker in a new folder in this room. Put the interface in index.html and the data in books.json. Save changes to books.json through Cabane's file API, show any save errors, and check that an update survives closing and reopening the page.

Pages run in a sandbox, and browser storage is temporary. Data you need to keep belongs in workspace files. Edits are recorded as changes by the person using the page, with the usual version-history grouping.

The page, open
Portfolio tracker
WrapperActive
RunwayExited
Saved to portfolio.json
file API
Two files in the room
rooms/portfolio/tracker
index.htmlthe interface
portfolio.jsonthe data, with versions
Browser storage: temporary. Gone on another device or a cleared browser.
A portfolio tracker whose interface is index.html and whose data is portfolio.json, written through Cabane's file API; browser storage is temporary

Check the result

Open the page, change one value, close it and reopen it. Confirm the change remains. If it doesn't, ask the agent to fix saving before relying on the tool.

An agent with browser access can help perform this check. Keep save errors visible so a failed update doesn't look successful.

Understand its access

Inside Cabane, a page reads the workspace as nobody in particular, so it gets the same answers whoever opens it. It can read public workspace files and the files in its own room. It can't reach other private rooms, even ones you belong to. It doesn't get your unread status, the questions waiting on you or your recent files, though it can read the questions in conversations it can access. Write permissions still apply.

The containing folder organizes the page and its data; it doesn't generally confine an in-app page's access to those files alone.

Cabane renews an open page's access automatically and may reload it when renewing. Save data in workspace files so it survives a reload.

rooms/portfolio/tracker/index.html, opened by Miles, reads as nobody in particular
fund-overview.mdpublic: reads it
rooms/dealspublic room: reads it
rooms/portfolioits own room: reads it
rooms/partnersprivate: not even for Miles
rooms/fund-iiprivate: no
A page in Portfolio reads public files and its own room's; it can't read private Partners or Fund II, even when Miles, a member of both, opens it

Change it or use it as a room home

Ask for changes in the conversation beside the page. The page redraws when the agent edits its HTML. Its source and data remain ordinary files, with versions you can restore.

A workroom's files view uses index.html in the room folder as its home page. After renaming a room, check any links that contain its old full address.

Share it outside Cabane

A public page link is read-only and has a different scope: it includes the page's containing folder and its subfolders. Give a page you intend to share a dedicated folder containing only the material you mean to publish.

Sharing a page at the workspace root includes public workspace contents in that scope. It doesn't open unrelated private rooms. Review the folder before enabling Share links.