← All posts

How Autopilot keeps your feed active while you're deep in building

Set up MarketMee Autopilot to watch your repos, turn new commits into posts, and keep your feed active even during heads-down building weeks.

· 6 min read· By MarketMee Team
  • autopilot
  • developer marketing
  • build in public

There's a familiar pattern for anyone who builds software: you disappear into a feature for two or three weeks, ship something you're proud of, and then realize your social accounts have gone quiet the entire time. The work was happening—it just never made it out of your Git history.

MarketMee's Autopilot is designed to close that gap. It watches your GitHub repositories, turns new commits into posts on a cadence you choose, and drops them into your posting queue so your feed stays active while your attention stays on the code. Here's how to set it up so it runs in the background and sounds like you.

What Autopilot actually does

Autopilot is the hands-off side of MarketMee. Instead of opening the app to review commits every time you ship, you configure it once per repository and let it run:

  • It checks for new commits on the cadence you set.
  • For everything shipped since the last run, it generates content—images, videos, or both.
  • It adds those posts to your queue, where they land in your next open schedule slot (or publishes them immediately, depending on your settings).

The important part is that it picks up everything shipped since the last run. You don't have to remember which commits you've already posted about—Autopilot tracks that for you and only works with what's new.

Setting up a repository

Everything happens on the Autopilot screen in the sidebar.

  1. Go to Autopilot and connect a GitHub account, then select a repository.
  2. Configure that repository's settings (covered below).
  3. Toggle Autopilot on.

The first run happens at the next scheduled time. If you'd rather not wait, use Run now to trigger a run immediately—useful for confirming the output looks right before you walk away.

A quick prerequisite check: Autopilot needs a GitHub account with at least one repository connected, and at least one social account connected so it has somewhere to publish. All generation features also require a paid plan, which start at $19/month with a monthly token allowance.

Choosing what Autopilot makes

For each repository, you decide the shape of the content:

  • Content: Choose Images, Video, or Both.
  • Video style (if Video is selected): Classic or Motion.
  • Image style (if Images is selected): Pick your preferred image and headline styles. Autopilot rotates through them, so your feed doesn't look like the same template every time.
  • Voice narration (if Video is selected): On or off.
  • Sound effects (if Video is selected, Classic mode only): On or off.

If you're not sure, Both gives you a mix of square marketing images and narrated videos, which tends to keep a feed feeling varied without any extra effort on your part.

Picking a cadence that matches your rhythm

The Check for new commits setting is where you match Autopilot to how you actually work. There are five cadences:

  • Every hour
  • Every 6 hours
  • Every 12 hours
  • Daily
  • Weekly

If you're in a heavy build phase and pushing commits all day, a Daily check usually strikes the right balance—frequent enough to stay current, spaced enough that each post represents a meaningful chunk of work. If you ship in bigger, less frequent batches, Weekly keeps things tidy. Teams that want near-real-time announcements can go as tight as Every hour.

Because your posting schedule and your check cadence are separate settings, you're never flooding your feed. Autopilot generates the posts; your Posting schedule (set in Settings) controls when they actually go out. New posts simply land in the next open slot in your queue.

Keeping your voice with standing instructions

The feature that makes Autopilot feel like you rather than a generic bot is Instructions. For each repository, you can write up to 1,000 characters of standing instructions that apply to every run.

This is where you set the tone and the angle. A few examples of what's worth putting here:

  • Audience: "Write for agency owners, not other developers."
  • Focus: "Focus on the new billing dashboard and the time it saves."
  • Tone: "Keep it plain and confident—no hype words, no exclamation marks."

Autopilot carries these instructions into every run, so you don't have to re-explain yourself each week. Set them once, and the voice stays consistent across every post it makes.

Choosing where posts go

Under Post to, select which connected social accounts Autopilot should publish to. MarketMee publishes to LinkedIn company pages, X, Facebook, and Instagram today, with TikTok, YouTube, Threads, and Pinterest being added. Posts from Autopilot go to the same queue and Timeline as everything else, so manual posts and automated ones live side by side.

What happens during a quiet week

The most common worry with any automated posting tool is the dry spell: what happens when you don't ship anything? A week of deep debugging or planning can mean zero new commits—and a tool that only posts from new commits would simply go silent, which defeats the purpose.

Autopilot handles this with quiet weeks. If there are no new commits on a run, it finds an earlier commit worth talking about and builds a post from that instead. Your feed keeps moving even when your Git history doesn't, so there's no visible gap for your audience during the weeks you're heads-down.

Checking the results

You don't have to trust it blindly. The Recent runs view on the Autopilot screen shows you exactly what happened on each run:

  • Which commits were picked up
  • Which posts were made
  • The status of each run

This is the panel to glance at when you resurface from a build sprint. If something didn't generate the way you wanted, you can adjust the instructions or styles and let the next run reflect it. And since failed generations refund their tokens automatically, an off run doesn't cost you anything.

A sensible starting configuration

If you want a setup that just works while you build, try this per repository:

  • Content: Both
  • Video style: Motion for a more cinematic feel, or Classic if you want scene-by-scene control
  • Image style: Pick two or three styles you like so the rotation stays fresh
  • Cadence: Daily
  • Instructions: One or two sentences on your audience and tone
  • Post to: Your two or three most active accounts

Toggle it on, hit Run now once to sanity-check the first batch, and then forget about it. The whole point is that your marketing keeps pace with your shipping without pulling you out of the work.

You can set all of this up at marketmee.app—connect a repo, write your instructions, and let Autopilot keep the feed warm while you go build the next thing.

Get a free narrated video of your own product, made from your own code

Sign up and connect a repository, and MarketMee will make you a narrated video and three marketing images, free. If you like what you see, choose a plan and switch on Autopilot.

Make my free video

No credit card. Plans start at $19 a month, with every feature included.