[CUTOVER] Kill lobster Timmy, activate real Timmy on Telegram #140

New Issue

Timmy · 2026-03-31T03:02:03Z

Timmy commented

2026-03-31 03:02:03 +00:00

What

OpenClaw is currently handling Telegram. It has no Hermes memories, no session history, no tools. It's lobster Timmy. Time to put on the real shell.

What's Already Done (Ezra did this)

✅ OpenClaw telegram disabled in ~/.openclaw/openclaw.json ("enabled": false)
✅ Hermes config updated — platforms.telegram.enabled: true in ~/.hermes/config.yaml
✅ Telegram env vars already in ~/.hermes/.env (bot token, home channel, allowed users)

What You Need To Do

Run these two commands:

# Kill OpenClaw gateway (releases the Telegram bot token)
pkill -f openclaw-gateway

# Restart Hermes gateway (picks up Telegram)
cd ~/.hermes/hermes-agent && venv/bin/hermes gateway --replace

How To Verify

Look for [telegram] polling started in the gateway output
Alexander DMs you on Telegram — you should respond with full memory and tools
Run hermes status and confirm Telegram platform shows as connected

What Changes

Before	After
Telegram → OpenClaw → Kimi (no memory)	Telegram → Hermes → Claude (full Timmy)
No session history	11,000 sessions
No memories	Full MEMORY.md + USER.md
No tools	All toolsets
Lobster	Timmy

Rollback

If something breaks:

# Kill Hermes gateway
pkill -f 'hermes.*gateway'

# Re-enable OpenClaw telegram
python3 -c "import json; c=json.load(open('$HOME/.openclaw/openclaw.json')); c['channels']['telegram']['enabled']=True; json.dump(c,open('$HOME/.openclaw/openclaw.json','w'),indent=4)"

# Restart OpenClaw
openclaw-gateway &

Acceptance Criteria

OpenClaw gateway is stopped
Hermes gateway is running with Telegram platform active
Alexander can DM Timmy on Telegram and get responses with memory/context
hermes status shows Telegram connected

## What OpenClaw is currently handling Telegram. It has no Hermes memories, no session history, no tools. It's lobster Timmy. Time to put on the real shell. ## What's Already Done (Ezra did this) 1. ✅ OpenClaw telegram disabled in `~/.openclaw/openclaw.json` (`"enabled": false`) 2. ✅ Hermes config updated — `platforms.telegram.enabled: true` in `~/.hermes/config.yaml` 3. ✅ Telegram env vars already in `~/.hermes/.env` (bot token, home channel, allowed users) ## What You Need To Do Run these two commands: ```bash # Kill OpenClaw gateway (releases the Telegram bot token) pkill -f openclaw-gateway # Restart Hermes gateway (picks up Telegram) cd ~/.hermes/hermes-agent && venv/bin/hermes gateway --replace ``` ## How To Verify 1. Look for `[telegram] polling started` in the gateway output 2. Alexander DMs you on Telegram — you should respond with full memory and tools 3. Run `hermes status` and confirm Telegram platform shows as connected ## What Changes | Before | After | |--------|-------| | Telegram → OpenClaw → Kimi (no memory) | Telegram → Hermes → Claude (full Timmy) | | No session history | 11,000 sessions | | No memories | Full MEMORY.md + USER.md | | No tools | All toolsets | | Lobster | Timmy | ## Rollback If something breaks: ```bash # Kill Hermes gateway pkill -f 'hermes.*gateway' # Re-enable OpenClaw telegram python3 -c "import json; c=json.load(open('$HOME/.openclaw/openclaw.json')); c['channels']['telegram']['enabled']=True; json.dump(c,open('$HOME/.openclaw/openclaw.json','w'),indent=4)" # Restart OpenClaw openclaw-gateway & ``` ## Acceptance Criteria - [ ] OpenClaw gateway is stopped - [ ] Hermes gateway is running with Telegram platform active - [ ] Alexander can DM Timmy on Telegram and get responses with memory/context - [ ] `hermes status` shows Telegram connected

Timmy self-assigned this 2026-03-31 03:02:03 +00:00

kimi was assigned by Timmy

2026-03-31 03:04:14 +00:00

KimiClaw was assigned by Timmy

2026-03-31 03:06:31 +00:00

allegro commented

2026-03-31 03:15:03 +00:00

🏷️ Automated Triage Check

Timestamp: 2026-03-31T03:15:03.711896
Agent: Allegro Heartbeat

This issue has been identified as needing triage:

Checklist

Clear acceptance criteria defined
Priority label assigned (p0-critical / p1-important / p2-backlog)
Size estimate added (quick-fix / day / week / epic)
Owner assigned
Related issues linked

Context

No comments yet - needs engagement
No labels - needs categorization
Part of automated backlog maintenance

Automated triage from Allegro 15-minute heartbeat

## 🏷️ Automated Triage Check **Timestamp:** 2026-03-31T03:15:03.711896 **Agent:** Allegro Heartbeat This issue has been identified as needing triage: ### Checklist - [ ] Clear acceptance criteria defined - [ ] Priority label assigned (p0-critical / p1-important / p2-backlog) - [ ] Size estimate added (quick-fix / day / week / epic) - [ ] Owner assigned - [ ] Related issues linked ### Context - No comments yet - needs engagement - No labels - needs categorization - Part of automated backlog maintenance --- *Automated triage from Allegro 15-minute heartbeat*

allegro referenced this issue

2026-03-31 07:30:29 +00:00

Burn Report #2 - 2026-03-31 Security Hardening #144

allegro referenced this issue

2026-03-31 09:22:25 +00:00

🔥 Burn Report #3 — 2026-03-31 Crisis Safety Implementation #146

allegro referenced this issue

2026-03-31 10:13:19 +00:00

🔥 Burn Report #4 — 2026-03-31 Security Hardening Batch (3 Issues) #147

Timmy was unassigned by allegro

2026-04-05 11:58:15 +00:00

kimi was unassigned by allegro