An app is a small web front end that runs inside an Agent Serve workspace. You write the screens your team needs — a deal desk, a field visit log, a support queue — and the workspace provides everything around them.
What the workspace gives you
You write only your domain code. The rest comes from the workspace the app is installed in:
| You get | How |
|---|---|
| Sign-in, people and roles | People open the app from the workspace, already signed in. The app reads who they are and their role with useViewer(). |
| Data | Read and add rows in Tables, query the semantic model, and read or create workspace Files. |
| Models | Run deployed workflows, hand tasks to Relays, or open Chat with a question. Each one uses the models and integrations already set up in the workspace. |
| Your own logic | Ship code tools with the app: functions that run on Agent Serve, give the same answer every time, and can be called by the app, Chat, Relays and workflows. |
| Security | The app acts as the person using it, narrowed to what its manifest names. It runs in a sandboxed frame with no network access of its own. See Security model. |
| Metering and audit | Paid work an app starts, including its code tool runs, is counted against its monthly budget, and every write and tool run is in the audit trail. |
There is no server to run, no login to build, and no database to provision.
How it fits together
- Manifest.
agentserve.app.yamlnames the app, its pages, what it may reach, and what to create on install. See Manifest reference. - Bundle. You build the front end into static files (HTML, JavaScript, CSS, images). The CLI packs them with the manifest into an archive.
- Draft version.
agentserve app deployuploads the archive as a draft version of the app. Or connect a repository, and each push builds a draft version on Agent Serve. Where the browser IDE is on, you can also edit and push from the browser. - Publish. A workspace admin publishes the draft, which makes it installable:
agentserve app publish <version>. - Install. An admin installs a published version in a workspace. The install creates the tables, rules and Relays the app declares, if they are missing.
- Open. People open the app from the Apps section of the workspace. Admins can pin it to the rail for chosen roles or permission groups.
Apps are turned on per workspace or organization. If you do not see the Apps section, Apps is not on for your workspace yet, or your permission group does not include it.
An app can also provide dashboard panels and Chat cards: small HTML views that render in the same sandboxed frame, inside a dashboard or a Chat reply.
Where to start
Quickstart
Create, run, deploy, publish and install an app.
Templates
Seven starting points, from a blank app to a knowledge assistant, and two complete example apps.
Manifest reference
Every field of agentserve.app.yaml.
App SDK
The client, React hooks, errors and limits.
Security model
What an app can reach, and who approves it.
agentserve app
The CLI commands for building and running apps.
Code tools
Functions that ship with your app and run on Agent Serve.
Deploying from Git
Build a draft version on every push from GitHub or GitLab.
Browser IDE
Edit an app in VS Code for the web with a live preview. A preview feature.