How to schedule Claude Code to run automatically

Issue summaries, maintenance reviews, and documentation checks are repeatable prompts that can become saved jobs. Aiola Automations keeps each job with its workspace, schedule and run history. Return to the results to decide what needs follow-up.

Open Automations inside the workspace that owns the work. Create a job from scratch or use an in-app template, then save the prompt and execution settings. Templates cover areas such as maintenance, documentation, GitHub, and release work; review the selected template before running it.

• Schedules: Daily, Weekdays, Weekly, Interval, Manual, or Custom RRULE, with a configured timezone. Jobs can be Active, Paused, or Disabled.
• Provider choice: select an enabled provider and model per automation. Reasoning, Fast Mode, and context controls depend on provider support.
• Workspace agent: select a saved agent with its instructions, compatible skills, and memory. Those instructions and memory stay scoped to that workspace.
• Execution: Local uses the workspace checkout; Worktree uses a separate checkout. Choose according to whether the job should share the project’s working files.
• Run history: inspect the next and last run, result, run count, status, duration, output, errors, and linked threads from the automation detail page.

Prompts can mention files, tasks, agents, issues, and pull requests. Follow a run’s linked thread to inspect the work. Create a workspace task for any follow-up, including the relevant context. Tasks can start a configured agent workflow and move through Human Review and Create PR stages.

Jobs run on your desktop: keep Aiola running and the computer awake for scheduled starts. Central Home surfaces recent and upcoming automation activity, and Central Calendar shows schedules across workspaces. Editing stays on the workspace’s Automations page.

A first automation could review repository dependencies and summarize proposed updates and compatibility risks. Instruct it to avoid edits, commits and publications. This gives you a defined output to evaluate before scheduling repeated runs.

1. Open the repository workspace’s Automations page and create a job with a focused prompt.
2. Choose Claude Code and an available model, review any workspace agent’s instructions, and select Local or Worktree execution.
3. Start with Manual scheduling and run the automation from its detail page.
4. Review the output, errors, duration, and linked thread; inspect diffs and run relevant checks if any files changed.
5. Adjust the prompt, then choose a recurring schedule and timezone once the result meets your needs.

Use the same manual-run-and-review process when changing the provider, agent, or scope of an existing job. The Automations docs describe the schedule and execution controls.

• Define the scope. Name the files or records to inspect and the expected output; state whether edits, commits, or publication are allowed.
• Check the workspace and agent. Confirm the repository, saved instructions, and provider-compatible skills before running.
• Choose the execution location. Use Worktree for separate working files when appropriate; review each branch because worktrees do not eliminate merge conflicts.
• Check provider access. Confirm the selected CLI is installed and authenticated using Central Settings → Providers.
• Check the schedule. Confirm the timezone and keep Aiola running on an awake desktop for scheduled starts.
• Review results. Inspect run history, errors, linked threads, diffs, and relevant checks before accepting changes; pause the automation while adjusting it.

Aiola supports six agent CLIs: Claude Code, Codex, Cursor, Grok CLI, OpenCode, and Antigravity. Each automation selects its own enabled provider and model. Use Claude Code for recurring issue summaries and Codex for weekly maintenance reviews in the same workspace. Give each separate prompts and schedules. Both use your own provider access, with no token markup from Aiola.

Reuse a workspace agent where its instructions and skills fit the job. Linking a skill locks the agent to that skill’s compatible provider; remove the linked skills before switching provider families. Agent memory belongs to the workspace rather than a shared memory across projects.

Threads, tasks, notes, and automations are stored locally. Prompts and file context go to your chosen AI provider; Aiola does not proxy, store, or resell that traffic. GUI Lifetime includes custom automations and non-hosted presets. Presets requiring hosted Analytics, App Logs or Feedback need Pro or trial. See pricing for access options.

Download Aiola for macOS 12+ or Windows 10+ (64-bit), then confirm the CLIs you plan to use in provider settings. Run and review each new automation manually before scheduling it.

Choose cron or CI if you prefer to configure the scheduler and execution environment yourself. Aiola provides workspace-scoped settings, saved agents, and run history for recurring jobs on your desktop.