Threads and comments

Follow-up comments

Thread replies and follow-up comments after the main post — with delays between parts.

A post can have more than one part: a main post (caption plus media) and optional parts in Follow-up comments.

Those parts publish as thread replies on Threads and X, and as comments on Instagram, LinkedIn, and Facebook. They can be a thread reply, or a comment on your own post.

Where in the composer

The Follow-up comments panel appears when your selection includes Threads, X, Instagram, LinkedIn, or Facebook.

Adding a follow-up

Where: In the post editor, open the Follow-up comments section. Use the pink Add … button below Drag & drop section.

The button label follows the focused channel:

Each follow-up comment row has its own text field, a reply toolbar under the text area, a Delay control, and row actions:

Reply toolbar

Each follow-up comment row includes a toolbar, but limited to actions that work on thread replies or comments:

You can only drag and drop images or videos onto a follow-up comment row when that network supports media. Instagram and LinkedIn follow-up comments stay text only.

Delays between parts

Delays help in two ways. They spread Follow-up comments so a thread reads at a human pace.

They also let you put a link in a later reply or comment. Many networks treat links in comments more leniently than links in the caption.

OpenQuok shows an approximate clock (≈) from your post’s scheduled time, adding each prior follow-up comment row’s delay in order.

On Threads, the UI may add a small buffer for publish. Meta can still take longer to show thread replies live.

What each platform does

Cross-account plugs (from Plug settings) are separate from same-account Follow-up comments. Threads, X, and LinkedIn support them — see Cross-account plugs and below.

Per-network caps on the main post still apply. See Posting rules by platform.

Thread finisher

For Threads and X, open Settings while that channel is focused. Enable Thread finisher to post a closing message after all Follow-up comments.

The default message is That's a wrap! You can edit it. The finisher runs at the end of the thread, not between every follow-up comment row.

On Threads only, Settings also offer a delayed engagement reply — one extra same-account comment after the finisher. That is an internal plug, not a Follow-up comments row.

CLI and API users set finisher fields under threads.enabled / threads.message or the X finisher bucket; the engagement plug uses threads.internalEngagementPlug. Examples are in CLI examples — Threads and CLI examples — X.

Cross-account plugs

Settings can schedule cross-account plugs — comments from another connected channel after publish (supported on Threads, X, and LinkedIn).

See Cross-account plugs for setup steps. OpenQuok runs plugs after the main post (and after Follow-up comments when configured).

Multi-channel and Global mode

In Global mode, one Follow-up comments program is copied to every selected Threads, X, Instagram, LinkedIn, and Facebook channel. The same text, delays, and media (where the network allows it) apply to each supported network.

When only one network should differ, focus that channel and customize — see Global vs per-channel. In per-channel mode, Follow-up comments edit only while a supported channel is focused.

Write for every network

A safe pattern when several supported networks are selected together:

• Put must-have media on the main post so Instagram and LinkedIn still publish correctly (their Follow-up comments are text only)
• Use media on follow-up comment rows only on Threads, X, or Facebook when that channel is focused and the extra attachment is intentional

Agents, CLI, and API

Outside the dashboard, Follow-up comments live in providerSettingsByIntegrationId under each channel’s bucket (replies[] — Follow-up comments in the composer):

Each entry uses message and delaySeconds. On networks that allow media on Follow-up comments, add media (flat array or media.items — same shapes as the main post). Upload files for Follow-up comments with openquok upload before posts:create; main-post -m does not attach to follow-up comment rows automatically.

Copy-paste recipes:

• CLI examples — Threads — text and media on threads.replies[]
• CLI examples — X — up to four images per x.replies[] row
• CLI examples — Facebook — one image per facebook.replies[] row
• CLI examples — Instagram — text-only instagram.replies[]
• CLI examples — LinkedIn — text-only linkedin.replies[]

Agent JSON examples (replace placeholders, then openquok posts:create --json …): threads-follow-up-reply-with-image.json, x-follow-up-reply-with-image.json, and facebook-follow-up-comment-with-image.json in agent/skills/openquok-core/resources/examples/.

See Managing posts and Provider settings for request shapes.

Related