Run the manager
The manager plans the account's next moves through its first active agent on a cadence you set: read the wake runs and their proposals, approve a run's proposals in one call or dismiss it with feedback the next run learns from, and read spend against the monthly allowance.
Settings hold the cadence and targeting. Where a standing agent is one brief, the manager is the desk that decides what runs.
Ask in plain words
- "plan this week's content now"
- "approve everything the manager proposed this morning"
- "how much of my agent budget is left this month"
- "run the agents twice a week instead of daily"
- "dismiss today's plan and tell it to lean into video"
From an agent host (MCP)
No MCP tool yet: call the REST routes below.
From code (REST)
Bearer API key with the scope each call names (auth, OpenAPI).
POST /api/manager/run(publish scope): Plan now through the first active agent.GET /api/manager/runs(read scope): Wake runs and their proposals.GET /api/manager/runs/{id}(read scope): One wake run.POST /api/manager/runs/{id}/approve(publish scope): Approve a run's proposals.POST /api/manager/runs/{id}/dismiss(write scope): Dismiss a run with feedback.GET /api/manager/settings(read scope): Cadence and targeting.PUT /api/manager/settings(write scope): Set cadence and targeting.GET /api/manager/budget(read scope): Spend, allowance, paused state.
From a terminal (CLI)
No CLI command yet.