Prerequisites
- Node.js 20+ — nodejs.org
- Docker — docker.com (Docker Desktop on macOS/Windows, or Docker Engine on Linux). Not required if all agents use the host-user runtime.
1. Create a project
config.toml: project-level settings.env.toml: local environment binding (gitignored)package.json: with@action-llama/action-llamaas a dependencyCLAUDE.md: a symlink to an AGENTS.md file in the npm package that has everything your agent needs to know.mcp.json: MCP server config so Claude Code can interact with your agents
2. Create an agent
Add a “dev” agent that will implement Github issues when they are tagged with “ready-for-dev”:You can also use your agent, such as Claude Code, to create new agents! The CLAUDE.md in the project root has everything it needs to know.
3. Run
-w to enable the web dashboard:
What just happened?
- The scheduler scanned for directories with
SKILL.mdand found your agent - It built a Docker image with your agent’s tools
- On the first cron tick, it launched a container, loaded credentials, and started an LLM session
- The LLM received your
SKILL.mdinstructions and ran autonomously - When it finished, the container was removed and logs were saved
Key files
| File | Purpose |
|---|---|
config.toml | Project settings: named models, Docker limits, webhook sources |
agents/<name>/SKILL.md | Portable metadata + agent instructions |
agents/<name>/config.toml | Agent runtime config: credentials, models, schedule, webhooks, params |
Manual test run
Run a single agent once without starting the scheduler:What’s next
- Using Webhooks — trigger agents from GitHub events
- Dynamic Context — use hooks to stage context
- Deploying to a VPS — run agents 24/7 on a server
- Agents (concepts) — understand the runtime lifecycle
- CLI Commands — all available commands and flags