TL;DR
- An AI fruit drama channel posts generated reality-show episodes starring a recurring cast of fruit characters.
- A ready-made template that runs on naïve: an agent team makes the episodes, you approve what posts.
- Every episode is drama, never violence.
- To start, sign up for a naïve account, then deploy the AI Fruit Drama Channel template.
An AI fruit drama channel posts generated reality-show episodes starring one recurring cast of fruit characters, and it runs as a ready-made naïve template.
There is nothing to film.
Step one is a naïve account. Then you deploy the template, and every episode waits for your approval before it posts.
What is an AI fruit drama channel?
It is one ready-made company template, not a pile of tools you wire together. When you deploy the template, naïve sets up — in a single step — a small team of AI agents, a channel dashboard to manage the queue, your connected posting accounts, and the budgets those agents run under. The fruit-drama version is a style of the faceless short-form channel — the same underlying setup, with the fruit-drama skill (a pinned set of instructions) on every agent so it already knows the format.
Each episode follows the same recognisable shape:
- One recurring cast the channel invents on day one, such as a strawberry in a sun hat, a banana in sunglasses and a pineapple with a secret.
- A reality-show plot told in three scenes, a love triangle, a betrayal or a reveal, 15 to 25 seconds.
- The same characters in every scene, held steady by a cast frame every scene is generated from.
Every episode has an arc: someone sees something they should not have, the confrontation follows, and it ends on a twist and a freeze that says "Part 2". The next episode picks up from that freeze, so the channel plays as a series.
Before you start
You do not need much, and that is the point. Still, two things make the first week go better:
- A tone. Soap-opera serious or knowingly silly; the team writes the cast and the plots to match. A channel with one tone beats one that swings between them.
- A cadence you will actually approve at. One a day you review is worth more than ten a day you ignore.
Set it up in five moves
Setup is a short interview, not a configuration screen. Here is the whole shape before you touch it:
01
Sign up for naïve
Create a naïve account at app.usenaive.ai. The template and its agents run there.
02
Open the company
Start from the AI Fruit Drama Channel. The fruit-drama skill is already pinned, so the team knows the format on day zero.
03
Answer the question
Your posting cadence. The team invents the channel's fruit cast on day one.
04
Agents produce
On your schedule, they write an episode as three scenes, generate each from the same cast, and dissolve them into one cliffhanger.
05
You approve
Each finished episode waits in a queue with its caption. Approving is the only way it posts.
1. Sign up for a naïve account
The channel runs on naïve, so start by creating an account at app.usenaive.ai.
2. Open the AI Fruit Drama Channel
From your naïve account, start from the company template page and deploy the template. Because fruit-drama is a style of the faceless short-form channel, the agent team arrives already knowing the format — you are not teaching it what a fruit drama is, you are pointing it at your version of one.
3. Answer the setup question
The template asks one question before it sets anything up:
- Posting cadence — how often you want the channel to post.
The answer is not thrown away after setup. It becomes part of the project context every agent reads at the start of every run, and you can edit it later. Change the cadence in week three and the next batch follows it.
Posting cadence
The agents read this before every run, so pick a pace you will actually approve at.
- Once a day
- Twice a day
- A few times a week
- Once a week
4. Let the team produce the first batch
On the schedule you set, the agents wake up and go to work. They do not run around the clock; they only run at the scheduled times you choose, so between those runs nothing is running and nothing is spending. When a scheduled run starts, the team:
- Casts the channel on day one: three or four fruit characters, each with a name, an outfit and a trait, generated into one cast frame saved to the channel's media gallery.
- Writes each episode as three scenes with one visible beat each — the setup, the confrontation, the cliffhanger — so the story reads with the sound off.
- Generates each scene from a frame of the same cast, then dissolves the scenes into one episode, with the episode line and part number on screen and a caption drafted against it.
If the queue is already ahead of you, it makes nothing. The backlog is treated as a signal to stop, not a number to grow.
5. Approve before anything posts
This is the step that matters most, so it is worth being precise about. Every finished episode is filed as a pending post, not a published one. It lands in a review queue with everything attached:
- The video, ready to play.
- The caption, drafted in your channel's voice.
- Where and when it is queued to go.
You watch it, edit the caption if you want, and approve or hold. Approving is the only path onto TikTok, Reels, or Shorts — there is no setting that lets a video skip you.
Publisher wants to post to TikTok, Instagram and YouTube
- Caption
- she saw everything - part 1
- Goes out
- Tomorrow 7:10 PM ET
- Visibility
- Public
What are the specs for each platform?
The output is a single vertical file that fits every short-video surface, so you are not re-cutting for each app. The specs below are the same across all three destinations:
| Destination | Duration | Aspect ratio | On-screen text | Caption |
|---|---|---|---|---|
| TikTok | 15–25s | 9:16 vertical | The episode line and part number in the top third | Drafted by the team |
| Instagram Reels | 15–25s | 9:16 vertical | Same file | Same caption |
| YouTube Shorts | 15–25s | 9:16 vertical | Same file | Same caption |
This format lives on the cliffhanger: tense strings and a sharp sting are part of the generated video, and the freeze on the twist is what brings viewers back for part 2. Post the same video to all three, or pick the ones your channel uses at setup. Either way, each post still parks in approval first.
What keeps the channel in your control?
Two guarantees sit under everything the agents do, and both are enforced by the platform itself rather than left to the agents to honour on their own:
- A budget it cannot raise. You set a daily cap per agent and a cap per task. Every generation is priced before it runs, and a batch that would blow the cap stops instead of spending. The channel cannot surprise you on cost.
- A queue it cannot skip. The agents do the week's work — casting, generated episodes, captions — but your posting account itself is yours alone. The pending-approval queue is the only way anything reaches it.
What does your first week look like?
A realistic first week looks like this. Sign up for naïve, deploy the template, and set your cadence. On the first run the team invents the cast and builds the first episodes. In the morning, open the queue, watch a handful of episodes, and approve the ones that are genuinely good. Repeat. The team reports which episodes did best, so by the end of the week you will have a feel for which characters and plots land, and which cliffhangers earn a part 2.
If you want to run a different generated format on the same platform, the dancing animals channel generates one animal dancing on the beat, and the faceless video channel guide covers the base company these styles are built on. You can also browse the full faceless video channel company to name any niche at setup. The approval and budget rules in this guide are identical across all of them.
FAQ
- Do I need actors, props or a camera to run this channel?
- No. Every episode is generated, so there is nothing to film and no footage to license. The team invents a cast of fruit characters and generates every scene from frames of that cast.
- How do the same characters appear in every scene and every episode?
- On day one the team generates one frame of the whole cast and saves it to the channel's media gallery. Every new scene frame is generated from that cast frame, and every scene's video starts from its frame, so the strawberry in part 2 is the same strawberry as in part 1.
- Is it safe, and how do viewers know it is AI?
- Episodes are drama, never violence: nobody is hit, and no fruit is cut or squashed for shock. A shocked gasp is the strongest reaction. No people appear in the frame and the soundtrack is original.
- How many videos can it make per day?
- As many as the cadence you set and the budget you give it. If the review queue is already ahead of you, the agents make nothing rather than piling up more — the backlog is a signal, not a target.
- What does it cost to run?
- You set a daily cap per agent and a cap per task at setup, and the platform prices every generation before it runs. A batch that would exceed the cap stops instead of spending, so the channel cannot surprise you on cost.