CropPilot Configuration

CROPPILOT.md is a per-tenant configuration file that customizes how CropPilot behaves. It lets you define workflows, skip confirmation prompts, and set up post-launch automation — all in plain Markdown.

Where to Edit

CROPPILOT.md is managed in the orchestrator dashboard:

1. Open the orchestrator at your deployment URL
2. Go to Settings
3. Find the CROPPILOT.md section
4. Click Edit CROPPILOT.md

Your configuration is stored in the browser and sent to CropPilot as part of its system instructions on every request. Maximum length is 10,000 characters.

How It Works

When CropPilot receives a message, it loads your CROPPILOT.md content as mandatory instructions that override its default behavior. CropPilot will execute every step you define in order — it won’t skip steps or stop early. Safety requirements (confirming destructive operations like stop/remove) still take priority.

Directives

Auto-Launch

By default, CropPilot shows a launch summary and waits for your confirmation before creating a container. Add the auto-launch directive to skip the confirmation:

## Launch Settings

auto-launch

With auto-launch enabled, CropPilot still resolves all values (worker, image, name) and shows a brief summary, but proceeds immediately without waiting for “yes.”

Post-Launch Workflow

Define what CropPilot should do automatically after launching a container. Without a workflow, CropPilot asks if you’d like to open a terminal. With a workflow, it executes your steps instead:

## Post-Launch Workflow

1. Start Claude Code in the container with `--dangerously-skip-permissions`
2. Open the terminal so I can watch

CropPilot will follow these steps sequentially after a successful launch, loading the appropriate skills (background-exec, interactive-exec) as needed.

Example

Here’s a complete CROPPILOT.md that auto-launches containers and starts the AI agent automatically:

## Launch Settings

auto-launch

## Post-Launch Workflow

1. Start Claude Code with --dangerously-skip-permissions
2. Open the live terminal

## Preferences

- Always use terminal images, not display images
- Default to 8 GB memory for containers
- When I say "plant", treat it as a launch request

Tips

• Keep instructions clear and actionable — CropPilot follows them literally
• Use numbered lists for sequential workflows
• The Preferences section is free-form — CropPilot interprets it as behavioral guidance
• You can reset to defaults at any time from the Settings page
• Changes take effect on the next CropPilot message — no restart needed