WeMAIde Content Operator: A local-first workspace for multi-platform content

Hi Product Hunt 👋 I’m Alexandr from WeMAIde, and we built Content Operator because our content workflow had become a collection of prompts, documents, browser tabs, and mental reminders. Generating text was not the main problem. The difficult part was keeping the operation reliable: - Which product facts are approved? - Did an AI draft introduce a claim we cannot support? - How should the same idea change for each platform? - Which version was actually reviewed? - What is ready, scheduled, or already published? - What happens if someone edits a scheduled post? WeMAIde Content Operator brings that workflow into one local-first Windows application. It separates context into three clear layers: 🧭 Brand Profile — positioning, audience, tone, goals, and communication boundaries. 📚 Knowledge — imported local files and folders containing verified product and project information. 📝 Notes — direct facts or instructions that matter for the current content task. From that source material, the application can prepare independent drafts for LinkedIn, X, Threads, Telegram, Instagram, and Facebook. Each version can have its own language, length, CTA, hashtag preference, visual direction, status, and calendar position. The current workflow uses four visible states: Draft, Ready, Scheduled, and Published. If a scheduled draft is edited, it is removed from the calendar and must be reviewed again. Approval belongs to the version that was reviewed — not permanently to the title. Content Operator also supports manual content creation, search, version history, a recoverable archive, controlled deletion, and a working local editorial calendar. The workspace stays on the Windows computer, credentials use Windows secure storage, and selected context is sent directly to the configured OpenAI provider through the Responses API with store: false only when generation is requested. An important note about this milestone: social OAuth, automatic publishing, background retries, and final image rendering are not enabled yet. We are validating the full knowledge → creation → review → scheduling workflow before connecting external accounts. We would especially value feedback from founders, content operators, agencies, and small product teams: 1. Which part of your multi-platform workflow creates the most friction today? 2. What would you need to trust scheduled automatic publishing? 3. Would you prefer a local-first desktop tool or a shared cloud workspace for this kind of system? Thanks for checking out what we’re building. I’ll be here to answer questions and share what we learn. — Alexandr, WeMAIde