Your agent shipped the feature.
Let it write the story.
BloggyBox is a writing and publishing workspace for people who build things — developers, founders, and teams. Your agent already knows what you shipped, so let it draft the article, announcement, changelog, or docs update — or write it yourself. Either way: review, organize, publish. Writing lives here, not in your repo.
Works with Claude, ChatGPT, Codex, Cursor, OpenCode — any MCP-compatible agent.
Shipping got automated.
Writing about it didn't.
Your code is already being shipped by agents.
Claude Code. Codex. OpenCode. And whatever comes next. You tell them what to build. They read your codebase. They change the code. They run the tests. They ship the feature. You barely touch the keyboard.
“Oh right. We should probably tell people about this.”
And then the writing starts — usually somewhere built for code: your repo, your CMS, or another PR just to publish a few paragraphs.
What if your agent could ship the story too?
Your agent already knows:
- What changed
- Why you changed it
- How it works
- Files touched
So instead of opening a blank editor and thinking:
“How the hell do I explain this?”
Tell your agent: “Send this to BloggyBox.” And it creates a draft in your publication.
The GitHub import feature is ready and committed to main.
Your agent writes it. You decide whether it ships.
BloggyBox isn't here to replace your judgment. Your agent creates the first draft. You open it. You change whatever you want. You cut the fluff. You add the important bit the agent missed. Then you publish.
Nothing goes public until you say so.
Autonomous drafting with deterministic human sign-off.
From shipped to published.
You built the feature. Now write about it — in a real writing workspace, not your repo. Your agent can draft it or you can; you edit, organize, and publish with one click. No PR, no deploy, no CMS.
Create your first publicationFour simple steps from code to reader.
One loop for developers, founders, and teams — from wherever you already work to a live page. No repo, no CMS, no pull request.
Build
Ship your feature with the tools you already use. (Claude Code. Codex. OpenCode. Whatever you like.)
Send
Ask your agent to send it to BloggyBox. The draft lands in your publication — private, ready for you to review.
Review
Open it, rewrite it, make it yours. Your agent starts it; you finish it — in the editor, not the terminal.
Publish
One click and it's live on your publication. No PR, no deploy, no CMS.
The old way vs. the BloggyBox way.
Publishing a post shouldn't cost more time than the feature it talks about.
Prefer writing it yourself?
Good. BloggyBox is a writing workspace first. Start from a blank page, keep drafts and revisions organized, edit however you want, and publish to your publication — agent entirely optional.
“The agent is an input. It isn't the product.”
stream.onmessage = (e) => dispatch(e.data);
Prefer ChatGPT or Claude? Use whichever.
Writing shouldn't require a terminal. Draft right in the chat you already use — connect ChatGPT, Claude, or Gemini in one click — and send it straight to your publication. Switch assistants whenever you like; your drafts, reviews, and publication stay put.
Not everything you ship deserves a launch campaign.
Changelogs, release notes, quick updates — the small stuff still deserves to be read. Have your agent draft them, approve, done.
Changelogs and release notes are stories too — they just shouldn't take a full day of writing.
Added dark mode
2h agoFull contrast optimization across all theme tokens and code renderers.
Improved search latency by 40%
YesterdayMigrated inverted indexes to edge in-memory caching stores.
New API endpoint for webhook verification
3d agoCryptographic signature headers added for zero-trust consumer callbacks.
Fixed a painfully annoying Safari bug
May 12Resolved WebKit viewport overscroll rubberbanding glitch on canvas panes.
Finally shipped that feature you've been talking about for three months
May 10Multi-branch previews with instant preview domains are now standard.
Give your agent a publishing endpoint.
Connect your agent once and it can send drafts straight into your publication — Claude, ChatGPT, Cursor, OpenCode, Codex. It works through MCP, the open standard these tools already speak, so there's no plugin to install and no lock-in.
No copy-pasting. No jumping between tabs. No asking an AI to write something, copying it into another editor, formatting it, and eventually remembering to publish it. Your agent already did the work. Let it hand the story over.
{
"mcpServers": {
"bloggybox": {
"type": "http",
"url": "https://your-host/mcp",
"headers": {
"Authorization": "Bearer bbkx_..."
}
}
}
}Agents can draft. Humans publish.
BloggyBox keeps the final step yours. Your agent can create a draft. It cannot quietly publish it. You review. You edit. You decide.
“Because ‘the AI published something’ should never be a surprise.”
One publication for everything you write.
Each project gets its own publication — clean URLs, your branding, your audience. Articles, product announcements, changelogs, release notes, tutorials, docs, founder updates: one place for all of it, edited by you. Not a chat transcript. Not an AI content dump. A publication.
Introducing GitHub Import: Zero-Config Workspaces
Developer tools thrive when onboarding latency drops to zero. Over the last release cycle, our primary focus was eliminating manual project scaffolding entirely.
By connecting directly to the GitHub Repositories API through authenticated OAuth scopes, your teams can now spin up active sandboxes in under two seconds.
Today, it's your blog. Tomorrow, wherever your story needs to go.
A word from the founders.
We were shipping features at 2 AM with Claude and Codex. 15 commits, 3 PRs merged, entire backend rewritten. But writing the release post felt like hitting a brick wall.
We realized: your AI already holds the full context of what was created, why decisions were made, and how it impacts users. It watched the diff evolve line by line. It analyzed the error boundaries. It knows the exact nuances of the new feature better than you do after an 18-hour coding sprint.
Why throw that context away into the void? Why force engineers to switch gears from architecting systems to staring at an empty WYSIWYG editor wondering how to summarize their work?
“BloggyBox was born because building is exhilarating, but sharing what you built shouldn't be exhausting.”
We created BloggyBox to be the missing bridge: your agent drafts what you shipped, and you stay in control of the publish button. No auto-publish surprises — just a proper place to write about what you build.
The hard part was never the code.
It's telling people what it does.
AI writes more of the code every month. What's left is the part code can't do for you: the announcement, the changelog, the explainer — written down where your audience actually reads it.
We build BloggyBox in public and publish everything on BloggyBox itself. Follow along, see what we ship, and read how it was made — the same week it happens.
“Stop letting your agent delete its own memory after git push. A publication endpoint turns agent epiphanies into permanent team assets.”
watching BloggyBox get built in public
Simple plans for solo builders and high-velocity teams.
Start free with your favorite AI agent. Paid plans arrive soon — everything below ships on the free plan today.
For individual builders shipping solo projects.
- 1 Active Publication
- Unlimited MCP agent drafts (Claude Code, Codex, Cursor)
- Up to 5 published articles per month
- bloggybox.com/your-project subdomain
- Markdown & raw terminal sync
- Human-in-the-loop review workflow
For founders and engineers who ship and update continuously.
- 3 Custom Domains (e.g. blog.yourdomain.com with auto SSL)
- Unlimited published articles & changelog micro-updates
- Custom publication themes, typography & branding
- Custom agent prompt instructions & editorial voice rules
- Automated OpenGraph banner generation for X/LinkedIn
- RSS feed, newsletter dispatch & subscriber capture
For growing dev teams and multi-agent engineering setups.
- Unlimited publications & custom domains
- Multi-seat editorial collaboration & draft approval rules
- Multi-agent MCP orchestration (per-repo or per-service keys)
- Priority edge caching & global CDN distribution
- Priority developer support & direct MCP assistance
Run self-hosted relays behind your corporate VPC with bespoke audit logs.
Everything about connecting your agent — and staying in control.
How connection, drafts, review, and publishing work, answered plainly.
How do I connect my agent to BloggyBox?
Add your publication's endpoint URL to your agent's MCP config — on first connect your browser opens BloggyBox, where you pick a publication and approve access. Prefer a key? Generate one on the MCP & Feed page and pass it as a Bearer header. No package to install, no daemon to run.
Which agents work with BloggyBox?
Any MCP-compatible client: Claude Code, Cursor, OpenCode, Codex, Windsurf, Zed, Gemini CLI, Cline, Copilot, and ChatGPT. If it speaks MCP over Streamable HTTP, it can hand drafts to your publication.
Can my agent publish without my permission?
No. Agent keys carry the draft:create scope only, and the create_draft tool only creates drafts — it cannot publish, edit live posts, or touch settings. Nothing goes public until a human reviews and hits Publish.
What happens after my agent sends a draft?
It lands in your publication as a private draft ready for review. Retries are safe: sending the same client_request_id twice never creates a duplicate.
Can I ignore the agent and just write myself?
Absolutely — manual writing is a first-class path, not a fallback. Start an article in the editor, keep drafts and revisions organized, publish when you're ready. The agent is an input, never a requirement.
What data of mine reaches BloggyBox?
Only what your agent sends as a draft: title, markdown content, excerpt, tags, and slug. Your agent reads your codebase locally on your machine; BloggyBox stores the resulting draft in your publication and nothing else.
You shipped the feature.
Now ship the story.
Articles, announcements, changelogs — write them yourself or let your agent start them. Review. Publish. Done.
Free to start · No credit card required