The book stays yours
Chapters are Markdown in a Git repository you own. Accepted work becomes a normal commit. If Authorbot goes away, the manuscript does not go with it.
Git-backed editorial control planeWriting is the fun part.
Writing is the fun part.
Authorbot is the rest.
Authorbot publishes your book from a Git repository you own. Start alone if you like. When you want help (reader notes, suggested edits, even drafts from software agents), the machinery for review and credit is already there.
It never calls a language model, and it never writes a word on its own.
authorbot / control planelive
Git is the literary truthchapters · story bible · history
✓Authorbot handles the worknotes · votes · leases · review
The book stays readableplain HTML or your own frontend · one address
✓accepted revision
chapter-01.mdcommit 8c31a7f01 your repository02 plain Markdown03 full attribution04 works offline
What it keeps straightA book is prose.
A book is prose.
The work around it is a system.
Git is excellent at remembering files. It is less useful for live discussion, assignment, permissions, and review. Authorbot handles those parts without turning the manuscript into a database export.
People and agents use the same door
Humans and software agents work through the same API, validation, review, and attribution rules. Agents never need direct write access to the repository.
Governance is boring on purpose
Suggestions, votes, leases, permissions, and decisions are explicit records. Rules live beside the book, and a human maintainer keeps the final call.
Publishing is part of the loop
The reading site, authoring tools, collaboration API, and deployment share one address. A revision can move from a note to a live chapter without losing its history.
Runs on your laptop too
authorbot dev runs the real API and authoring UI locally: no Cloudflare account, no GitHub connection, and no network once the packages are installed. Write on a plane, push when you land.
The site is yours to shape
Drop assets in public/, add cover art and character portraits, link custom pages from the nav, or go fully headless. Every build ships the whole book as versioned JSON your own frontend can render.
Solo or with helpGood alone.
Good alone.
Built for company.
Collaboration is optional. A book with no collaborators is still a clean way to write and publish a serial, and the day you want another set of hands, nothing needs to be rebuilt.
writing alone
- A reading site generated from plain Markdown
- In-browser editing that looks like the published page
- Chapter history you can walk revision by revision
- A story bible for outline, timeline, and characters
- Offline drafting with
authorbot dev
writing with help
- Reader notes anchored to the exact sentence
- Suggested edits you approve, reject, or discuss
- A work queue with timed claims, so jobs never collide
- Scoped tokens for software agents, under your rules
- Attribution kept on every accepted change
Same book, same repository. Collaboration is a switch, not a migration.
How work movesFrom a note in the margin
From a note in the margin
to a commit you can inspect.
- 01
A reader leaves a note
Feedback stays attached to the exact chapter, range, or block it refers to.
- 02
The author makes it work
A maintainer can review votes, promote the note, and set the job that needs doing.
- 03
Someone claims it
A human or agent takes a timed lease, reads the book context, and submits against a known revision.
- 04
Authorbot checks the change
It validates the edit, keeps attribution, and applies the project’s review rules.
- 05
Git records the result
Accepted prose lands as a narrow commit, and the published book updates from that source.
Start with one commandMake the repository.
Make the repository.
Publish when you're ready.
The setup wizard checks the tools, creates the book, publishes the reading site, turns on collaboration if you want it, and can issue a narrowly scoped token for an agent. Prefer to stay local? authorbot dev runs the same API and authoring UI on your machine, offline, with no accounts connected.
Fair warning: this is early software. It has not yet met every possible GitHub account, Cloudflare setup, or author habit.
$ npx @authorbot/create
✓ tools checked✓ book repository created✓ reading site published✓ collaboration ready
$ npx authorbot dev
✓ writing locally at localhost:4321