Reads the room
Every new issue is matched against the discussions, replies, and closed tickets you've written before — so the answer is grounded, not guessed.
Volume 1 · Edition 04
§ 01 · A field guide
For maintainers who would rather be writing the next chapter than answering the same question for the seventh time.
01Read every issue
02Recall what you wrote before
03Suggest the next paragraph
Tend youropen sourcelike a garden,not a queue.
Responder · the maintainer's atelier01 / 04
§ 02The chapters
Four small acts that keep
a project from drowning.
The boring half of maintainership — triage, repetition, the third time you've explained the same flag — happens by itself, in the margins, while you keep writing the parts only you can write.
Drafts in your hand
A reply lands as a draft signed with your voice and your prior choices. Approve, edit, or send it straight back. Always your call.
Mends the docs
When an issue closes, Responder reads the resolution and proposes a diff against the page that should have answered it.
Lives where you do
Webhooks, GitHub Apps, repository indexing. No new dashboard for your contributors — only the calmer issue tracker they already use.
§ 04 · A small invitationHand the dull part over.
Hand the dull part over.
Keep the writing.
Sign in with GitHub. Pick a repository. Watch the next ten issues answer themselves — softly, in your voice, with you in the loop.
Sign in & open the studio
Free5 reposNo cardrequiredOpensource friendly