Schedule up to 3 reposts and 3 reshares the moment you compose. Configurable delays from one hour to one year. Same picker in the composer, the calendar modal, and the chat publish dock — so the decision lives where you make it.
Native re-broadcast where supported, or a fresh copy where it isn’t — both in one panel.
Hard cap matches our existing recycle limits. Six total recycles per evergreen post.
Preset chips for +1d, +1w, +1mo, plus a custom offset with h/d/w/mo units.
Composer, calendar modal, chat publish dock — identical UX everywhere.
A recycle landing in a blocked window is nudged to the next valid slot.
Recycled posts show up on the calendar with a recycle badge linking back to the source.
Cancel, edit, or add recycles from the post detail drawer at any time.
Recycle entries are first-class in the publish API, so AI agents can set them too.
Use the composer, calendar modal, or chat publish dock — whichever surface you start in.
Collapsible "Auto-recycle this post" section below the schedule picker. Two chip rows: Repost and Reshare.
Tap preset chips (+1d, +1w, +1mo) or set a custom offset. Up to 3 per kind per source.
Recycles auto-schedule the moment the source publishes. Visible on the calendar with a recycle badge.
A Repost is the platform’s native re-broadcast — the original post resurfaces on the feed (where supported). A Reshare creates a new copy of the post and publishes it as a fresh entry. Both keep your evergreen content circulating, but Reshare is supported on every platform Aidelly publishes to; Repost is platform-dependent.
Two reasons. First, recycle decisions are usually the same kind of decision as the schedule itself — you make them together. Second, scheduling at compose ensures the recycle plan ships with the post even if you never look at the calendar again. The Inbox / calendar still let you tweak after the fact.
Up to 3 reposts and 3 reshares per source post — six total recycles per piece of evergreen content. Delays range from a minimum of 1 hour to a maximum of about 1 year. Hard-capped at the schema layer so a misconfigured rule can’t balloon into runaway publishes.
Three surfaces, identical UI: the post composer (the main place), the calendar schedule modal (when editing a scheduled post), and the chat publish-confirm dock (when an agent is about to publish). They share the same picker component so behavior matches everywhere.
Yes. A scheduled recycle still runs through posting cooldowns, quiet hours, and warning rules. If a recycle would land during a blocked window, Aidelly nudges to the next valid slot rather than firing into a quiet period.
Yes. The recycle entries live as separate scheduled_posts rows linked to the source. Edit, cancel, or add more from the post detail drawer — same as any scheduled post.
Set the recycles when you set the publish. Ship once, circulate six times.