Automations

Automations let Supen keep moving when the work is repeatable enough that you should not have to manually reissue the same prompt every time.

Good uses for automations

• follow-up on an ongoing thread of work
• recurring summaries or checks
• status reporting for long-running efforts
• scheduled tasks that have clear success and failure conditions

Start manually first

Do not automate a vague workflow. Start by running it manually until you know:

• which agent should own it
• what the prompt should say
• how often it should run
• what a useful result looks like

Once the manual version is stable, turn it into an automation.

Use the platform to manage automations

The platform is the best place to:

• create automations
• pause and resume them
• review recent runs
• edit prompts when they become noisy or stale

Keep automation prompts durable

Good automation prompts are:

• narrow enough to be repeatable
• clear about what the agent should do
• stable enough to survive small changes in surrounding context

If an automation needs constant babysitting, it probably should not be automated yet.

Use channels for visibility, not control

Channels are useful for surfacing the results of automated work. They are less useful as the main place to configure the automation itself.

Build the automation in Supen first, then let channels carry the output where it needs to be seen.