GoLocomotiveExtend your app
Bigger changes: new kinds of data, new screens, new actions, links to other services. How to ask, and what your app is made of.
On other platforms, you extend an app with add ons from a store, or with a small panel that runs inside someone else's system under strict limits. In GoLocomotive, your app is its own program. A bigger change is a request like any other, and the agent changes the app itself: its data, its screens, its server.
What your app is made of#
| part | what it holds | you ask for |
|---|---|---|
| the schema | each kind of record, its fields, its links to other records, its rules | "a client has several sites", "staff see only their site" |
| summaries | computed lists over your data: totals per month, late orders per site | "a page with the revenue per month and per site" |
| the screens | lists, record pages, forms, dashboards, documents | "a dashboard for the morning meeting" |
| the server | checks before a save, steps after it, scheduled tasks, actions behind a button, calls to other services | "mail the invoice when an order is delivered" |
| the AI tools | what your own AI can do in the app | "let the AI create tickets but never delete them" |
Because each app runs alone, nothing limits it to a sandbox inside a shared system: it has real database columns and indexes, server code, and a full screen framework. The limits are your rules and your review.
How a bigger change goes#
- Describe the result and who uses it. A short paragraph, as in Your first week.
- Answer the agent's questions. For a new kind of data, expect one or two: what is required, who sees it.
- Judge in steps. A bigger change comes as several cards: the data and its list first, then the screens, then the automations.
- Release when the whole is ready. Approved cards wait under Unreleased until you release.
A change to existing data#
Adding a field or a new kind of record is safe: the app adds it at its next start. Removing or renaming a field that holds data, or changing its type, needs a written migration step. The app refuses to start without one, so data is never dropped by accident. The agent writes the step, and it shows in the card.
Pages in this section#
- What to ask for: four example requests and what the agent builds for each.
- Connect other services: accounting tools, payment providers, mail, storage, webhooks.
- The agent kit: the rules our agents follow in every app.