CompanyOS automation runs hourly, on a cron you can set

Agno's CompanyConfig now takes a cron_expr that controls how often CompanyOS checks Ready Tasks and authorized Routine proposals. AgentOS writes that value to the runtime-owned Company automation schedule at startup, and the default "0 * * * *" fires at the top of every hour.

Earlier releases created the schedule with a one-minute cron. On the first start after the upgrade, AgentOS finds the old * * * * * row, rewrites its cron and recomputes next_run_at. We started AgentOS three times against one SQLite database, once on the previous release and twice on this one:

With the default, a Ready Task or an auto-accepted Routine proposal can wait up to an hour for pickup. A person can still start a Task right away with POST /company/tasks/{task_id}/runs. A deployment that wants the old pace sets the cron back:

agent_os = AgentOS(
    db=db,
    company=CompanyConfig(cron_expr="* * * * *"),
    scheduler=True,
)

CompanyConfig refuses an empty value when you build it. Anything else that is not a cron expression builds fine and is caught at AgentOS startup, by the scheduler's own cron validator, before the poller runs. Both errors below are real output:

# raised by CompanyConfig
CompanyConfig(cron_expr="")
ValueError: cron_expr must be a cron expression
 
# raised when an AgentOS carrying this config starts up
CompanyConfig(cron_expr="every hour")
ValueError: Invalid cron expression: every hour

This release also renames the six Company tools that act on a single Product. Models see the new names, and the earlier names no longer exist, so update any agent or Routine instructions that mention them. The methods on CompanyTools change the same way, including the async versions with an a prefix such as aread_product_source. Company-wide tools and HTTP routes keep their names.

See the cookbook, and learn more about the AgentOS scheduler in the documentation.