Patch on top of v2026.05.31.1 — three coordinated fixes so ABE companies don't get created into a "no way to make this autonomous without restarting" trap.
Bug 1 — mind_control start was silently broken
AutonomousMind.start is async; the gateway called it without await in TWO places (the /mind start chat command and the mind_control web command). The coroutine was created and discarded — the start button silently no-op'd while the caller saw "Mind started" with nothing actually running.
Fix: added the missing awaits in both code paths.
Bug 2 — Enabling the mind required a config edit + restart
Before: _autonomous_mind was None whenever autonomous_mind.enabled: false in config.yaml, so the only way to turn it on was to edit the config and restart the agent.
Fix: AutonomousMind is now always instantiated. The enabled flag controls AUTO-START at gateway boot only (gated in cli/gateway_cmd.py). The operator can flip the mind on at runtime via:
- The web Mind page Start button
- The
/mind startchat command - Direct
mind_controlWebSocket command
No restart needed. enabled: false just means "don't auto-start" — the control surface stays live.
Feature — company_create prompts to enable the mind
When the operator creates a company while the mind is off, company_create now returns mind_running: false plus a mind_suggestion field telling the agent to ASK the operator if they'd like to start the mind. Without mind, a new company can only act when chat-driven or scheduled — there's no autonomous rotation across companies, which is what most operators want when they create an ABE.
The suggestion surfaces naturally through the agent's normal "explain what the tool returned" loop. Mechanism: _CompanyToolBase gains an optional _agent reference, injected via the existing hasattr-driven company-tool deps block.
Upgrading
./update.sh
./start.sh --web
After restart:
- The Mind page Start button works
- Creating a new company while mind is off → the agent will ask if you want to enable autonomous mode
autonomous_mind.enabled: falsein config no longer locks you out of runtime enablement
Everything in v2026.05.31 + v2026.05.31.1 is included.
Full diff: v2026.05.31.1...v2026.05.31.2