Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Introduction

Amodal hosts agents defined by source files. The files describe the agent's instructions, API connections, knowledge, tools, stores, and evals. You can start from a template with source stored in Amodal, or connect a Git repository.

Amodal builds and deploys the agent, serves its chat UI or custom app, and records sessions, tool calls, logs, and usage.

How It Works

  1. Define the agent. Add an amodal.json manifest and the files described in Project Structure.
  2. Configure the deployment. Choose a model, set secrets, and configure access in Amodal.
  3. Build and test. Deploy a source version, chat with it, and run evals.
  4. Select production. Make a tested deploy active so the persistent agent URL serves it.
  5. Inspect and improve. Review sessions and traces, edit the source, and deploy again.

During a conversation, the model can call the tools available to the agent, use their results, and answer the user. Skills provide instructions for particular tasks. Named agents can limit the tools, connections, skills, and stores available to a workflow.

Core Concepts

ConceptMeaningExample
AgentA deployed definition of instructions and capabilities.support-agent
SessionOne conversation, including messages, tool calls, approvals, and usage.A ticket investigation
ScopeAn identifier that labels sessions and partitions memory, non-shared runtime stores, and scoped credentials.tenant:acme
Scope contextFacts the application supplies for the current turn.{ "ticket_id": "123", "page": "support" }
Named agentA prompt and a selected set of capabilities for a workflow.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 starts a separate conversation unless you also pass its session_id.

Scope context supplies information to the model. Tenant isolation requires backend authorization for each scope, session, and operation, even with scoped runtime tokens. Tools and connections must also enforce tenant access; see Embedding & Multi-tenancy.

Next Steps