@roomy-ai/apps
v0.2.6
Published
Roomy-shipped built-in apps. Synced to ~/Roomy/.apps/ on server start and mounted into every sandbox at /opt/roomy-apps/.
Readme
@roomy-ai/apps
Roomy-shipped built-in apps. Each *.app/ directory in this package is a complete Roomy app — the same structure that roomy-agent app create produces in a workspace — pre-built so dist/ is shipped alongside source.
On server start, runtime.writeBuiltinApps(home) copies every <name>.app/ here into ~/Roomy/.apps/<name>.app/ (overwriting), then the sandbox mount plan binds ~/Roomy/.apps/ read-only at /opt/roomy-apps/. Agents attach built-in fragments via the regular roomy-agent chat attach-artifact command using paths under /opt/roomy-apps/.
Adding a built-in app
The intended workflow is to build the app via Roomy itself (dogfood), then promote the workspace output into this package:
- Open a Roomy chat in any workspace.
- Ask Roomy to build the app (e.g.
chat-forms.appwith ayes_nofragment). - Iterate until the workspace app is correct.
- Copy
<workspace>/.chats/<chatId>/artifacts/<name>.app/intopackages/apps/<name>.app/. - Commit. The next server start syncs it into
~/Roomy/.apps/.
Constraint
All built-in apps must use @roomy-ai/ui for every UI primitive — no raw HTML elements where a UI component exists, no second component library. If a primitive is missing, add it to @roomy-ai/ui first.
