Skip to main content
Configure Evolve before the first run. This example gives Codex a sales CSV, reporting instructions, and a reusable skill, then retrieves its report. Complete the SDK setup first, including installation and EVOLVE_API_KEY. Run the example from your project directory.

Add a reporting skill

A skill is a folder containing a SKILL.md file. Create skills/reporting/SKILL.md with these contents:
skills/reporting/SKILL.md

Configure and run

type selects the harness, the CLI agent that works in the sandbox. model selects the model it calls. See models and effort levels for supported choices.
The first run() creates the sandbox and uploads the files and skill. The finally block destroys the sandbox after you retrieve the report, including when a run fails.

Choose where files go

File mappings use destination paths as keys and file contents as values. Paths below are relative to the default /home/user/workspace directory. The example sends file contents directly. To send a local file, read it in your application and pass its text or binary contents in the same mapping.

Choose a sandbox

The example explicitly selects managed E2B. Change "e2b" to "daytona" or "modal" to use another managed provider with the same Evolve API key. If you omit the sandbox configuration, Evolve selects a provider from your environment: Your sandbox credentials take priority over managed E2B. If several provider keys are set, selection order is E2B, Daytona, then Modal. Keep EVOLVE_API_KEY set to continue using Evolve model access with your own sandbox account.

Reuse other skills

Replace "./skills/reporting" with another local skill folder or a Git reference, such as "anthropics/skills". A whole repository reference loads the skills it publishes; use a specific skill path when you only need one. Skills mount in the selected harness’s native skills directory. A local skill folder must contain SKILL.md; a skill name alone is not a built-in catalog.
Last modified on November 9, 2026