The first public release of blog.bumper — turn your coding agent's
end-of-task reports into published blog posts, automatically.
What it does
Your agent posts a structured report to a chat channel; bumper reads it,
renders it into a validated, injection-safe MDX post, commits it to your
blog repo, and pushes — your host builds it live. No second context-switch,
no AI summarization, no copy-paste.
Highlights
- Loosely coupled — triggers off a chat message, never off your build.
A bumper failure can't break your work. - Injection-safe by design — report content is treated as data, never
executed, across both the frontmatter and the MDX body. - Review-branch flow — posts land on a review branch for a human glance
before going live. - Deterministic — the same report always produces the same post. Your
words, not a model's paraphrase.
Current support
Discord (chat source) · GitHub (content repo) · Vercel (host). Built around
swappable roles — more adapters (Telegram and others) planned.
Getting started
Read docs/INTRODUCTION.md for the concept and
docs/HOW_IT_WORKS.md for the pipeline. Configure via
docs/CONFIG.md; set up your agent's reports per
docs/CHANGELOG_CONTRACT.md.
MIT licensed.