Skip to main content
Give a Paradime DinoAI agent a task to run as part of a Bolt schedule, so an autonomous agent runs on a cron schedule, on PR merge, on an upstream job’s completion, or any other Bolt trigger. Bolt schedules agents natively: when the trigger fires, Bolt dispatches the agent run directly inside your workspace. There is no API key, SDK, or CLI setup involved.

​
Prerequisites

  • A programmable agent, either defined under .dinoai/agents/<name>.yml in your repository or built in the app from the Agents page (see Creating Agents in the App).
  • A connected git repository. A schedule that only runs agents doesn’t need a data warehouse connection or a dbt™ project.
No API keys required. The command runs natively inside your workspace, so there are no credentials to set on the schedule. Existing schedules that still set PARADIME_API_ENDPOINT, PARADIME_API_SECRET, or PARADIME_WORKSPACE_UID as environment variables keep working unchanged, and you can remove those variables.

​
Usage

Add the Run DinoAI Background Agent command to your schedule, then:
  1. Select the Agent name from the dropdown. The list includes agents from the YAML files in .dinoai/agents/ on the configured branch as well as agents built in the app.
  2. Describe the Task you want the agent to complete (for example, “investigate why the run failed and propose a fix”). Be specific and reference concrete inputs like table names or time windows.
  3. Click Add command.
You can also start from the agent: on the Agents page of the DinoAI Agent app, click Schedule on an agent’s row. This opens a new Bolt schedule with the command already added and the agent pre-selected.

​
What happens on a run

  • Bolt dispatches the agent run natively and waits for it: the command blocks until the agent reaches a terminal state, and the Bolt run inherits the agent’s success or failure.
  • The agent’s messages stream into the command log, so you can follow progress live in the Bolt run logs.
  • The session also appears in the DinoAI Agent sessions panel under the Bolt source, so scheduled runs are easy to tell apart from API or Slack sessions.
  • Overlapping runs. If every command in the schedule is a DinoAI agent command, up to 5 runs of the schedule can be in progress at once, so a cron fire, an API call, or another trigger starts its own run even while an earlier one is still working. At 5, a manual or API trigger is refused and a cron fire is skipped. Schedules that mix agent commands with other commands run one at a time. The Run button stays disabled while the latest run is in progress.
Each run starts a fresh agent session with the configured task as its first message. It does not resume previous sessions.

​
Learn more