Schedule ConsoleX tasks in Claude Code

Use /consolex:schedule in the Claude desktop app to run an added ConsoleX task on your computer at a chosen time. Claude Code does the work; ConsoleX records the delivery and, with automatic checks enabled, checks it against the task's saved criteria.

Local scheduling applies to both workflows. A needs the main Skill on this computer; B also has the option of scheduling in ConsoleX. Compare execution locations below, then follow the Desktop steps.

Choose where the schedule runs

	Schedule in ConsoleX	Schedule in Claude Code Desktop
What starts the run	ConsoleX	The Claude desktop app on the chosen computer
Where the work runs	ConsoleX	That computer's Claude Code environment and working folder
Task with its method saved in ConsoleX	Supported	Supported through the plugin
Task with its method in a local Skill	Runs in its coding agent; no ConsoleX schedule	Supported when that computer has the main Skill
Where to change or stop the schedule	The task's settings in ConsoleX	Claude desktop app on that computer

See Two kinds of tasks and Schedule a task in ConsoleX.

The integration described here uses local Desktop scheduled tasks. Anthropic also offers cloud schedules and CLI /loop; /consolex:schedule uses the Desktop scheduling tools. Local runs need the app open and the computer awake, and may start late or catch up after sleep. See Claude Code's scheduling documentation for current app behavior.

Before you start

1. Install and connect the ConsoleX plugin on the computer that will run the task. Use a Claude Code session in the desktop app with its scheduled-task tools available.

2. Open a session in the folder where the work should happen. The plugin prepares the schedule using this session's folder.

3. If the task needs ConsoleX tools or files, enable Tools and files for this computer under Settings → Coding agents. Check that the required connections are ready.

4. Add the task to this computer:

   /consolex:add Weekly research brief

5. Run it once using its /cx-… Skill. Check that it can read the materials, use the needed tools and deliver a checked result before scheduling it.

Create the schedule

In that desktop session, run:

/consolex:schedule Weekly research brief -- every weekday at 08:30

You can identify the added task by its name, task link or /cx-… name. If more than one matches, choose the intended task. If you leave out the time, Claude asks when it should run.

The plugin checks whether the task is already scheduled elsewhere, then gives Claude the task prompt to pass to the desktop scheduler. Confirm the time, this computer's local time zone, working folder and permission mode in the resulting schedule. This time zone is separate from your ConsoleX account's time zone.

After creation, check the schedule in the desktop app's Scheduled view and try Run now. Use its session history to inspect permissions or execution problems; use the ConsoleX task's Run history to inspect submitted deliveries and checks.

Keep the work's requirements with the task

The schedule identifies the task, time and working folder. Keep the method, delivery goal, publishing or sending requirements, approval rules and failed-check policy with the task:

• Method in ConsoleX: edit the task's saved instructions there.
• Method in a local Skill: edit the original Skill; keep the delivery goal and run rules in ConsoleX.
• Checks and automatic revision: change them in the task's checks settings.

Let the plugin generate the scheduled prompt rather than copying the business instructions into a second prompt. For example, “publish only after my approval” belongs in the task's rules; the schedule only needs to say which task to run and when.

Unattended runs and checks

In a scheduled run, nobody is present to answer the agent. Items that need your decision or verification are reported for you to review. This doesn't grant permission to take actions beyond the task's saved rules.

Automatic revision is off by default. If enabled, required output failures can trigger revision and another check within your chosen limit. Missing evidence or items needing review don't automatically trigger a rewrite. See After a check.

The desktop app's tool permissions still apply. A run can wait on a permission prompt even though it was scheduled successfully. Test the run and choose appropriate tool permissions before relying on unattended execution.

Change, pause or stop a schedule

• Change the time: run /consolex:schedule again with the same task and the new time in the desktop app. The plugin offers the existing schedule for updating; specify which one if several exist. An additional time is created only when you ask for one.
• Pause or resume: use the schedule's controls in the Claude desktop app. Ask Claude there to pause it if preferred.
• Stop it: delete the schedule in the desktop app. Removing the local task Skill with /consolex:remove is a separate operation and doesn't replace stopping a schedule.
• Change where it runs: stop the old schedule first, then open a session in the intended folder or computer and set it up there.

Changes made directly in the desktop app may reach ConsoleX on the next Claude Code prompt, session start or scheduled run. The ConsoleX display can therefore lag behind the desktop app.

Avoid duplicate schedules

A task should run on a schedule from one place. When the plugin can confirm an active schedule in ConsoleX or another computer, it refuses to create or enable another there. ConsoleX likewise blocks enabling its own schedule while a current local schedule is active.

In the ConsoleX task's settings, look for a notice such as Runs on a schedule by Claude on …. To switch locations, stop the schedule where it runs now, then set up the replacement.

These checks depend on reported state. If ConsoleX is unreachable, the plugin warns that it couldn't check; verify existing schedules yourself. Older or manually created schedules can still overlap. If the task runs twice, turn one off where it was created.

If an old computer no longer runs it, This computer no longer runs it releases that recorded schedule in ConsoleX. This only clears the record; it doesn't stop anything on the other computer. Stop the actual schedule if that computer is still in use.

Common problems

What you see	What to check
No scheduled-task tools	Use a desktop session with scheduling available. This integration doesn't create a persistent desktop schedule from an ordinary terminal session.
The schedule didn't run on time	Check the computer, desktop app, schedule status and desktop run history. A saved schedule isn't proof of a completed run.
The run is waiting	Open its Claude session and inspect permission prompts, missing materials or tools.
ConsoleX has no new delivery	Check whether the desktop run started and reached delivery, and whether /consolex:status shows a valid connection.
ConsoleX still shows the old schedule	Start a new Claude Code session or send a prompt to let the plugin sync, then refresh the task page.
The method Skill is missing	Restore or install the task's main Skill on that computer before starting it again.

Related

• Install and connect
• Run and check tasks
• Save a session as a task
• Schedule a task in ConsoleX