Skip to content
scsiwygest. ‘26
Sign in
get startedmcpcommunityapiplaygroundswaggersign insign up
Vol. II · No. 04Headless publishing for the people who think out loudMay 4, 2026
A field manual for thinking in public

Write where
you work.

A blog and a wiki you build by talking to your AI — drafted in your voice, published with a nod.

For anyone who already talks to an AI. Works inside Claude, ChatGPT, Cursor, Copilot, Windsurf — wherever your thinking happens.

claude · scsiwyg session00:14
Plate I.  A workspace, mid-sentence — late afternoon
F · 35mm · © scsiwyg / 2026
Typewriter transforming into digital code — scsiwyg turns your IDE into a publishing tool
§ I — Two modes of writingpp. 04 — 11

One platform.
Two ways to keep a record.

Every scsiwyg site is either a blog — a chronological field recording of the work — or a wiki, a structured tree your AI maintains as you learn. Same API. Same MCP. Different shape.

Mode 01 — Blogchronological feed

The journal you didn’t mean to keep.

Tell your agent what just happened. It drafts in your voice from the context of your open files. You read it, you approve it, it’s live.

> blog: I just shipped the new auth flow. We went stateless JWT, rotating refresh. Tag it engineering. Drafted → "Why we rewrote our auth middleware" slug → auth-middleware-rewrite status → published
Mode 02 — Wikistructured knowledge tree

A second brain that organizes itself.

Pages have parents, children, sort order, confidence and provenance. Your agent builds the tree as you learn; the platform renders it with sidebar nav and breadcrumbs.

> publish my wiki to scsiwyg research/ llm-patterns mediumtransformer-arch highreference/ platform-arch highsecurity-posture medium Published 11 pages, updated 3
§ II — On the practicepp. 12 — 19

Publishing as a practice,
not a project.

Most writing tools assume the writing comes after the work. You finish the sprint, switch tabs, summon the CMS, fight the editor, find the photo, choose the slug. By the time the post is up, the moment has gone cold.

scsiwyg inverts that. The composition surface is the place you already are — your editor, your chat with Claude, your terminal. The agent reads the room. You correct it. You ship.

“The point isn’t to write more. It’s to leave a trail of how you actually thought, while you were thinking.”
i.

Zero context switch

You never leave the editor or the chat. Content lives inside the same mental frame as the work — the bug you untangled, the refactor that backfired, the decision you almost forgot.

ii.

Authentic voice, written in the moment

The agent drafts from your open files, your last messages, your tone. Not reconstructed from memory a week later. The result reads like you, because it was you.

iii.

For anyone who thinks out loud

Researchers maintaining living wikis. Teams blogging together. Founders building in public. Anyone who already talks to an AI has a publishing surface, now.

iv.

A corpus, accumulated

Posts and pages compound into a record of how you think and work — searchable, embeddable, exportable. Yours, in flat portable JSON, forever.

§ III — How to beginpp. 20 — 22

Three steps,
and you’re publishing.

No CMS. No build system. No context switch. Sign up, install the MCP, and tell your agent to write something.

i.

Create an account

Sign up free. You get a connection key that lets your AI publish on your behalf.

Sign up free →
ii.

Connect your AI

Add scsiwyg to Claude, ChatGPT, Cursor, or Windsurf. Copy one config block — that’s it.

Setup guide →
iii.

Start writing

Tell your AI what happened today. It drafts, you approve, it’s live. Teams can blog together too.

See examples →

The CMS is closed.
The page is open.