Workspace

Automation

An automation is a prompt that a coworker runs on a schedule, without you starting it. Use it for repeated jobs such as a standup digest, a dependency audit or a weekly summary. Each run produces a report you can open afterwards.

Creating an automation for a project.

Project and group automations

Scope What a run works on
Project The project's linked folder. The run can read and change code on its own branch
Group The group's boards and notes, across its projects. The run makes no code changes

A project needs a linked folder before an automation can change its code. In a group where AI-DLC is in force, automations make no code changes, and the templates that edit code are disabled.

Create an automation

Automations run as a coworker, so you need at least one. You can create one from inside the editor with + Create a co-worker.

  1. Open a group or project and choose New automation, or open its Automations list and select + New Automation.
  2. Choose Start blank, or pick a template and select Use template.
  3. Enter a name and write the prompt: describe what the agent should do.
  4. Under Scope, choose the project or group.
  5. Under Run as, choose the coworker.
  6. Under Repeats, choose Hourly, Daily, Weekdays, Weekly or Custom. Custom takes a cron expression in the order minute, hour, day, month, weekday.
  7. Choose the Timezone. The editor shows the next run times.
  8. Set the options in the table below.
  9. Select Create automation.
Option Default What it does
Enabled On Runs on the schedule. Turn off to pause
Notify On Sends a notification when a run completes
Catch up missed runs On If Clauge was closed at a scheduled time, runs once on next launch. When off, the missed run is skipped
Timeout 30 min Stops a run that takes longer. Choices: 10 min, 30 min, 60 min
The automation editor.

Templates

A template fills in the prompt and schedule. You still name the automation and save it. Templates that need code appear only for a project. Templates that work across projects appear only for a group.

Category Project templates Group templates
Status reports Standup digest, Weekly team update, Weekly PR recap Group standup digest, Weekly group summary
Release prep Changelog draft, Release notes draft, Pre-release audit Release notes draft, Release checklist
Code health Nightly code health, Dependency audit, Test triage, Daily bug scan, Docs freshness Stale cards sweep
Growth Skill growth suggestions, Weekend side project
The template gallery.

Run and manage automations

Each row in the Automations list has these controls:

Control What it does
Switch Enables or disables the automation
Run now Starts a run immediately
Edit Opens the editor
Delete Deletes the automation after you confirm
Show recent runs Expands the row to list its runs

A project automation whose project has no linked folder shows paused · needs folder. Its scheduled runs are held back until you link a folder.

To stop all scheduled runs at once, turn on Pause all scheduling under Settings → Automations. The list then shows Scheduling paused.

An automation with its recent runs.

Read a run

Click a run to open it. The page shows the status, how it was started (Scheduled, Manual or Catch-up), the coworker, the report and, under Raw transcript, the full output.

Status Meaning
Queued Waiting to start
Running In progress
Success Finished without problems
Issues Finished and reported problems
Failed Stopped with an error
Timed out Exceeded the timeout
Cancelled You cancelled it
Skipped A scheduled run that did not start

Actions on a run:

Action When
Cancel While the run is in progress
Re-run Starts a new run of the same automation
View diff Project runs. Shows the file changes on the run's branch
Create PR Project runs with changes. Needs a GitHub or GitLab account connected in Settings. Once created, the button becomes Open PR
Delete run Removes the run from the list

A group run shows Group run — no code changes in place of the diff.

What’s next