For experts and media buyers who run a blog and sell through content
Every idea becomes a material with versions, a folder and a release date. Arrows show what grew out of what, and AI only follows the voice rules you have approved.
Sound familiar?
The Reels idea is in your phone notes. The script is in a doc called “final_v3_really”. DM questions that would make a great series are buried in Telegram’s Saved Messages. What’s already filmed and what’s still a plan exists only in your head.
And when you ask AI to finish a post, you get a smooth text that sounds like everyone else. You end up putting your own voice back by hand, every single time.
So I built a workspace where the idea, the text, its versions, the plan and your voice live together.
How it works
A material gets its ID when it’s created and keeps it through edits, moves and publishing. So you always see where it came from, which version went live and where it is now.
From a note, an idea in Dayveo, a news item or a breakdown of someone else’s video. It lands in a folder and on the canvas, linked to its source.
A Reels template with the hook, voice-over and shots. You save a named version at every stage.
A carousel, a Threads post and a Telegram post become separate materials, with arrows showing what came from where.
A prep date, a release date and a checklist: script, video and captions, cover, final review.
Add the post URL or ID, and the material becomes “Published”, tied to the exact text version.
Content OS never publishes for you. It only reads social networks, and there’s no “publish” button by design.
Space
Materials sit on the canvas as cards. “Origin” arrows lead from a YouTube breakdown to a Reel, a carousel and a post, “Release order” shows the sequence, and “Funnel” shows the path to a lead. A series gets a frame you can drag as a whole.
Folders · Board · Tree
Space is for links, Board is for statuses, Tree is for keeping folders tidy. A card’s status updates itself: with a release date it’s “Scheduled”, with a confirmed post it’s “Published”.
Editor and versions
Scripts are written in a full editor: headings, lists, checklists, inline images. The draft saves itself, and “Save version” captures a named stage. Any version opens side by side with the current one, and you can restore it as a new version.
Release plan
Every material has two dates: “Prepare by” and “Release”. The week view shows both, the release queue lists everything in order. “Ready” only switches on when the checklist is confirmed for the current text.
Author system
You mark your own texts as voice examples. “Find patterns” looks for recurring moves within one channel and proposes a rule backed by exact quotes from at least three different materials. A rule only goes to work after you accept it.
Modules
ReelsMaker takes jobs for a transcript, a frame check and the final export, and the finished file comes back to the library. Creo provides briefs, creative layouts and creative batches. Ideas from Dayveo land in the Inbox, and Dayveo itself stays untouched.
Mac worker
A separate process on your Mac connects to Content OS on its own and picks up jobs: local module calls, Claude Code, video downloads and speech recognition. It never accepts arbitrary commands, only allowed actions.
Details
The month’s focus, a shoot reminder, a series idea. They sit next to the cards but aren’t materials and stay out of the plan.
A deleted material or folder comes back with the same versions and links. After 30 days it’s cleared automatically.
A YouTube or Reels link → captions or on-Mac speech recognition → a breakdown → a new material.
RSS from sources you trust, similar headlines grouped, a morning summary and a “Use in content” button.
The exact text version, caption, cover and files in one ZIP. You publish yourself without mixing anything up.
Every 3 hours a snapshot goes to a private repo: a full SQL dump and every material as a separate Markdown file.
Who it’s for
Writes about ads, shares case studies and sells audits or account management through Reels, carousels and Threads.
Cuts one long breakdown into several formats and wants to see what’s out and what still needs filming.
Uses AI, but wants the texts to sound like them, not like a template.
Numbers and limits
FAQ
No, you do. Content OS prepares a package with the exact text version, caption and files, and after publishing you add the post URL or ID. Publishing actions are blocked for AI and automations.
AI helps with drafts and adaptations if Claude Code is connected. But you set the voice: a request only includes the rules you approved for that channel. A one-off request in chat never changes your standing rules.
You mark your own texts as voice examples, at least three in one channel. AI looks for recurring moves and proposes rules with word-for-word quotes. You accept, edit or reject each one. The model isn’t retrained: approved rules are simply added to its context.
Through MCP modules. ReelsMaker handles transcripts, frame checks and export, Creo provides briefs and creative batches, and Dayveo ideas arrive in the Inbox read-only. Each tool runs on its own, and Content OS ties them together.
On your Mac, in a local database. Backups can go automatically to your private Git repo: a full dump plus every material as Markdown.
No. It’s a personal workspace for one author: no roles, no shared access and no separate client accounts.
Content OS is my personal tool, not a subscription service. Message me on Telegram: I’ll show you how it works, and we’ll talk about what would fit your blog.
I’ll walk you through the canvas, the editor, the release plan and the Author system, and we’ll see how it fits your blog.
Talk on TelegramOther products