schedules

Create a schedule

Turn the user's description into scheduled work in the current workspace. Research what is available before asking questions. Ask only for essential details you cannot discover or reasonably decide from the request.

Choose the destination

By default, schedule a message in this conversation. “Remind me”, “check later”, “keep watching” and “schedule yourself” mean continue this chat. Supply name, schedule and prompt; the tool resolves the current chat from its signed context. Choose another existing chat with targetSessionId only when requested. Its model, tools, machine and attachments apply at run time, so do not copy those settings into the schedule.

Use reusable_session or new_session_per_run with agentConfig only when the user requests separate-agent work. Sessionless calls require an explicit destination or a separate-agent mode.

For separate-agent work, use agentConfig.executionTarget: "workspace_default" unless the user chose a specific machine or backend. Each new run chat resolves the current workspace default; a reusable chat keeps its first machine. Explicit machineTarget or sandboxBackend pins placement and cannot be combined with executionTarget. An unavailable machine is a blocker, never permission to switch computers.

Discover what the task needs

• Use scheduled_tasks_list to avoid duplicating an existing schedule. Follow pagination when needed and use scheduled_tasks_get for a relevant task's details. A list summary is not its complete configuration.
• If the work needs a repository, use github_repositories_list to find the authorized repository and select the required resources.
• If the scheduled agent needs credentials, use secret_search to find the saved item and write its reference (for example {{secret:GitHub/token}}) in the prompt. Save it to the workspace with secret_save or secret_move when the schedule runs without you; never copy secret values into prompts.
• If it needs an integration such as Slack or Sentry, use capability_catalog_search and the available tool discovery to find the capability and exact operations. Follow returned connection/setup and approval requirements. Do not claim that discovery means the integration is ready.
• For posting as the workspace Slack bot, verify the available bot and channel through its tools. Record the exact Slack workspace and channel in the task instructions; use an explicit connection ID when multiple bots are available. Scheduled and interactive work use the same bot capability. No separate schedule-specific posting setting is required. Never substitute a personal account when the user requested the bot.