Auto-recycle: a queue that fills itself, in voice

When you manage many brands, some queues inevitably run thin between attention cycles. Auto-recycle is a per-project worker that detects this and fills the gap automatically: it picks a top past post, rewrites it in the brand's voice, and schedules the new variation.

It's disabled by default. You opt in per project once the brand voice is trained.

Trigger conditions

The worker runs hourly. For each project with auto-recycle enabled, it checks three conditions before firing:

1. The project has a trained brand voice. Without one the worker can't produce in-voice output, so it skips.
2. Fewer scheduled posts in the next 14 days than the refill threshold (default 2, configurable).
3. The minimum cadence has elapsed since the last auto-recycle on this project (default 7 days, configurable).

What happens when it fires

1. Pick the top-performing past post on the project based on available engagement signal.
2. Send it to Claude with the project's voice paragraph and an instruction to rewrite — same insight, different hook, vocabulary, and structure.
3. Create one scheduled post per platform that the original targeted.
4. Set the publish time to tomorrow 09:00 in the project's timezone.
5. Stamp last_auto_recycle_at so the cadence debounce kicks in for the next tick.

Rewriting, not reposting

Publishing an identical caption a second time generally underperforms compared to the original — readers recognize duplicates and some platforms suppress them. The worker therefore rewrites rather than reposts: the system prompt instructs the AI to keep the insight but change the hook, the vocabulary, and the structure.

Because the project's voice paragraph is included in the same prompt, the rewrite stays consistent with how the brand normally sounds.

Settings

Each project exposes three controls in Settings → Auto-recycle:

• Toggle. Disabled by default. Greyed out until the brand voice is trained.
• Refill threshold. Fewer than N scheduled posts in the next 14 days fires the worker. Default 2.
• Minimum cadence. Days between successive auto-recycles on the same project. Default 7.

Visibility

Every auto-recycle run is logged. Open /app/activity and filter to a project to see when the worker fired, on which post, and what was generated. The resulting scheduled post appears in the queue alongside manual posts — you can edit, reschedule, or delete it before publish time.

Current limitations

• The publish time heuristic is tomorrow 09:00 in the project's timezone. Per-audience optimal-time selection is planned for a future release.
• The worker requires at least 3 published posts in the project to have a meaningful pool to rewrite from. Below that threshold it skips.
• Auto-recycle requires a paid plan (Pro or Agency), like the rest of the MCP-callable surface.

When to use it

Auto-recycle is most useful on projects where you don't want a fully dormant feed but can't justify daily attention. Side projects, smaller brand experiments, and long-tail products in a portfolio are the typical use cases. On flagship brands you most likely want full manual control instead.