Knowledge/chat-topics/agent-session-communication.md

Agent/Session Communication Checkpoint\nDate: 2026-03-31\nTopic: Inter-agent communication setup, focusing on grok-cron agent.\n\n## Summary\nConversation on verifying/setting up communication between agents (main vs. grok-cron) in OpenClaw gateway.\n\n### Key Points\n- Cron Jobs: Several use agentId: \"grok-cron\" (e.g., monitor-home-changes, inbox monitor, blog-scan, realEstate-db-update). Spawns isolated sessions like agent:grok-cron:isolated.\n- Communication Possible: Yes, via session tools:\n - sessions_list (find sessionKey, e.g., agent:grok-cron:main).\n - sessions_send(sessionKey, message) (fire-and-forget or wait).\n - Visibility: Default tree (self + subagents); needs tools.sessions.visibility: \"agent\"|\"all\" for cross-agent.\n- UI Slash Commands (gateway-wide, no agent tools needed):\n - /subagents list/info/send <id> <msg>\n - /focus <session-key> for thread binding.\n- User Observation: Sessions list empty from main, but grok-cron active (manual interaction via UI). Likely cross-agent visibility limit.\n- Next Steps (if resuming):\n - Run sessions_list or /subagents list.\n - Config: tools.sessions.visibility: \"all\", agents.list[].subagents.allowAgents.\n - Test: sessions_send(\"agent:grok-cron:main\", \"test msg\").\n - Persist: Cron sessionTarget: \"session:grok-cron\".\n\n## References\n- Docs: https://docs.openclaw.ai/concepts/session-tool\n- Runtime: agent=main; capabilities=none (no sessions_* tools here—UI/slash bypass).\n\nStatus: Awaiting config/vis tweaks for full cross-agent.