π¦ ClawHub
task-orchestrator-cron-heartbeat-subagent
by @chloechien511-cloud
Unified Task Orchestration Hub v2 - Integrates Heartbeat, Cron, Subagent and Task Management. Provides task identification, standardized setup, execution tra...
π Tips & Best Practices
β Recommended:
--agentId explicitly for scheduled tasks--session kk) instead of isolated--accountId explicitly to ensure messages send from correct accountβ Avoid:
FAQ
Q1: Why are my messages sent from default bot instead of kk bot?
A: Because the scheduled task didn't specify --agentId and --accountId. By default:
Solution: Specify explicitly when creating task:
openclaw cron add \
--agentId "kk" \
--session "kk" \
--accountId "kk-feishu" \
...
Q2: What's the difference between isolated session and agent dedicated session?
A:
isolated session: Temporary isolated session, doesn't inherit agent's channel bindingkk session: kk agent's dedicated session, inherits kk's channel binding (including accountId)If you want to use a specific agent's configuration, should use agent's dedicated session:
--session "kk" # β
Inherits kk's configuration
--session isolated # β Doesn't inherit any configuration
Q3: How to verify scheduled task configuration is correct?
A: Use these commands to verify:
# 1. View task list
openclaw cron list2. Run configuration check script
python3 ~/.openclaw/skills/task-orchestrator/scripts/check_cron_config.py3. Test execution
openclaw cron run {task_id}4. Check Feishu message
Confirm message is sent from correct bot
TERMINAL
clawhub install task-orchestrator-cron-heartbeat-subagent