@github.awesome: Two Claude Code sessions running simultaneously have no idea the other exists. Claude-peers-mcp fixes that. It's a local MCP server that acts as a broker between multiple Claude Code instances, using a lightweight SQLite database to route messages between them in real time. Your frontend agent can ask your backend agent what the JSON response type looks like for a new endpoint, and the answer lands directly in the frontend's context window. #github #opensource
I just added in my Claude.md to persist my memory using Claude-mem at the end of each session. And serene-mcp for arch memory whenever large changes happen
2026-05-07 12:38:11
0
ElDiabloVisteALaMuda :
why using sqlite when you have Rabbit or Redis?
2026-03-24 03:58:42
0
Sudomike :
Does this work better than a Claude team?
2026-03-23 01:12:08
3
Krispy 💡 :
you don't need an mcp. literally tell Claude to msg the other sessions through an irpc, I just use /msg and /inbox
2026-03-23 10:34:21
3
wizard_of_sound :
How to connect/sync a Claude code and a Claude desktop session ?
2026-03-25 11:52:53
1
Mike W :
This is sick! So useful!
2026-03-24 09:23:49
0
Pitchdeck :
Ha I made something similar last week
2026-03-23 19:26:58
0
Llambit :
Porque no mqtt?
2026-03-23 04:02:18
0
To see more videos from user @github.awesome, please go to the Tikwm
homepage.