Documentation

Reply Angles

The reply panel suggests two or three one-line angles per tweet instead of drafting. You write the reply. BlackOps tracks your sent rate per Hunt.

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 a short headline naming the move, followed by a sentence or two explaining what you would say and why it fits this tweet.

Ask: Ask whether the renders hold up once a client wants changes

The tweet calls the results scary good. Asking what happens after the first round of client feedback moves the conversation from a demo to real work.

Angles start from the tweet itself. Each one responds to something specific the tweet says or shows, so you can tell which tweet it was written for. Your brain notes and recent posts are background, used only when they genuinely connect.

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. An Add experience angle always has an anchor: without a note that holds the experience, it is not shown at all, so the panel never suggests you share something you did not do.
  • 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.
  • An Interview button. Answer one question and your answer becomes the reply. See Interview Mode.

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 usually come back in a few seconds. If a request takes longer than twelve, it stops and tells you, and Write full draft still works.

Where Angles Come From

Two things can put a tweet in front of you: one of your Hunts, or its overlap with what you recently posted (your tweets, your blog posts, and your past replies). Each tweet gets one of these as its source, and the score and angles both come from that source.

  • A Hunt matches. The tweet shows the Hunt's badge and score. The angles follow that Hunt's goal and brain.
  • No Hunt fits, but it relates to your recent posts. The tweet shows one relevance score. The angles build on what you already said: they extend it, apply it to this tweet, or push back from it, and can anchor to your own tweet or post.
  • Neither. The tweet shows a plain skip with the reason, and no score. A skipped tweet is never ranked.

A Hunt wins when both apply. Some posts are skipped whatever their relevance: posts that are a bad place to show up, promotional or engagement-bait posts, and threads you already replied to.

On your home timeline, Hunts are checked only when you open the reply panel. Opening it can change the badge: a Hunt can take over the tweet, or a post the Hunt check rules out can turn into a skip.

Interview Mode

A draft written for you rarely sounds like you. Interview Mode goes the other way: you say what you think, and the panel only tidies it up.

  1. Press Interview on the angle you want. The card opens with one question.
  2. Answer in your own words. Rough is fine: a sentence or two, typos and all. Press Shape reply, or Cmd+Enter.
  3. Your answer comes back as a reply in the reply box. Edit it, then press Add to Reply. Nothing is sent until you press Reply on X.

The edit may cut filler, fix typos and reorder what you said. It may not add anything. Every claim, number, name and link in the reply has to come from your answer. If the edited version brings in a number, a name or a link you did not give, it is thrown away and your answer comes back as you wrote it, with a note saying so.

Add experience angles get a question written for that tweet, because they need something only you know. Push back, Ask and Agree + extend use a plain question for their type, such as "Where does this not match what you've seen?" The angle above the question gives it the context.

Back to angles returns to the list if you want a different one.

Every interview also teaches the voice digest how you talk. Your answer is saved exactly as you typed it, next to the tidied reply. If what you send differs from the tidied version, that edit is recorded as a voice correction with your original words attached. The digest then sees what the tidy-up changed that you put back, and can suggest a rule to keep your wording next time. A reply sent exactly as tidied is not a correction, and nothing is recorded when your answer came back as written.

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

Want this page as machine-readable markdown? GET /docs/features/reply-angles.md