Amodal Cloud
Amodal hosts agents defined by source files: instructions, API connections, knowledge, tools, stores, and evals. Source lives in a connected Git repository or in Amodal-hosted source versions, and starts with amodal.json. Amodal builds and deploys the agent, serves its chat UI or custom app, and records sessions, tool calls, logs, and usage.
Build an agent
- Build with a coding agent: give your coding agent the setup prompt.
- Project Structure: where each file belongs.
- Run locally to try an agent on your machine.
- Build a support agent: a complete example against a public demo API.
- Source & deploy in Amodal: create, deploy, and select production in the app.
Core concepts
| Concept | Meaning | Example |
|---|---|---|
| Agent | A deployed definition of instructions and capabilities. | support-agent |
| Session | One conversation, including messages, tool calls, approvals, and usage. | A ticket investigation |
| Scope | An identifier that labels sessions and partitions memory, non-shared runtime stores, and scoped credentials. | tenant:acme |
| Scope context | Facts the application supplies for the current turn. | { "ticket_id": "123", "page": "support" } |
| Named agent | A prompt and a selected set of capabilities under agents/<name>/. | review |
Use scope_id to identify the application boundary and session_id to continue a conversation. Several sessions can share a scope. Sending the same scope_id without its session_id starts a separate conversation.
Scope context is information for the model, not an authorization claim. A runtime token minted with a scope_id confines chat and session history to that scope, so your backend must mint each token only for a scope the user may access. Tools and connections must also enforce tenant access; see Embedding & Multi-tenancy.
Deploy, test, and embed
- Evals: check behavior before deploying changes.
- Providers: choose models and configure provider access.
- Authentication: control access to the hosted app and runtime.
- Deployment API: deploy, activate, promote, and roll back.
- React SDK: embed chat and agent data in your application.
- Runtime Apps: deploy a custom frontend at the agent's URL.
- Runtime Server: call chat endpoints and consume streaming responses.