Creator OS
ai videoclaude codecreator osinstagram trial reelsmcp server

Post Trial Reels With Claude Code: 2026 Terminal Workflow

Generate and publish Instagram trial reel variants straight from the terminal using the Creator OS Claude Code plugin and hosted MCP server, with prompts shown.

Creator OS · November 8, 2026 · 9 min read

To post trial reels with Claude Code, you install the Creator OS plugin in your terminal, let the agent draft variants from a brief, then call the MCP create_post tool with trial_reel set to "auto" or "manual". The post goes out as a Trial Reel, visible to non-followers first, without you opening the Instagram app.

brief (text)
   |
   v
Claude Code + Creator OS plugin
   |  drafts 2-3 variants
   v
create_post (MCP)  --trial_reel "auto"
   |
   v
Creator OS  -->  Instagram Graph
   |
   +--> shown to non-followers first
   |
   +--> post_type short_video, trial_reel set
        |
        v
GET /v1/analytics/posts  --> reelsSkipRate,
                              avg watch time
One loop: brief, draft, publish as trial, read the numbers.

What Does It Mean to Post Trial Reels With Claude Code?

It means the agent holds the publishing credential and the platform rules, so you describe the Reel in plain language and it calls the tool.

Claude Code is Anthropic’s terminal agent. Creator OS connects to it two ways: a Claude Code plugin that adds skills, commands and a publish guard, and a hosted MCP server that exposes about 160 tools. Instagram Trial Reels are Reels shown to non-followers first. Instagram then either shares them to followers based on performance or waits for you to share them yourself.

Put together, the loop is: you write a short brief in the terminal, Claude Code proposes variants, you approve, and one tool call publishes each variant as a Trial Reel. No browser tab, no upload screen, no copy-paste of the caption.

Two rules matter before anything else. Instagram only allows Trial Reels on accounts with 1,000+ followers, and Creator OS refuses the post up front below that with trial_reel_needs_followers and suggests a regular Reel instead. And the API cannot attach trending audio, so sound has to be baked into the file you upload.

Get started for $0

How the Creator OS Claude Code Plugin and Hosted MCP Server Fit Together

The MCP server is the hands. The plugin is the workflow around them: skills, slash commands, a live pane and a guard that asks before anything publishes.

Piece What it gives you
Hosted MCP server https://mcp.creatoros.ca/mcp, nothing to install, about 160 tools including create_post, get_post_analytics and get_best_time_to_post
Claude Code plugin Adds the MCP server plus Meta, TikTok, Google and LinkedIn campaign builder skills and Agent Posts, a live pane (/creatoros), /cos-stats, /cos-health, a status line, and the publish guard
Publish guard Asks Proceed or Cancel before anything is published, spent or deleted
Skills on disk npx @creatoros/cli@latest init installs 14 skills, including post-shortform and analytics

The plugin needs Claude Code 2.1.287 or later. If you only want the tools and not the mod, you can add the MCP server by itself and skip the plugin install. The Claude Code plugin docs and the MCP docs cover both paths.

Setting Up: Plugin Install, MCP Auth, and Your First Terminal Session

Setup is three commands and one key, and the key lives in Settings > API keys as a cos_live_... token pinned to one workspace.

  1. Add the marketplace and install the plugin, then configure it with your key:
/plugin marketplace add kevinbadi/creatoros-claude-plugin
/plugin install creatoros@creatoros
/plugin configure creatoros@creatoros

If you prefer the bare MCP route instead, one command does it:

claude mcp add --transport http creatoros https://mcp.creatoros.ca/mcp \
  --header "Authorization: Bearer cos_live_..."
  1. Install the skills and check the connection:
npx @creatoros/cli@latest init
creatoros auth:check
creatoros accounts:list

You should see your Instagram account with an acc_ id. That typed token is what the rest of the workflow references. Keys are scoped to one workspace, so an agent holding one client’s key cannot post to another client’s account. Read-only keys are available too, and the API refuses writes from them.

If you want a walkthrough of the setup on screen, the KevBuildsApps YouTube channel has the install and first-post runs.

The Exact Prompts: Turning a Brief Into Trial Reel Variants

Write the brief as constraints, not adjectives. The agent needs a hook, a length, a target viewer and a file, and it needs to know it is making a trial.

Here is a prompt that works, typed straight into the session:

Draft 3 Trial Reel variants for my Instagram account.
Topic: why my first 10 posts got zero reach.
Audience: people who just started posting, not my followers.
Length: 18-24 seconds each.
Rule: hook in the first 2 seconds, one idea per video,
no music references I cannot bake into the file.
For each variant give me: hook line, on-screen text,
caption under 300 chars, and the first comment with my link.
Do not publish yet.

The last line matters. Without it a confident agent may go straight to publishing, and the publish guard will ask Proceed or Cancel anyway, but it is cleaner to separate drafting from posting. Ask for variants one at a time when the topic is subtle and three at once when you are testing angles.

A second pass tightens the winner:

Take variant 2. Cut the setup line. Give me two hooks
I can test: one question, one number. Keep the caption
identical so the only variable is the hook.

That is the whole value of the terminal workflow. Variants are cheap to produce, and because they publish as trial status, non-followers decide which one is worth sharing before your audience sees any of them.

The Exact Tool Calls: Publishing Variants to Instagram Trial Status

One tool call publishes each variant, and the only thing that makes it a trial is the trial_reel field next to post_type: short_video.

Through MCP, the call looks like this:

create_post
  platforms: ["instagram"]
  post_type: "short_video"
  trial_reel: "auto"
  content: "<caption>"
  media: ["https://.../variant-2.mp4"]
  firstComment: "full breakdown: https://..."

