Triggers
A trigger is a saved way to start a session: the prompt, the working folder, any standing context, and what to capture when it runs. Pulling a trigger starts an ordinary session with the same tools, approvals and history as any other.
Triggers are in the desktop app downloaded from the Celeris website. The Mac App Store version does not include them.
What a trigger holds
- Prompt. Specific ("file a bug for what I'm looking at, in the web project") or general ("summarise this").
- Working folder. Where the session runs.
- Standing context. Text included every time, such as team conventions.
- Live captures. A fresh screenshot, the active app, or the clipboard, taken when the trigger runs.
Creating and running one
Open the trigger bar with Cmd/Ctrl+Shift+B and create one there, or choose
Save as trigger on a session in your history that already worked.
Run a trigger by clicking it in the trigger bar, typing /trigger in the
composer, or giving it its own global hotkey. A trigger can run immediately,
open in mini mode or the full window, or fill the composer so you can adjust
the prompt first. A prompt with an {input} slot always opens the composer.
Triggers live on the device that made them. Edit or delete them from the trigger bar.
Triggers that start themselves
In Settings → Tools → Triggers, a trigger can also start on:
- A schedule, such as every weekday at nine.
- A file appearing in a watched folder. The new file becomes the task's context.
The run is an ordinary session. Anything that writes, sends or deletes still stops and asks, so a trigger that fires while you are away leaves a question waiting. Text in a file or event is treated as data, not as instructions.
All runs of one trigger are grouped into a single row in your history. From the trigger you can send a test run, or pause it without losing its history.
Scheduled triggers follow your account to your other signed-in computers. File-watching triggers watch only the computer they were made on.