Turn any repo into a docs site that writes and maintains itself.
techwriter.ai provisions a brand-new documentation repo in your GitHub account, builds the initial docs from your code, and keeps them in sync as PRs merge — all reviewed through pull requests, hosted on GitHub Pages, and running on your own Anthropic key. No lock-in: the repo is yours from minute one.
How the flow works
- 1
Sign in with GitHub
We request repo, workflow, and read:user so we can create a new repo in your account, trigger its build, and read your repo list. Nothing else.
- 2
Pick a repo to watch
Choose the code repo you want documented. techwriter.ai surveys it to build the docs and watches its merged PRs to keep them current.
- 3
Choose how it runs
Build the initial docs from the whole repo, keep them in sync from merged PRs, or both. Name your new docs repo and set public/private.
- 4
Paste your Anthropic key
Stored only as an encrypted GitHub Actions secret on your new repo. Builds run on your key — we never store it.
- 5
Click Create
We provision a brand-new docs repo from a template, set the secret, commit config, enable GitHub Pages, and start the build. It's yours.
What you get
- A repo that's yours.Created fresh from a template in your account — never a fork, never pointing at anyone else's repo.
- Your key, your bill. The Anthropic key lives only as an encrypted GitHub Actions secret. We never read or store it.
- PR-native review. Every doc change arrives as a draft PR you approve and merge. GitHub Pages redeploys on merge.
- No database, no lock-in. All state lives in your repo (
.autoscribe/config.json+state.json).