Cron-triggered sessions never get Composio MCP tools attached (works fine in Telegram/TUI sessions)

[RUKE03]

Bug: Composio MCP server is not attached to the tool list for cron-triggered sessions, even though the same profile works fine for interactive (Telegram/TUI) sessions.

Environment: v0.18.0 (v2026.7.1), self-hosted on Railway. Also reproduced on v0.17.0 (v2026.6.19) before upgrading.

Setup: Single profile (default), Composio MCP server configured globally under /mcp, used by both a Telegram channel and a cron job.

Steps to reproduce: 1) Configure Composio MCP server globally (only one profile exists, no per-profile MCP config). 2) Trigger the cron job manually or let it run on schedule. 3) Open the resulting session transcript.

Expected: Composio MCP tools are callable, same as in an interactive Telegram session.

Actual: Session tool call fails with "Tool does not exist, available tools: process, terminal". After upgrading to v0.18.0, the agent does not even attempt the MCP tool call anymore, goes straight to terminal exploration, reports no Composio env vars and no MCP config found, then falls back to a broken output noting the integration is unavailable.

Already ruled out: Cron job Deliver To setting (tested Local, Telegram, origin - same failure on all). Railway environment variables (no Composio/MCP config there). Outdated version (upgraded HERMES_REF to v2026.7.1, confirmed via build logs, bug persists). Per-profile MCP attachment (only one profile exists total).

This suggests cron-triggered sessions start through a different code path than interactive/channel sessions, and that path does not wire up MCP servers into the tool list.

[RUKE03]

Additional evidence from live session transcripts on our instance:

Cron session ("RUKE Morning Briefing", Jul 03 17:10) - only a terminal tool was available. All 9 tool calls were the assistant trying to work around missing MCP tools via shell: checked for mcp binary (found, but "No Composio env vars"), tried pip install mcp[cli] ("typer is required"), looked for a config file ("No MCP config found"), tried the Composio CLI directly ("command not found"). Final output: "ACTION REQUIRED: The Composio MCP server needs to be configured and authenticated for this cron job."

Interactive session ("Gmail Draft Creation Test Successful", tagged tui) - the assistant called mcp_composio_COMPOSIO_MULTI_EXECUTE_TOOL directly as a native registered tool, no workaround needed, succeeded immediately.

Same bot, same deployment, same Composio config - only variable is session trigger type. Confirms the MCP registration step is skipped in the cron init path specifically. Saw the linked PR #57898 - will review.

[teknium1]

Thanks for the detailed transcripts and for linking PR #57898. This automated hermes-sweeper review found that the requested cron/MCP behavior is already implemented on current main.

• cron/scheduler.py:3150-3169 discovers configured MCP tools before constructing the cron AIAgent.
• cron/scheduler.py:3189 passes the resolved cron toolsets into that agent.
• hermes_cli/tools_config.py:1884-1900 adds globally enabled MCP servers to platform toolsets by default, including the cron fallback path.
• The implementation was added by 04918345ea31b1106d2ee6d4f42822f4f57616ee (fix(cron): initialize MCP servers before constructing the cron AIAgent (#21354)).

PR #57898's proposed fallback merge is redundant with _get_platform_tools already adding those enabled MCP server names.