Company Manager can run Company Routines

Agno CompanyOS Routines now accept executor_id='company-manager-internal', and AgentOS resolves that ID from the AgentOS that owns the Company, then schedules POST /agents/company-manager-internal/runs.

Routine(
    name="weekly-review",
    executor_type="agent",
    executor_id="company-manager-internal",
    cron_expr="0 9 * * 1",
    timezone="Europe/London",
    instructions=REVIEW,
    auto_accept=False,
)

Earlier releases looked Routine executors up only in the reusable registry, which leaves the framework managers out on purpose, so this Routine failed at bootstrap. The old product-manager-internal ID failed the same way. We ran the same declaration on both releases with SQLite and no model call.

The /company/routines API gives the same answer: a 201 with that endpoint for Company Manager, and a 422 for OS Manager. Company Manager is the only framework manager allowed here. OS Manager, Platform Builder and Platform Manager can edit the platform, and a Routine runs unattended on Source content. Saved or user-defined components can't claim the reserved IDs, and a stale archived catalog row no longer collides with them.

The declaration works with or without OSManager. AgentOS always serves Company Manager at its own agent routes, and when OS Manager is on, the team gets a separate Company Manager member that carries OS Manager's member_tool_call_limit. Product Manager is now called Company Manager. AgentOS.product_manager still works as a deprecated alias of AgentOS.company_manager.

A Routine run by Company Manager keeps the usual limits. Company Manager has no scheduler tools, and it can't be accepted as a Task executor. Two reporting gaps are fixed for every Routine too. A denied update_company_status write now fails the run, and so does a Studio run_agent, run_team or run_workflow delegation that comes back with an error. If you call rehydrate_product or CompanyManager.create_routine from Python, pass agent_os=agent_os so the manager can be found.

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