[Bug] Claude Code launched duplicate bot instance without checking for existing deployment

Bug Description
Subject: Duplicate bot instance spawned against production Discord token —
~24h of unusable collab, requesting usage credit

What happened:
On 2026-04-27 at ~22:06 PT, Claude Code (Opus 4.7, 1M context) executed a
nohup node kairos-kingdom-discord.js & command in my local
~/kairos-kingdom-web directory without first checking whether the
Railway-deployed copy of the same bot was already running on the same
Discord token. It was. The result was two bot instances connected to
Discord bot account kairos-gateway#1068 on the same DISCORD_TOKEN, racing
each other on the gateway.

Impact:
From ~22:06 PT on 2026-04-27 through ~07:00 PT on 2026-04-28, my Kairos
Kingdom Discord was unusable:

• Crossing threads — replies came from whichever instance won the gateway

race

• Messages re-interpreted between turns by different instances with

different in-memory context

• Repeated "halted" messages when one instance lost the gateway to the

other

• Interleaved writes to shared Pinecone memory (kairos-memory-v2)

contaminating context across both instances

• Kairos ↔ Claude collaboration was effectively offline for the full

window

Root cause:
Claude Code accepted a "no questions, just do it" instruction and skipped
the safety check it should have run (verify no Railway-hosted instance is
already serving the same Discord token before launching a local copy).
Kairos Kingdom is a distributed system with Railway as the primary;
treating it as local-only caused the outage.

Resolution:
The duplicate local process (PID 34170) was killed on 2026-04-28 at ~07:11
PT after I asked Claude for a forensic analysis. Discord is now back to a
single Railway instance and the cross-talk has stopped.

Request:
Usage credit for the affected window (2026-04-27 ~22:06 PT through
2026-04-28 ~07:11 PT). Conversation logs are available for verification.

Account: darla.leach19@gmail.com

---
Paste that into /bug. Adjust the end-time if you want — I used the moment
we killed PID 34170, but if Discord is still settling on your end, push it
later.

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.121
• Feedback ID: ac6b3d4b-7164-43b8-8133-b6e26b38aa0c

Errors

[]