Configuration
Agents are configured through the CLI and dashboard. Here's what each option means.
Creating an agent
Use maritime create to provision a new agent. You can pass options inline or follow the interactive prompts:
terminal
maritime create -n my-agent -t crewai --tier extendedAgent options
| Option | Flag | Required | Description |
|---|---|---|---|
| name | -n, --name | Yes | Unique agent name |
| template | -t, --template | No | Template ID (interactive picker if omitted). See maritime templates |
| framework | --framework | No | Agent framework: crewai, langgraph, openclaw, docker, or custom (default: custom) |
| tier | --tier | No | Pricing tier: smart ($1/mo), extended ($5/mo), or always_on ($10/mo). Default: smart |
| env | -e, --env | No | Initial environment variables as KEY=value (repeatable) |
Environment variables
Environment variables are managed through the CLI or the dashboard. Variables are marked as secret by default.
terminal
# Set a secret environment variable
maritime env set my-agent OPENAI_API_KEY=sk-...
# Set a non-secret variable
maritime env set my-agent LOG_LEVEL=debug --no-secret
# List all variables
maritime env list my-agent
# Remove a variable
maritime env remove my-agent LOG_LEVELTriggers
Triggers (cron, webhook, Telegram, Discord, email) are configured through the dashboard. Triggers wake sleeping agents automatically when fired.
Resource limits
Resources (memory, CPU) are allocated automatically based on your tier:
| Tier | Memory | CPU | Price |
|---|---|---|---|
| smart | 512 MB | 0.25 vCPU | $1/mo |
| extended | 1 GB | 0.5 vCPU | $5/mo |
| always_on | 2 GB | 1.0 vCPU | $10/mo |