Planner + controlled automation Feature preview

Plan the work once. Let the Auto Worker process the reviewed queue.

Connect characters, image targets, local asset sets, publishing channels, and scheduled dates in one production calendar. The Auto Worker can then process eligible tasks while keeping review states, logs, and failures visible.

Request beta access Explore all features

✓Local planning data
✓Reviewed queue items only
✓Visible worker status
✓Connected services are optional

Production calendar Worker idle

Mara Venn — Reddit release12/12Ready for review

Ilya North — Patreon early access8/8Approved

Sana Mire — Bluesky preview5/6Waiting for images

Avery Rune — X image set10/10Scheduled

Fictional planner data · shown for illustration.

Interactive preview

Inspect the board, then simulate the worker.

Filter by platform or state, open an item to see the worker decision, approve it, place it in the queue, and start or pause the worker. Demo only — no data is sent and no post is published.

Demo only — no data is sent and no post is published.

How it works

Five connected steps from plan to verified result.

1PlanChoose the project, fictional character, target platform, date, and required asset count.
2Attach assetsConnect a reviewed image set from Selection or wait until the required local assets are available.
3ReviewConfirm captions, prompts, labels, tier information, community context, and the intended destination.
4QueueOnly approved and eligible entries can enter the Auto Worker queue.
5Execute & verifyThe worker starts the configured handoff, waits for the action to finish, records the result, and keeps failed tasks visible for review.

Division of responsibility

The Planner decides. The Auto Worker performs.

Planner

•Defines dates and priorities
•Connects characters and asset sets
•Stores target platforms
•Tracks readiness
•Requires explicit approval
•Provides production context

Auto Worker

•Reads approved queue items
•Checks required assets
•Checks configured sessions
•Starts supported workflows
•Waits for completion
•Records status and errors
•Stops or pauses when user intervention is required

The Planner decides what is eligible. The Auto Worker performs only the configured and approved next step.

Worker decision panel

Every decision is explicit and inspectable.

The worker must not silently skip missing authentication, required assets, failed browser sessions, or review requirements. When a check fails, the task pauses and reports what it is waiting for.

worker.decisionWAITING

Task: Mara Venn — Reddit release

Planned time reachedYes

Required assets available12 of 12

Selection reviewedYes

Community selectedYes

Browser session availableNo

Final resultWaiting for login

Workflow destinations

What is available, in development, and planned.

Available

Workflow foundations

✓Local Planner records
✓Character association
✓Selected asset sets
✓Local queue state
✓Worker logs

In development

Connected workflows

◐Reddit handoff
◐Patreon tier and release context
◐X publishing queue
◐Bluesky publishing queue
◐Browser-session checks

Planned

Longer-term direction

○Cross-channel conflict detection
○Smarter scheduling recommendations
○Worker retry policies
○Quality-aware asset selection
○Learned prompt and image-quality signals

Safety & control

Automation does not remove your final control.

✓The worker processes only approved tasks.

✓Missing authentication pauses the related task.

✓Failed actions remain visible.

✓The worker should not endlessly retry external actions.

✓You can pause the queue at any time.

✓Logs explain what the worker checked and why it continued or stopped.

✓No platform receives content until its configured action is started.

✓Platform rules and final publishing responsibility remain with you.

Local-first architecture

Planning stays local. Connections run only when required.

Planner entries, fictional character references, local file paths, queue states, and worker logs remain in the local Setvyn workspace. Reddit, Patreon, X, Bluesky, ComfyUI, browser sessions, or optional model providers are contacted only when you configure and start the related workflow.

Stays local

Planner entries, character references, file paths, queue states, and logs.

Only when started

External platforms and model providers, for the configured action only.

Local-first does not mean every connected workflow works fully offline.

Preview roadmap

Where the Planner is heading.

Now

✓Local planner records
✓Character and asset context
✓Queue states
✓Worker logging
✓Manual approval

◐Stronger session validation
◐Controlled worker retries
◐Clearer failure recovery
◐Platform-specific readiness checks

Later

○Scheduling recommendations
○Quality-aware automatic asset suggestions
○Training data for prompt and image evaluation
○Conflict detection across platforms

FAQ

Planner & Auto Worker FAQ

What happens when the browser session is not logged in?

The task pauses and reports that user action is required. It must not continue with an unauthenticated session.

Can the worker publish without approval?

The intended workflow requires an approved and eligible planner entry before it enters the worker queue.

What happens when images are missing?

The planner keeps the task in a waiting state until the configured asset requirement is satisfied.

Does the worker close the browser immediately?

No. A connected workflow may need to remain open until the scheduled action has completed and its result has been recorded.

Is everything stored locally?

Planner state, asset references, queue status, and logs remain local. Configured external services receive only the data required for the action you start.

Is the feature finished?

No. This page describes the active foundation and the intended direction of the Planner and Auto Worker. Individual connections may still be under development.

Feature preview

Build a production queue you can understand and control.

Setvyn is developing the Planner and Auto Worker as a visible, reviewable layer between local production and connected publishing workflows.

Request beta access Compare editions