Using Publit.Si
Automation: daily Shorts
An automation lets your agent (Claude, Codex, Cursor or OpenCode) make new Shorts on its own at a fixed time. Each run starts fresh with a short recipe from one of your chats and hands the Shorts to Queue › Review.
You need
- A project folder in the Studio
- A Studio chat in which your agent already made Shorts
- Posting slots for the accounts (see Slots and goals)
Create an automation
Open Studio › Automation → New automation. Or, in a chat that made Shorts, open ⋯ → Repeat daily as automation….
Under Recipe from chat, pick that chat. Its agent reads it and fills in the recipe, Name and Topic. This can take a few minutes.
Set the Time, the Days and the Shorts per run (up to 10).
Check What will happen in the Preview tab. Edit lets you change the recipe yourself: render command, steps, assets, style.
If the form lists commands under “These commands are needed”, click Allow: nobody can confirm them during the run. Then save.
Pick the agent
Agent picks Claude Code, Codex, Cursor or OpenCode. A recipe from a Codex, Cursor or OpenCode chat uses that agent by default. Advanced holds the Model and effort.
Only Claude Code has a cost cap: Max. cost per run ($) under Advanced, $3 by default. Claude stops when it is spent. Codex, Cursor and OpenCode run on your plan and stop after the run's Shorts. Codex makes assets lets the agent order images and other assets from Codex before rendering.
Active switches an automation on or off without deleting it.
When it runs
An automation runs once a day at its time, on the chosen days. The card shows Next run. Publit.Si's background service (the worker) must be running: without it no automation starts, not even Run now.
A computer that slept through the time still runs it up to six hours later. After that, the day shows as Missed.
| Button | What it does |
|---|---|
| Run now | Starts a run within a minute, outside the schedule. The request expires after six hours. |
| Stop | Ends a running run. The agent stops within a few seconds. |
| Open run | Opens the run as a chat in the Studio, so you can read what happened. |
| Edit / Delete | Change the automation, or remove it. Shorts already made stay in the backlog. |
Review the Shorts
Each Short is checked against every account (length, orientation, size) and lands as a draft on a free posting slot under Queue › Review. Approve it there.
Reject… removes a Short and takes an optional reason, e.g. “hook too slow”. Later runs avoid that kind of Short.
Latest runs lists each run with its status (Done, Partly done, Failed, Stopped, Missed), the Shorts delivered and, for Claude, the cost of the last 30 days.
When the agent is signed out
Before each run, Publit.Si checks that the agent is installed and signed in. If not, the run doesn't start and the card says what to do.
Sign in once in a terminal, then click Run now. Or pick another agent in the automation.
claude /login # Claude Code
codex login # Codex
cursor-agent login # CursorCheck
After a run, the card shows Done with the number of Shorts, and the drafts wait under Queue › Review.
Troubleshooting
- Daily Shorts run fails: the agent is not installed or signed out
- Sign in in a terminal (
claude /login,codex loginorcursor-agent login), then click Run now, or pick another agent in the automation. - The agent changes files in my app's repository
- Link the project to a separate marketing folder instead: Studio → Change project folder → Create a marketing folder.
Stuck? Search the troubleshooting list or write to us . Leave out secrets and tokens.