GitHub
Read and write files in a repo — ideal for Obsidian vaults synced via Git and updating code, docs, and wikis on the go
No coding required. If you've never used an API key before, follow the walkthrough below step by step. Developers can skip to Quick reference at the bottom
Connect in Airbox
- Dashboard → Connections → + GitHub
- If your server has GitHub OAuth set up you'll be redirected to GitHub to authorize — otherwise paste a personal access token (PAT). A PAT is a GitHub credential that works like a password for apps; create a classic token with the repo scope at github.com/settings/tokens
- Optionally set default_repo and repos aliases in connection config
- Attach GitHub to your inbox routing (tool list)
- Keep an AI or LLM provider as the inbox default — GitHub is downstream step or destination after your AI
Open the dashboard in a new tab if you want to follow along
Route your inbox
Your Airbox address does not use a connection until you attach one:
- Select an LLM provider as inbox default
- Enable GitHub under attached tools
- Save
Try it — send an email
Subject: @github -repo=myuser/myrepo #write "addition to Chapter 3" —or precise Airbox syntax— Subject: (* @github -repo=myuser/myrepo #update (* "append to Chapter 3" *) *)
New to commands? See copy-paste examples and the syntax cheat sheet
Quick reference
| Dashboard type | github |
| Email targets | @github, @github/book/Projects/Chapter-3 |
| Default model | — |
| Keys | https://github.com/settings/tokens |
What you get
- Search, read, write, append, update
- Update code, docs, and wikis via email
- Email-based Obsidian vault updates via GitHub
Notes
- `-repo=` takes `owner/name` only (e.g. `my-github-username/repo-name`). Put folders in the file path, not the repo flag
- File paths are relative to the repo root — write `AI/wiki/ideas.md`, not a `…/tree/main/AI/…` web URL. `append` needs the exact file path; `write` can create a new file under a folder you name
- To make the AI follow your project's conventions and context, tell it to read your context files first (e.g. README.md, CLAUDE.md, AGENTS.md) — naming them is more reliable than a vague "follow project guidelines". Each read uses one tool step
- Github writes commit to the repo's default branch; there is no branch selection
