Turn an idea, image, video, or OpenMontage project into a real social media campaign

Get started

You need a Claude subscription either way — Claude Code is what actually writes and publishes your posts. Two ways in, both ending at the same place: a working Claude Code session, open in this project.

New to all this? Download Socials Studio — no GitHub account or Git required on any platform:

• Windows (recommended): Socials-Studio-Setup.exe — sets up Python for you automatically, no Python knowledge needed. Not code-signed yet, so Windows may show a SmartScreen "unrecognized publisher" warning — that's expected for now.
• macOS: Socials-Studio-macOS.zip — unzip, run install.sh; needs a system Python 3.10+ already present.
• Linux: Socials-Studio-Linux.tar.gz — extract, run install.sh; needs a system Python 3.10+ already present, and real Google Chrome (not Chromium — chromium/chromium-browser aren't supported).

Prefer a guided page with all three, checksums, and testing notes? Use solvx.uk/socials-studio or the Releases page. The installer checks for Chrome and Claude Code, and offers to install Claude Code for you if it's missing — on Windows, as an unchecked opt-in checkbox on the finish page (WinGet if available, otherwise Anthropic's official installer); on macOS/Linux, as a yes/no prompt. Declining is fine either way — the launcher installs regardless, Claude Code just needs to be installed before you can use it. It finishes by opening a launcher — the first time you run it, Claude introduces itself and offers to walk you through connecting your first platform. It never logs into a social platform or publishes anything during setup, and never bundles or redistributes Claude Code itself — only Anthropic's own official installer, only with your say-so. CI builds and smoke-tests all three installers on GitHub's own runners before merge. The v0.1.0-beta.3 Windows installer was also installed and launched successfully on a real Windows 11 machine — the newly built v0.1.0-beta.4 binary hasn't had a separate human hardware retest of its own yet. macOS has only the automated runner test, and Linux has had its mechanics (not real Chrome/account publishing) tested on Ubuntu 24.04 x64 — see the README's testing status for the full picture.

Already use Claude Code? Install via the repository instead — the secondary, technical route:

git clone https://github.com/tradewithmeai/socials-studio.git
cd socials-studio
claude

Once Claude Code is open in the project, just ask it to set things up. Claude will explain each setup step (a Python virtual environment, dependencies, a health check) and wait for your yes each time — nothing happens silently.

Either route ends with a real, human-driven login per platform (or a one-time OAuth step for YouTube) that Claude walks you through — only asked once, the first time you connect each one.

Then just say what you want, in plain language. For example:

• "Turn this idea into a campaign for YouTube, X, Bluesky, LinkedIn and Instagram."
• "Use this OpenMontage project to prepare platform-specific posts."
• "Create several coordinated posts from this video."
• "Show me the campaign and validate everything before publishing."
• "Check how the published posts are performing."
• "Add support for another social platform."

Claude prepares and orchestrates the workflow using this repository's authentication, validation, and publishing tools — composing or extending them as your request needs. Publication always stays reviewable: nothing posts for real until you explicitly confirm it.

idea or media → Claude prepares the campaign → you review → explicit confirmation → publish to YouTube, X, Bluesky, LinkedIn or Instagram

Built for OpenMontage output — and anything else

Socials Studio has no dependency on OpenMontage's code and doesn't call into it — this is file-based compatibility, not a technical integration. It works with a finished video file from OpenMontage exactly the same way it would work with a finished video file from anywhere else, or with no video at all if the campaign is text and image only.

Ask Claude to request media from OpenMontage — or another available agentic video application — as part of preparing a campaign, and it can read whatever context an OpenMontage project already generated (its script, intended tone, target audience) to ground the copy it suggests, instead of guessing from the filename. See the OpenMontage guide for how that works and what it depends on.

What isn't available yet

Two genuine gaps, not a fixed feature list:

• Live streaming.
• Unattended or scheduled automated publishing, as a packaged, supported workflow. Claude can already prepare and execute a multi-post, multi-platform campaign in one session with your review and explicit confirmation at each consequential step — what's missing is publication that continues without you reviewing and authorising it.

A future skill can package either of these into something more discoverable, repeatable and tested once there's a proven pattern worth packaging — not the first moment the underlying capability exists. Anything not listed here as a gap is something you can already ask Claude Code to do; see the README for the full capability list.

Supported platforms

Publish videos and posts to YouTube, X (Twitter), Bluesky, LinkedIn and Instagram. See the roadmap for what's next.

Platform	Login (session creation)	Publish
YouTube	OAuth (no browser)	Yes — Data API, official path
X (Twitter)	Yes	Yes — text, image or video (browser session, not the X API)
Bluesky	Yes	Yes — text, image or video
LinkedIn	Yes	Yes — text, image or video
Instagram	Yes	Yes — reels (video)

Public beta — v0.1.0-beta.4

Prefer the raw commands? They're all still here

Everything Claude does when operating Socials Studio ultimately runs through a small, transparent set of Python publishers and a health-check script — no hidden state, nothing Claude can do that you can't inspect or run yourself. Useful for debugging, for scripting, or if you'd rather drive it entirely by hand with no agent at all:

1. python doctor.py — check what's connected, what isn't.
2. Authenticate once per platform (a real, human-driven login — this tool never automates that step).
3. Point a publisher at a file, set the title, description, and visibility.
4. Validate — every publisher checks inputs and touches no browser or API by default, until you explicitly confirm.
5. Pass --confirm-publish, then publish to YouTube, X, Bluesky, LinkedIn, or Instagram.

See the example usage and full CLI reference in the README for the exact commands.