> ## Content Index
> Fetch the complete content index at: https://christophermoravec.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Claude Clue #36: Give Your Claudes a Bulletin Board
- URL: https://christophermoravec.com/claude-clues/claude-clue-36-give-your-claudes-a-bulletin-board-2/
- Published: 2026-08-25T15:00:56.000Z
- Updated: 2026-08-25T15:00:56.000Z
- Description: Your Claude just renamed an interface. Your coworker's Claude has no idea.
- Author: Christopher Moravec
- Tags: Claude Clues

Let's imagine that you and a coworker are building in the same repo, and each of you has your own Claude. The two of you talk all day, but the two Claudes have never met.

Most of the time it won't matter; you each give Claude its own branch so they don't have to coordinate, and then you deal with the merge conflicts the same way you would with any other human teammate. But then one crazy morning your Claude renames an interface, you forget to pass it along, and your coworker (with Claude) spends days (hours?) building against an interface that no longer exists. Then later you find out! Okay, so this is a little contrived, but I think you get the idea: more collaboration is better.

What if you gave your Claudes a bulletin board to share? We did this with a GitHub issue (what I call a gissue). The gissue body holds the ground rules so that every time a Claude discovers, plans, decides, tests, or finishes something, it leaves a comment noting it. A small bash script polls the issue in the background and pings each Claude when a new comment appears.

There is more than one way to achieve this; for example, you could use Claude Code's [hooks](https://code.claude.com/docs/en/hooks?ref=christophermoravec.com) to wire the same loop, but it seems less satisfying. Anthropic has an [open feature request](https://github.com/anthropics/claude-code/issues/28300?ref=christophermoravec.com) for Claudes that talk to each other across machines. Until that ships, a bash script and a GitHub issue aren't fancy, but they get the job done. (It reminds me a little of [MoltBook](https://www.moltbook.com/?ref=christophermoravec.com)).

With a shared board in place, that rename issue we described goes differently. The first Claude comments the rename as soon as it finishes, the poll pings your coworker's Claude a few minutes later, and now the two agents can sync up. One side effect is that the gissue turns into a play-by-play of the build, so you can open it and watch changes happen in real time as agents collaborate.

*Kevin Sadrak found this one, Roscoe emailed it over, Claude drafted the post, and I edited it. Four of us, and not one bulletin board between us.*