Ion SHM Response Time Fix - Plan of Action
Problem Statement
SHM response time is >2 minutes due to broken openclaw agent CLI wake mechanism.
Current State (Before Fix)
Detection: 0-15s ✅ (working)
Wake mechanism: 120s timeout ❌ (broken)
Total: 2+ minutes ❌
Solution Architecture
Simplify to two independent components:
1. Poller (Already Deployed ✅)
Frequency: Every 30 seconds
API: Only
seed-cli activity --after <timestamp>Output:
memory/seed-event-queue.jsonState:
memory/seed-last-activity-time.txtStatus: ✅ Deployed
2. Queue Processor (TODO)
Frequency: Every 30 seconds (heartbeat)
Input:
memory/seed-event-queue.jsonAction: Process events, respond on SHM
Output: Telegram alert to Eric
Status: ⏳ Not implemented
Implementation Steps
Phase 1: Simplify Poller (DONE ✅)
[x] Create
seed-simple-poller.sh- only uses activity API[x] Remove comment list, citations, search API calls
[x] Track last event timestamp per URL
[x] Schedule via systemd timer (30s interval)
[x] Write events to queue file
Phase 2: Create Queue Processor (TODO)
[ ] Add queue check to
HEARTBEAT.md(30s interval)[ ] Read
memory/seed-event-queue.json[ ] For each event:
Extract comment/mention details
Generate response via LLM
Post to SHM via
seed-cli comment createSend Telegram summary to Eric
[ ] Clear processed events from queue
Phase 3: Testing & Monitoring
[ ] Test with manual SHM comment
[ ] Verify 30-60s response time
[ ] Monitor
logs/seed-simple-poller.log[ ] Monitor
logs/seed-queue-processor.log[ ] Adjust timing if needed
Phase 4: Cleanup
[ ] Disable old poller (
seed-ion-trigger.service)[ ] Remove old state files
[ ] Update documentation
Files Created/Modified
/home/e.guest/.openclaw/workspace/scripts/seed-simple-poller.sh✅/home/e.guest/.config/systemd/user/seed-poller.service✅/home/e.guest/.config/systemd/user/seed-poller.timer✅/home/e.guest/.openclaw/workspace/HEARTBEAT.md(needs update) ⏳/home/e.guest/.openclaw/workspace/memory/seed-event-queue.json✅
Expected Timeline
Phase 2 (Queue Processor): 30 minutes
Phase 3 (Testing): 15 minutes
Phase 4 (Cleanup): 10 minutes
Total: ~55 minutes
Success Criteria
Response time: 30-60 seconds consistently
No missed mentions/comments
Queue processes without manual intervention
Telegram alerts for failures only
Current Status
Last Updated: 2026-05-05 13:28 CEST Phase: 1/4 Complete ✅ Next Action: Implement queue processor in heartbeat
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime