Skip to main content

Synopsis

Description

The deploy command handles agent deployment workflows. Currently supports local deployment, with remote cloud deployment coming soon.
Note: Remote deployment features require authentication and are coming soon. Local deployment is fully available through the serve command.

Options

Current Usage

Local Deployment

For local deployment, use the serve command directly:
The --local option internally calls the serve command with automatic:
  • Port allocation
  • Database management
  • Agent registration

Coming Soon: Remote Deployment

Remote Deployment Workflow (Coming Soon)

Planned Remote Features

1

Authentication Setup

2

Agent Upload

3

Remote Start

4

Full Deployment

Local Deployment Process (Available Now)

Using runagent serve for local deployment:
1

Validation

  • Checks runagent.config.json
  • Validates entrypoints and framework
  • Verifies agent structure
2

Database Registration

  • Registers agent in local database
  • Allocates unique port automatically
  • Handles capacity management (5 agents max)
3

Server Start

  • Starts FastAPI server
  • Configures endpoints
  • Enables real-time execution
4

Ready for Use

  • Agent available at local endpoint
  • Can execute via Python SDK or CLI

Examples

Current Local Deployment

Local Deployment via Deploy Command

Future Remote Examples (Coming Soon)

Output

Local Deployment Output

Future Remote Deployment Output (Coming Soon)

Local Database Management

Local deployments are managed through a SQLite database:
Capacity Limits:
  • Maximum 5 agents simultaneously
  • Automatic port allocation (8450-8454)
  • Replace oldest agent when at capacity

Configuration

Agent Configuration

In runagent.config.json:

Future Remote Configuration (Coming Soon)

Validation Checks

Before deployment, RunAgent validates:

Error Handling

Common Local Deployment Errors

Troubleshooting

Local deployment automatically handles port allocation:
  • Starts from port 8450
  • Increments if port is busy
  • Maximum 5 agents (ports 8450-8454)

Best Practices

  1. Test with Serve: Always use runagent serve for local development
  2. Monitor Capacity: Check runagent db-status --capacity regularly
  3. Clean Up: Remove unused agents with runagent delete
  4. Version Control: Keep runagent.config.json in version control
  5. Environment Setup: Configure .env files properly

Migration Guide

Current Workflow

Future Remote Workflow (Coming Soon)

See Also