Automations

Automations let you run the same task on a schedule. Each automation stores a prompt, one project, one agent, and a schedule. When it fires, Krabby creates a background task and starts the agent automatically.

Creating an automation

1. Open Automations from the left sidebar
2. Click New Automation
3. Enter a title and prompt
4. Pick a project
5. Choose an agent
6. Choose Worktree or Direct
7. Set a schedule
8. Click Create

Use ⌘/Ctrl+Enter to create quickly.

Schedule types

Krabby supports four schedule types:

• Hourly
• Daily
• Weekly
• Monthly

Automations run in the background and appear in the Active list on the Automations page.

Worktree or Direct

Worktree creates a separate git worktree for each run, just like a normal task. This is the safer default because changes stay isolated from your main checkout.

Direct runs against the main project checkout without creating a new worktree.

If your project needs preserved files, setup scripts, shell setup, or tmux configuration, set that up in Project Configuration first.

Managing automations

Each automation row supports:

• Run now
• Pause / Resume
• Edit
• Delete

When an automation runs:

• a background task is created
• the selected agent starts automatically
• the task appears in the Automation Tasks section
• the run count opens the run log history

Important behavior

• Krabby must be open for automations to run on time. Automations are scheduled by the app, not by your operating system.
• If Krabby was closed during a scheduled run, it will catch up once when you reopen the app.
• Each automation belongs to a single project.
• Frequent schedules can create a lot of tasks and worktrees. Review and clean up old runs regularly.

Recommended workflow

Before scheduling an automation, test the prompt in a normal task first. Make sure it behaves the way you expect, then turn it into an automation.

Start with a slower schedule like daily or weekly before moving to something more frequent.

If the automation starts local servers, use KRABBY_PORT in your Project Configuration so parallel runs do not collide.

Good examples

• Daily code review
• Dependency update checks
• Docs coverage checks
• Security scans
• Performance audits