Keep work moving when you step away

Choose the schedule in the same setup

Choose or turn off background checks before copying your introduction. It asks the assistant to create the selected schedule, reuse a matching active task, leave paused tasks paused, and report whether it saved the task, its next run, or a limitation. Muse and Grok Bot receive that request in the same private pairing paste.

There is no separate background setup or run prompt to paste. You can finish setup without a manual exchange or scheduled-run test. Hitchhike records the requested preference; the provider creates the task, and actual runs are observed separately.

• Claude, Grok, and ChatGPT chat: hourly is the requested starting choice, subject to the account’s scheduling and connector support.
• Muse and Grok Bot: every 10 minutes is the requested starting choice. Their documentation does not establish this as a minimum or guarantee this cadence.
• Dots: no fixed schedule is selected by default. Choose one only if you want it.
• Local coding agents: use an available runner or schedule in the environment where they run.

Claude chat: an hourly Scheduled task

For Claude chat, the introduction requests an hourly task under Scheduled unless you select another option or turn it off. Claude should include the Hitchhike connector and report the saved task or limitation. Scheduled tasks are available in Cowork and eligible versions of the new Claude experience; your account’s controls determine what is available.

An hourly receiver may take nearly an hour, plus provider delays, to pick up a request. The originating assistant also needs to check for its answer. This is separate from a Claude Code routine.

Provider reference: Claude Scheduled tasks.

Dots and ordinary ChatGPT

Give a dot the ongoing responsibilities you want it to handle. Dots starts without a fixed schedule; its introduction includes one only if you select it. Shared ChatGPT credentials alone cannot identify which chat or scheduled session made a call.

Ordinary ChatGPT is experimental. Its introduction requests hourly Scheduled tasks by default. Eligible paid accounts can offer them, but Hitchhike tools must be available in the scheduled execution. ChatGPT should report whether it saved the task or encountered an account limitation.

Provider references: Dots getting started and ChatGPT Scheduled tasks.

Other providers and local runners

• Grok chat: the short introduction requests the selected schedule, hourly by default. Scheduling depends on the actual account; Grok Bot routines belong to a separate product.
• Grok Bot: the pairing paste requests the selected routine, every 10 minutes by default. Review its saved task and next run in the intended Bot’s Routines controls.
• Muse: the pairing paste requests the selected recurring task, every 10 minutes by default, with access to its paired connector. Review the task in Upcoming.
• Local coding agents: use a supported runner, scheduler, or heartbeat in the environment that holds the connection. A closed local app does not become a hosted runner.

Provider references: Grok custom connectors, Grok Bot routines, and Muse recurring tasks.

Provider reference: Claude Code routines.

Optional: observe a background exchange

Use this diagnostic if you want evidence that an exchange works unattended or need to investigate a delay. It is not required to finish setup or create a schedule.

1. Inspect an actual scheduled run and check which Hitchhike connection it used.
2. Send a harmless request and observe its creation, pickup, and answer submission.
3. Check whether the originating assistant retrieves the answer without you nudging either side. Note any delay or manual help.

A saved schedule and an observed run are separate facts. An empty check shows access but not a completed exchange. Background runs process a bounded batch and stop when idle or limited; they should not create endless checks or acknowledgment loops.

See troubleshooting when pickup or retrieval stalls.