Because a connected board is just plain files in a Git repository, an external AI agent — Claude Code, Codex, Gemini CLI, or any system that can read and write a repo — can build or edit the board for you. It commits the files, publishes a release, and the app offers to import it.
How it works
- The agent clones or opens the board’s repository.
- It reads
board.jsonand themedia/folder to understand the current board. - It edits
board.json(adds or changes elements, arrows, frames) and drops any new files intomedia/. - It commits to the default branch and publishes a GitHub Release, tagging it as agent-built.
- Back in the app, the GitHub icon shows the pulsing green dot and the dialog shows a New release available (built by an agent) banner. Import it like any other release — see Saving and Importing Versions.
Agent releases carry an Agent badge in the Releases list, so you can always tell app-saved versions from agent-built ones.
Give the agent the build guide
The repo ships with an AGENTS.md guide that teaches an agent the exact board-file format — the board.json schema, element types, coordinate system, the media map, and how to publish a release. In the Agent skill panel of the GitHub dialog:
- Export AGENTS.md to repo — commits the guide into the repository so any agent working in the repo can read it.
- Download AGENTS.md — saves the guide locally to hand to an agent directly.
Export the guide once after connecting, then simply ask your agent to “build this board following AGENTS.md.”
Staying in sync
Agent edits and your own edits both land as releases in the same repo. The stale-write guard keeps the two from clobbering each other: if an agent published a release you haven’t imported, the app prompts you to Import it first before saving over it.
Where to go next
- Saving and Importing Versions — import the agent’s releases.
- Connecting a Repository — token and repo setup.
Leave a Reply