What problem does it solve? Setting up recurring automated tasks in APX requires choosing the right routine kind, writing correct schedule expressions, wiring pre/post shell hooks, and avoiding pitfalls like double Telegram replies — mistakes that silently produce no output or duplicate messages. ## Core Features & Use Cases - Kind selection guidance: Choose between heartbeat, shell, exec_agent, watch, super_agent, and telegram kinds based on whether the task needs tools, an LLM, or pure shell execution. - Schedule grammar: Use every:<N><unit>, once:<iso-8601>, or standard 5-field cron expressions to control when routines fire. - Pre/post command pipelines: Chain shell commands whose stdout feeds {{pre_output}} into prompts and whose LLM result flows to $APX_LLM_OUTPUT for delivery. - Use Case: Create a daily weather routine that fetches wttr.in data via a pre_command, has an agent write one friendly sentence with tools disabled, and delivers it through a Telegram post_command. ## Quick Start Ask the agent to create an APX routine named weather-bariloche in project acme that runs every 24 hours, fetches the weather with curl, and sends a one-sentence summary via Telegram.
