Capabilities
Choose the Rome App artifacts your app needs, and delete the ones it does not.
Agent-readable version: Markdown · llms.txt
Rome Apps are made from small declared artifacts. Start with the product shape,
then keep only the capabilities the app actually uses. Every capability listed
in app.yaml must have matching files on disk, and every removed capability
should be deleted from both places.
Actions
Define typed operations that agents, routines, APIs, and other app code can run.
Agents
Add app-private LLM agents for open-ended work over app context.
Skills
Ship plain-language instructions agents load only when relevant.
Hooks
React to daemon runtime events such as messages and agent turns.
Routines
Schedule actions or run them in response to event-bus triggers.
Events
Publish domain events and discover event payloads for routine filters.
Database & Migrations
Store app state in Drizzle tables inside the shared Rome SQLite database.
HTTP API
Serve app-owned backend endpoints for your UI, callbacks, and webhooks.
WebSockets
Upgrade app API requests to live WebSocket connections.
Web UI
Mount a React surface inside the dashboard and call your app backend.
Browser Automation
Drive the guardian's agent browser over CDP from app backend code.
Telemetry & Tracing
Stamp spans on your app's work so it shows up in the instance's traces.
Favor Request Actions
Charge favors before a hosted visitor dispatches one of your actions.