Skip to main content
The runagent.config.json file is the heart of your RunAgent project. It defines how your agent is configured, deployed, and executed.

Basic Structure

Configuration Fields

Core Fields

string
required
Unique identifier for your agent. Used in deployment and SDK initialization.
  • Must be lowercase
  • Can contain letters, numbers, hyphens, and underscores
  • Maximum 50 characters
string
Human-readable description of what your agent does. Displayed in dashboards and listings.
string
required
The AI framework your agent uses. Supported values:
  • langgraph
  • crewai
  • agno
  • letta
  • custom
string
required
Semantic version of your agent. Follow SemVer format.

Template Information

string
Name of the template used to create this project. Helps with updates and migration.
object
Source information for the template:

Agent Architecture

object
required
Defines how RunAgent interacts with your code:

Environment Variables

object
Environment variables for your agent. Supports two formats:
  1. Dynamic substitution: "${VAR_NAME}" - Reads from environment
  2. Fixed values: "fixed_value" - Uses the literal value
Never hardcode sensitive values like API keys. Always use dynamic substitution.

Entrypoint Types

Generic Entrypoint

Standard request/response pattern:
Configuration:

Streaming Entrypoint

For real-time response streaming:
Configuration:

Advanced Configuration

Multiple Entrypoints

You can define multiple entrypoints for different use cases:

Environment Variable Patterns

Validation

RunAgent validates your configuration on:
  • runagent init - When creating a project
  • runagent serve - Before starting local server
  • runagent deploy - Before deployment
Common validation errors:
Ensure all required fields (agent_name, framework, version, agent_architecture) are present.
Check that the module path is correct and the file exists.
Use one of the supported frameworks or "custom" for others.

Best Practices

Use Semantic Versioning

Follow SemVer for your version numbers to track changes properly

Document Entrypoints

Add comments in your code explaining what each entrypoint does

Environment Variables

Never hardcode secrets. Always use environment variable substitution

Validate Locally

Test your configuration with runagent serve before deploying

Example Configurations