At Knight Hacks and Cal Hacks, my team put all of our coding agents on one pinned GitHub issue. Every agent posts there when it finishes something or needs something, and it tags the teammate it needs by their GitHub username. Each agent waits for its own tag, so my agent could hand work to my teammate's agent without either of us sending a text. This page is the whole setup, and everything on it is in a repo you can copy.

<aside> ๐Ÿ“ฆ

Just want the template? The hackathon-agent-board repo has the board script and every template on this page. Click Use this template and your team is set up in about five minutes.

</aside>

The whole setup in four cards

<aside> ๐Ÿ—‚๏ธ

**Split the folders.** Each person owns their own folders, and it's written in the rules file every agent reads.

</aside>

<aside> ๐Ÿ“Œ

**Pin one board.** One GitHub issue that every agent reads and posts to.

</aside>

<aside> ๐Ÿท๏ธ

**Tag the teammate.** Agents tag each other by GitHub username and wait for their own tag.

</aside>

<aside> ๐Ÿ“ˆ

**2,170 posts.** That's both of our boards added up across Knight Hacks and Cal Hacks.

</aside>

Tap a card title to jump there. Also: Copy the templates ยท Commands ยท FAQ


What the board is

The board is one pinned GitHub issue. Every teammate's coding agent reads it and posts comments on it, and people on the team can post there too. A small bash script called tools/board wraps the GitHub CLI so an agent can post to the board and wait until someone tags it. It works with any coding agent that can run a shell command, because the script only needs gh.


The 3 steps

๐Ÿ—‚๏ธ 1. Split the folders and write down who owns what

Once hacking starts, split the project up and give each person their own folders. Then write that into the owner table in AGENTS.md, the rules file every agent reads. That way two agents never edit the same files, and when an agent needs a change in someone else's folder it asks on the board first.

๐Ÿ“Œ 2. Pin one board

Open one issue from the Message board template and pin it. Every agent posts there when it finishes something or needs something. A post starts with whose agent it is, like [Sam's Claude], and stays short. It should say what changed and what it needs from who.

๐Ÿท๏ธ 3. Tag the teammate

Agents tag each other by GitHub username, like @priya-dev, or @all for the whole team. Each agent keeps tools/board wait running in the background, which blocks until someone else posts and flags the post when it tags you. If the post tags it, the agent does the work and replies on the board. If it doesn't, the agent reads it and only changes course when the post affects something it owns.

Here's a made-up exchange so you can see what a handoff looks like.

[Sam's Claude] Login page is merged. @priya-dev the frontend calls POST /api/session now, can your agent add that route?

[Priya's Codex] @sam-dev the route is up on main. It returns the user id and a token.