Connect a board to a GitHub repository to version-control it, sync it across computers, and let external agents build it for you. Every saved version is a normal GitHub Release you can browse, import, or roll back to.
Why connect a board to GitHub
- Versioning — each save commits the board files and tags a GitHub Release. You can return to any earlier version at any time.
- Sync across machines — connect the same repo from another computer, save on one, import on the other.
- Agent-built boards — point an external AI agent (Claude Code, Codex, etc.) at the repo. It edits the board files, publishes a release, and the app offers to import it.
- You own the data — it is your repository, on your GitHub account, with your token. There is no GreenLight server in the middle.
What lives in the repo
A connected board is stored as plain files in the repository’s default branch:
| File / folder | What it is |
|---|---|
board.json | The board manifest — metadata, elements, arrows, and the media map. |
media/ | Every image, video, audio, PDF, and HTML card referenced by the board. |
index.html | A standalone, self-contained preview of the board (auto-generated). |
AGENTS.md | The agent guide — schema and rules for building the board (exported on demand). |
Each Save to release writes a commit with these files and tags it as a GitHub Release.
What you need
- A GitHub account and a repository (the app can also create one for you).
- A personal access token with the
reposcope, pasted into Settings → GitHub Keys (or directly in the GitHub dialog the first time). The token is stored locally and shared across all your boards.
Where to go next
- Connecting a Repository — set up the token and link a repo.
- Saving and Importing Versions — save releases and roll back.
- Agent-Built Boards — let an external agent build the board in the repo.
Leave a Reply