chimera serve

Run the messaging gateway on HTTP, Discord, Telegram, Slack or Signal. Requires a key. Add ``--cron`` to also fire scheduled jobs on a real clock — turning the reactive gateway into an agent that acts on time (the daemon that makes proactivity real). Pass ``--mcp`` to instead expose Chimera *as* an MCP server on stdio, so any MCP client (Claude Desktop, an IDE, another agent) can call ``chimera_solve`` / ``chimera_fuse`` / ``chimera_memory_search``.

Options

--hoststrdefault: '127.0.0.1'
Bind host.
--portintdefault: 8765
Bind port.
--model, -mstr
Override the model slug.
--max-stepsintdefault: 6
Max tool-calling steps per message.
--workspace, -wstrdefault: '.'
Workspace root for tools.
--fuseboolean
Route deep-reasoning turns through fusion.
--no-memoryboolean
Don't recall long-term memory.
--discordboolean
Serve on Discord (needs CHIMERA_DISCORD_BOT_TOKEN + the 'messaging' extra).
--telegramboolean
Serve on Telegram (needs CHIMERA_TELEGRAM_BOT_TOKEN).
--slackboolean
Serve on Slack (needs CHIMERA_SLACK_BOT_TOKEN + CHIMERA_SLACK_APP_TOKEN + the 'messaging' extra).
--signalboolean
Serve on Signal via a signal-cli-rest-api bridge (CHIMERA_SIGNAL_API_URL + CHIMERA_SIGNAL_NUMBER).
--cronboolean
Also run the cron daemon: fire scheduled jobs on the real clock (proactivity).
--cron-tickintdefault: 30
Seconds between cron scheduler ticks.
--mcpboolean
Serve Chimera AS an MCP server over stdio (solve/fuse/memory as tools).
--a2aboolean
Also expose an A2A endpoint on HTTP (agent card + task lifecycle).