"auto" means Instagram shares the Reel to followers if it performs well with non-followers. "manual", or plain true, means you share it to followers yourself from the Instagram app. The advanced REST form sends trialParams.graduationStrategy as MANUAL or SS_PERFORMANCE. The REST path is spelled out in the Trial Reels API walkthrough.

The same publish from the CLI, if you want to see exactly what will be sent:

creatoros media:upload ./variant-2.mp4
creatoros posts:create \
  --text "Your first 10 posts were not the problem." \
  --platforms instagram \
  --media med_... \
  --scheduledAt 2026-03-04T18:30:00Z --timezone America/Toronto

Note what the CLI does not do here: posts:create has no trial flag, so use the MCP tool or the API for the trial field. The CLI is best for uploading media and checking the result afterward.

creatoros posts:list --status published --limit 5
creatoros analytics:posts --platform instagram --sortBy engagement

Two fields to read once the Reel has views: reelsSkipRate, the share of views that swiped away in the first three seconds, and igReelsAvgWatchTime in milliseconds. Both come back from get_post_analytics. Meta reports them for Reels only. An agent can read them after publishing and change the next hook, length or topic. Creator OS supplies the posting and the numbers. Your prompt decides what changes.

Can Claude Code Edit and Re-Render Variants In Claude Code Before Posting?

Yes, if you install the open-source OPEN VIDEO EDIT skills, which render locally with Python and ffmpeg and hand back a finished file.

From the open-edits repo, the skills include split-animated-talking-head, fireship-style-short, split-animated-short and reverse-engineer. A raw talking-head clip goes in. Captions, logos, faces, GIFs, b-roll cards and counters come out. The result is a vertical file you can pass straight into create_post.

A practical chain in one session:

Use split-animated-short on ./raw-hook.mp4.
Bold captions, word synced, keep it under 22 seconds.
Then compare the hook against variant 2 and tell me
which opening frame reads faster at 1x speed.

Two limits to plan around. Rendering happens on your machine, so a long clip costs real time. And the API still cannot attach Instagram’s trending audio, so any sound must be inside the rendered file before upload. If you edit video this way often, the local AI video plugin post covers the render side in more detail.

What This Workflow Does Differently From the Instagram Trial Reels API

The API gives you one endpoint. The terminal workflow gives you a drafting partner, a guard before spend or publish, and a loop that reads the numbers back into the next draft.

Step Direct API Claude Code + Creator OS
Writing variants You write them Agent drafts from a brief, you pick
Publishing Your script calls the endpoint create_post with trial_reel, guard asks first
Reading results You fetch and interpret Agent reads skip rate and watch time, proposes the next hook
Editing Elsewhere OPEN VIDEO EDIT skills render in the same session
Other clients Separate credentials per workspace One connection per workspace on agency plans

A dashboard-style scheduler is a calendar with a compose box. Creator OS also ships a hosted MCP server, a CLI and a plugin, so an agent can run the posting, the replies and the reading while you stay in the terminal. If you are weighing that against a dashboard tool, the SocialBee alternative post frames the same difference.

One honest limit: Instagram exposes no field saying whether or when a Trial Reel was shared to followers. You will see watch stats and skip rate, not a graduation timestamp. Plan reporting around the numbers that exist.

FAQ

How do I post trial reels with Claude Code step by step?

Install the plugin with /plugin marketplace add kevinbadi/creatoros-claude-plugin, then /plugin install creatoros@creatoros and /plugin configure creatoros@creatoros with your cos_live_ key. Ask the agent for variants and stop it before publishing. Then call create_post with post_type: "short_video", trial_reel: "auto" or "manual", and the media.

Can Claude Code publish to Instagram trial status automatically?

Yes, once you approve. The plugin’s publish guard asks Proceed or Cancel before anything is published, spent or deleted, so the agent cannot fire a post without your yes. After that the tool call sets trial status on Instagram. If your account is under 1,000 followers, Creator OS refuses with trial_reel_needs_followers and suggests a regular Reel.

What is the Creator OS hosted MCP server and do I need it?

It is a hosted server at https://mcp.creatoros.ca/mcp that exposes about 160 Creator OS tools to any MCP-capable app, including Claude, ChatGPT and Claude Code. You need it, or the plugin that adds it, for the agent to publish anything. Nothing is installed for the server itself; you install the plugin only if you want the skills, commands and guard.

Is this different from using the Instagram trial reels API directly?

The API is the endpoint, and you drive it with your own code. The terminal workflow puts an agent in front of the same publishing path so variants get drafted, published and read back in one session. Both can set trial_reel; the difference is who writes and interprets the surrounding work.

Can I generate trial reel variants from Claude Code for TikTok or CapCut too?

Claude Code can draft variants for TikTok, and Creator OS publishes TikTok videos and photo carousels, with draft: true sending a video to the TikTok Creator Inbox to finish in the app. Trial Reels themselves are an Instagram feature, so the trial_reel field applies to Instagram only. Editing and rendering happen through the separate OPEN VIDEO EDIT skills.

Get Started: Generate Your First Claude Code Trial Reel Today

Start with one account, one brief, three variants, and read the skip rate the next morning. That single loop teaches you more about hooks than a month of guessing.

Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. Sign up at https://www.creatoros.ca/sign-up, create a cos_live_ key in Settings > API keys, and run the three setup commands. Then watch the launch video and the rest of the KevBuildsApps channel for the working examples.

For the full tool list and every post option, the docs at https://www.creatoros.ca/docs are the reference.

Get started for $0
Free trial for new subscribers. Cancel anytime.

Keep reading