Reply Angles

A drafted reply is easy to generate and hard to send. It reads like AI, and fixing one usually takes longer than writing your own. So most drafts never went out.

Reply Angles changes the job the tool does. It helps you decide what to say, then gets out of the way. You write the reply in your own words.

What You See

Open the reply panel on any tweet in X, or open your reply queue, and you get two or three angles instead of a draft. Each angle is one line of 20 words or fewer: the point you could make and the fact or experience behind it.

Push back: this breaks past 20 storefronts, UDX multi-property

Every angle carries:

• A type. Push back, Add experience, Ask, or Agree + extend. The panel tries to give you different types so you have a real choice.
• Its anchor. The fact it stands on and the brain note it came from. Anchors are checked word for word against the note. If a fact cannot be verified, the angle is labeled no anchor, opinion only rather than shown as fact.
• A Prefill button. Prefill drops a short starter into the X reply box so you are not facing a blank composer. It never sends anything. You finish the reply and press Reply yourself.

Angles never mention a product and never include a link.

When nothing about a tweet is worth adding, you get an explicit skip with the reason instead of filler. Skipping is a real answer.

Angles come back in under three seconds.

Writing a Full Draft

A full draft is still one click away. In the extension panel, click Write full draft. In the reply queue, click Write full draft on the item. Both run the same fact-anchored draft pipeline as before.

Knowing What You Actually Sent

A reply only counts if you sent it. BlackOps now records sent replies on its own, in three layers, cheapest first:

1. In the extension. When you post a reply on x.com to a tweet you opened in the reply panel, the extension sees X confirm the post and records the reply's id, the tweet it replies to, your final text, and which angle set you were shown (and which angle, if you used Prefill). A failed or cancelled post is never recorded, and replies to tweets you never opened in BlackOps are never sent anywhere.
2. On your profile. When you scroll the Replies tab of your own profile, replies the extension missed (say, ones you sent from your phone) are matched to the tweets you were targeting.
3. From X, as a fallback. An optional scheduled check reads your own recent posts from X's owned-read endpoint and matches replies to open Hunt targets. It only runs while Hunts are active and some targets have no recorded reply. Every call logs its cost, and a monthly cap stops it. It is off until it is switched on.

A reply caught by more than one layer is recorded once, with a note of every layer that caught it.

BlackOps also records which angle your final reply was closest to, so over time you can see which kinds of angles you actually use.

Sent Rate

Each Hunt now reports a sent rate: replies you sent against angle sets you were shown. It replaces the old drafted vs shipped count, which stopped meaning much once the tool stopped drafting. You see it on each Hunt in Admin → Hunts, and the Hunt tools in the MCP return angles_shown and replies_sent.

Sent can run higher than shown. A reply to a Hunt target counts however you wrote it, including targets you replied to without ever opening the panel.

Related

• Fact-Anchored Replies: the full draft pipeline behind Write full draft.
• Reply Cadence Engine: the daily reply queue, now staged with angles.
• Ranked Reply Targeting: how Hunts pick the tweets worth replying to.