Condor’s general routines
These live in the top-levelroutines/ folder. The Condor chat assistant, the Routines page and Telegram /routines can run them. Agents can’t.
Every one-shot routine above except
error_test builds an HTML report when it runs.
Shared routines
These live inagents/_shared/routines/. The Condor chat and every agent can run them. They appear under the Condor chip on the Routines page.
Agent routines
The shipped agents carry their own routines inagents/<slug>/routines/. Only that agent can run them, and they appear under the agent’s chip on the Routines page.
How price_monitor works
price_monitor is the shipped example of a continuous routine:
- Its config is
connector(defaultbinance),trading_pair(defaultBTC-USDT),threshold_pct(default1.0) andinterval_sec(default10). - It tries to send a Telegram message when it starts, then checks the price every
interval_secseconds. - When the price moves
threshold_pctor more since the previous check, it sends an alert. - On every check it rewrites one live report with the current price, high, low, total change, runtime, alert count and the last 50 checks.
- When you stop it, it sends a summary of how long it ran, how many checks it made and how many alerts it sent.
Adding your own
You don’t need to restart Condor. New and edited files are picked up the next time routines are listed. See Creating Routines.
Don’t edit the shipped files in
routines/ or agents/. They are tracked by git and belong to Condor, so keep your changes in .condor/. To change a shipped shared or agent routine, copy it to the same name under .condor/agents/, where your copy takes precedence.
