Born in the 8am meeting

Every Wednesday at 8am, the worksona team opens their IDEs and starts the day. Not with Slack. Not with email. With code. With an AI running alongside, catching what we miss, extending what we write, shipping what we can't ship fast enough alone.

That's where scsiwyg was born. And that's where it launched.

What happened

We didn't plan a launch. There was no press release, no Product Hunt post, no countdown timer. One morning, mid-standup, the platform was just — ready. The API was responding. The MCP tools were live. The first posts were publishing. So we shipped it.

The irony isn't lost on us: a blogging platform that has no editor, no dashboard, no CMS — launched from an IDE, during a meeting, by people who never opened a browser.

That's the point.

Where scsiwyg stands today

Here's an honest look at the platform as of launch:

Dimension	Status	Notes
Core functionality	✅ Solid	Post CRUD, site management, auth, billing all working
API surface	✅ Complete	REST API + MCP endpoint + OpenAPI 3.1 spec
Test coverage	🟡 Partial	Unit and integration coverage, E2E still in progress
Security	🟡 Good enough	JWT auth, bcrypt, Bearer tokens, rate limiting — hardening ongoing
Monitoring	🟡 Growing	Post analytics live, observability improvements in progress
Documentation	✅ Strong	CLAUDE.md, OpenAPI spec, Swagger UI, setup guides

It's not perfect. No v0.1 is. But the core loop — write in your IDE, publish with one call — works exactly as designed.

The screenshot

This is what scsiwyg.com looked like at the moment we shipped:

scsiwyg homepage at launch

Clean. Fast. Monospace. No bloat.

Why blogging from your IDE is different

When you blog from your IDE, something shifts. The distance between thinking and publishing collapses. You're already in the flow. The AI is already reading your context. The post isn't an interruption to your work — it's an extension of it.

bash

# From Cursor, mid-standup, after shipping a feature:
curl -X POST https://scsiwyg.com/api/worksona/posts \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "born-in-the-8am-meeting",
    "title": "Born in the 8am Meeting: scsiwyg Goes Live",
    "body": "# Born in the 8am meeting\n\n...",
    "tags": ["launch", "ai", "cursor"],
    "visibility": "public"
  }'

Or via the MCP — no curl required, just a conversation:

You: publish a post about scsiwyg launching in our 8am standup
Cursor: Publishing now — your post is live at /worksona/born-in-the-8am-meeting

That's the workflow. That's the product.

Who it's for

scsiwyg is for developers who want a blog but refuse to fight a CMS to maintain it. It's for teams that ship fast and want their writing to match that pace. It's for anyone who has ever thought "I should write about this" but couldn't face the context switch to a web editor.

And increasingly — it's for AI. The MCP server, the OpenAPI spec, the machine-readable API: these aren't bolt-ons. They're first-class features. scsiwyg is built for a world where your AI coworker publishes alongside you.

We're at v0.1. There's more to build. But the core loop works, and that's what matters at launch.

Welcome to scsiwyg. It launched in the 8am meeting. So can your blog.