You schedule a launch week with the Creator OS CLI by writing the week as one JSON calendar file, dry-running it with creatoros posts:bulk-upload --file launch.json --dryRun, then running the same command without the flag. The CLI drives 11 platforms plus Skool from your terminal, so a whole launch week goes out from one session without a dashboard.
LAUNCH WEEK PIPELINE
launch.json --+
teaser.mp4 --+--> creatoros posts:bulk-upload --file launch.json
caption.txt --+ |
+--> posts:list --status scheduled (verify)
+--> inbox:reply / private-reply (day of)
+--> automations:create (keyword funnel)
+--> skool:multi-post (announce)
+--> blog:create --schedule (SEO post)
What the Creator OS CLI Does for Launch Week Scheduling
The CLI turns a launch plan into scheduled posts on every connected account, and it keeps that plan in a plain file you can version, diff and rerun.
The package is @creatoros/cli. Run creatoros init to set up your key and install the Claude Code skills, then confirm the key with creatoros auth:check. Keys start with cos_live_ and each one is pinned to a single workspace, which is one set of socials. A key from your launch workspace cannot post to a client workspace.
Four command groups carry a launch week:
| Command group | What it handles during a launch |
|---|---|
posts:* |
Create, update, retry, unpublish and delete posts, plus the bulk upload of a whole calendar. |
inbox:* |
Comments, public replies, private replies, DMs and conversation status. |
automations:* |
The comment to DM keyword funnel, with match modes and public comment replies. |
skool:* and blog:* |
Community announcements, member approvals, MRR reads, and WordPress or Shopify blog articles. |
Flags and the rest of the surface are documented at the CLI docs. The tool does not replace the web app. It treats a launch week as a repeatable job, and repeatable jobs belong in a command you can rerun.
How to Schedule a Week of Launch Content With @creatoros/cli
Write the launch as a calendar file first, then import it once with posts:bulk-upload and always dry-run before anything is queued.
Start by checking the accounts you plan to post to, and sanity check one caption:
creatoros accounts:list
creatoros accounts:health
creatoros validate:post-length --text "Launch day. The beta is open."Then build the week. The calendar is a JSON array of post objects. Each one carries the caption, the platforms, any media, and a scheduled time with a timezone:
[
{
"text": "Day 1: we built it. Beta opens Thursday.",
"platforms": ["instagram", "tiktok", "youtube"],
"media": ["https://cdn.example.com/teaser.mp4"],
"scheduledAt": "2026-03-02T09:00:00Z",
"timezone": "America/Toronto"
},
{
"text": "Day 3: the feature tour, 90 seconds.",
"platforms": ["youtube", "linkedin"],
"media": ["https://cdn.example.com/tour.mp4"],
"title": "Feature tour",
"scheduledAt": "2026-03-04T14:30:00Z",
"timezone": "America/Toronto"
}
]
Run the dry run, then the real import, then read back what landed:
creatoros posts:bulk-upload --file launch.json --dryRun
creatoros posts:bulk-upload --file launch.json
creatoros posts:list --status scheduled --from 2026-03-01T00:00:00Z --to 2026-03-09T00:00:00ZThe dry run reports what would be created before it creates it. Upload media once with creatoros media:upload teaser.mp4 and you get a med_ id you can reuse on every post in the week, so the same video is not uploaded five times. Any platform named in a post that is not connected comes back in missing_platforms, and the rest still go out.
For the wider pacing of a launch month, the month of content guide covers the longer arc. Launch week is the dense middle of it.
How to Schedule Threads and Replies Across Every Platform
Launch weeks live or die on replies, so schedule the follow-up work in the same sitting as the posts.
Threads are built from threadItems in the API, a list of follow-up posts for X and Threads. Comment and DM work is where the CLI earns its keep, because the volume arrives faster than you can answer by hand. Every inbox command needs the account id of the account being answered:
creatoros inbox:comments --platform instagram --since 2026-03-02T00:00:00Z
creatoros inbox:reply post_123 --accountId acc_123 --message "Thanks. Beta link is in your DM."
creatoros inbox:private-reply post_123 cmt_456 --accountId acc_123 --message "Here is your beta key."The keyword funnel is the other half. automations:create binds a keyword list to a DM on a specific post, with a match mode of exact, contains or word, and an optional public comment reply:
creatoros automations:create \
--name launch-keyword --accountId acc_123 \
--keywords "beta,access,key" --matchMode word \
--dmMessage "Here is the link and your beta key." \
--commentReply "Sent you a DM."
creatoros automations:logs launch-keywordComment to DM funnels run on Instagram and Facebook, which is where launch curiosity concentrates. Read the logs the day after launch to see how many DMs actually went out. If a short video is part of the launch, the podcast clip walkthrough applies the same single chat pattern to clips.
How to Batch Skool Announcements From One Command
Skool is where a lot of launches convert, and the CLI posts to it with the same batching idea as socials.
Announce to several communities at once. skool:multi-post takes the community slugs on a required --communities flag, comma separated:
creatoros skool:multi-post \
--communities "founders,builders" \
--title "Launch week starts Monday" \
--text "We open the beta to members first. Reply here for the link."While you are in there, read the numbers that matter for a launch. creatoros skool:revenue founders gives MRR, creatoros skool:growth founders gives the trend, and creatoros skool:pending founders shows who is waiting to get in. The pending list returns the member ids to pass to skool:approve, which are Skool’s own ids. Approving those members during launch week is often the highest leverage five minutes of the day:
creatoros skool:pending founders
creatoros skool:approve founders 4829103Skool announcements and social posts can live in the same week and the same calendar file. The Skool docs list the full command surface, including DMs, member reads and email export.
How to Publish the Same Launch Week to a WordPress Blog
The blog side of a launch is two commands, and articles stay as drafts until you say otherwise.
creatoros blog:connect-selfhosted --site https://yoursite.com \
--username admin --password "..."
creatoros blog:create --title "Launch week: what we shipped and why" \
--file launch-post.html --tags launch,product \
--schedule 2026-03-02T13:00:00ZDrafts are the default unless you pass --publish or --schedule. That default is worth leaning on during a launch: you want the SEO post read before it goes live, not after. A connected Shopify store works the same way, with a blog and a catalog rather than a posting target.
If a script or an agent is building the calendar instead of a person at a terminal, use the REST API. It is authenticated with a Creator OS API key pinned to one workspace, and read-only keys can be created in Settings. Ids come back as typed tokens such as post_, cmt_ and med_, and errors arrive in one shape: { error: { code, message, status } }. The base URL lives in the docs, and the request shapes are in the blog API docs.
How to Schedule a Launch Week Without Duplicate Posts
The way to avoid duplicate posts is to treat the calendar file as the source of truth and check it with posts:list before every import.
Duplicates during a launch come from three habits. Rerunning a bulk upload after fixing one line. Creating a post with --platforms and again with --accounts for the same account. Letting an automation and a scheduled post both answer the same comment.
- Dry-run every edit with
--dryRun, then confirm the diff withcreatoros posts:list --status scheduled. - Pick one addressing style per post.
--platformsfor a same-everywhere caption,--accountsfor a per-account variant. Never mix them for the same content. - Keep a stable reference for each post in your own calendar so you can diff it against the
posts:listoutput before the next import.
If a post does go out twice, creatoros posts:delete post_123 removes it, and creatoros posts:unpublish post_123 --platform twitter takes it down on one network only. The multi-platform scheduling guide covers getting one caption right across networks before you queue it.
Can You Schedule a Whole Launch Week in One Sitting?
Yes. A launch week of posts, replies, a Skool announcement and a blog article fits in one session of about an hour, and most of it is writing captions.
A realistic hour looks like this. Twenty minutes drafting captions and the calendar file. Ten minutes on media uploads, reusing the med_ ids. Five minutes on the dry run and the posts:list check. Ten minutes on the blog draft. Ten minutes on the keyword automation and the Skool announcement. Five minutes of buffer for a caption that runs long somewhere.
What you cannot schedule ahead is the live conversation. Answer the good questions the morning of each post, after you read creatoros analytics:posts --sortBy engagement --limit 10 for the first day. The automation handles the keyword funnel on Instagram and Facebook, but a person still answers the questions worth answering.
If the launch includes a video edit, the open source skills in the open video edit repo turn a raw talking head clip into an animated short that renders locally, and the launch video shows the wider setup. If you would rather build your own agent for the launch, the Social Agents repo runs your socials on Creator OS with your own model.
FAQ
How do I schedule a week of launch content with the Creator OS CLI?
Install @creatoros/cli, run creatoros init, and confirm your key with creatoros auth:check. Write the week as a JSON calendar, dry-run it with posts:bulk-upload --file launch.json --dryRun, then run the same command without the flag. Verify the result with posts:list --status scheduled.
Can I schedule threads and replies across multiple platforms at once?
Threads are built from threadItems in the API, and X and Threads both support them. Replies split into two jobs: inbox:reply for public comment answers and inbox:private-reply for a DM to one commenter, both requiring --accountId. Keyword comment funnels run through automations:create on Instagram and Facebook.
Does the Creator OS CLI work with WordPress and Skool?
Yes to both. creatoros blog:connect-selfhosted connects a WordPress site and blog:create schedules articles as drafts unless you pass --publish or --schedule. The skool:* commands cover posting to one or several communities, commenting, approving members and reading MRR.
How far ahead should I schedule a launch week of content?
Queue the posts at least a week ahead so the calendar can be reviewed and media checked. Launch day is the wrong time to discover a caption is too long for one network. Run validate:post-length while drafting to catch that early.
What is the difference between the CLI and scheduling posts by hand?
Manual scheduling means repeating the same clicks for every network and every post. The CLI turns the week into one file and one command, and a dry run shows you the result before anything is queued. It also reaches the inbox, Skool and blog commands in the same session.
Get started
Start at the sign-up page. Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. If you want the terminal walkthrough step by step, watch the builds on the KevBuildsApps YouTube channel, then write your launch calendar and run the dry run.
Get started for $0
Free trial for new subscribers. Cancel anytime.