Research → repository
Save a plan, decision or brief where the next coding session can use it.
Forge is the safe handoff between a conversation and your repository: research, visual reviews and small edits become real commits and draft pull requests. It never runs code. It holds proposed work for your review.
https://timcoy.uk/forge/mcpClient support varies by plan and surface. Read and screenshot tools remain useful where write actions are unavailable.
Save a plan, decision or brief where the next coding session can use it.
See phone and desktop, then record the findings or make a small correction.
Hold implementation or risky work for review before it becomes repository truth.
Your repos, a repo’s files, or what a change did
no approvalCommits files directly or holds one change for review
no approvalSends one link to land a change on main
you approveSends one link to throw a change away
you approveCaptures a public page at phone and desktop
no approvalYou never name a branch — describe the work, and say those words again to continue it. A commit is on GitHub the moment a tool returns.
ChatGPT: Settings → Apps → Advanced settings → Developer mode. Claude: Settings → Connectors.
https://timcoy.uk/forge/mcp
ChatGPT custom write support currently depends on plan, workspace and surface. Use the actions your client enables.
Your client opens a Forge page, then GitHub asks whether to let Forge act as you. That is the last time tokens come up.
Authorizing says who you are. Installing says which repositories — all of them or a few, changeable any time from GitHub.
Use a coding agent for builds, tests, commands and deployments
Each repository has one Forge change
Captures need a URL that is already public
GitHub is the only place your work lives