Reply Cadence Engine

Knowing how to reply well was never the problem. Doing it every day is. The Reply Cadence Engine turns the reply workflow from a discipline problem into a checklist: at your chosen time each day, BlackOps searches your active Hunts, ranks what it finds, drafts a reply to each target worth answering, and stages the whole set as a queue. You get a notification that says "5 replies ready to send." You review, you send, you're done for the day.

Sending stays yours. The X API cannot post replies, and BlackOps would not want it to. Every draft is staged into X's native composer by the Chrome extension for you to read, edit, and fire.

How it works

1. You set a cadence. In Reply Queue settings, pick a ready-by time, your timezone (auto-detected), and a daily goal. That's the whole setup. No schedulers, no webhooks, no tool calls.
2. The queue builds itself. Before your ready-by time, the queue builder searches X for each of your active Hunts, ranks every hit with the same 0 to 100 value score used by Ranked Reply Targeting, and keeps only targets above your quality bar (60 by default). Quality over volume: a thin day stages three great targets, not ten mediocre ones.
3. Every target arrives pre-drafted. Each staged reply runs the full drafting pipeline the extension's reply panel uses: grounded in the Hunt's intent and your bound brains, anchored to a concrete fact you actually know, critiqued, refined, and conformed to your brand voice. Targets with nothing worth saying are held back, not padded.
4. You get pulled back in. When the queue is staged, a push notification links straight to it. Works on desktop browsers and on iPhone or iPad when BlackOps is added to your Home Screen.
5. You work the queue. Open each item on X. The Chrome extension stages the draft into the native reply composer. Read it, change it if you want, hit reply, mark it sent. Hit your daily goal and the day is complete.

Found, but held back

Not every good target gets a draft. When a tweet clears your quality bar but nothing concrete in your brains bears on it, the drafting gate holds it back instead of writing a generic reply. Held-back targets appear in their own section on the queue page with the tweet, its score, and why it was held.

Each one has a Draft anyway button. Click it and the full drafting pipeline runs for that single target, grounded in the Hunt's intent and your brand voice, and the result moves into your working queue for review. Nothing is ever drafted for a held-back target until you ask — the button is the only path. You can also dismiss any of them.

The queue page also shows each day's build in plain numbers: how many targets were found, how many cleared your bar, how many were drafted, and how many were held back. A thin day is explained, never mysterious.

The streak

Progress compounds when the loop runs daily, so the queue tracks it:

• Progress shows sent count against your daily goal, on the web queue and in the extension.
• Done for today renders the moment you hit the goal.
• Streak increments each completed day and resets on a miss. Your best streak is kept.

Configuration

| Setting | Default | What it does | |---|---|---| | Ready by | 09:00 | Local time your queue should be staged by | | Timezone | Auto-detected | IANA timezone the schedule runs in | | Daily goal | 5 | Replies sent for the day to count as complete | | Quality bar | 60 | Minimum value score a target needs to be staged | | Notify me | On | Web push when the queue is ready |

The queue builds from your active Hunts with search keywords. No active Hunts, no queue. Create one at Hunt Missions or ask your AI assistant to create_hunt.

Reading the queue from chat

Any connected MCP client can read the queue with get_reply_queue: the staged items in work order, drafts included, plus progress and streak state. Useful for a morning "what's in my queue today?" without opening the app. The tool is read-only. Sending always happens on x.com.

Related

• Ranked Reply Targeting — the Hunt definitions and value score the queue builds from
• Fact-Anchored Replies — why drafts lead with a concrete fact or don't exist at all