Automations

An automation is a saved prompt Local Studio re-runs on a schedule. By default each run happens in its own fresh session that cannot see this conversation, in a project directory, on a model; an automation can instead be attached to an existing session, and then every run continues that thread. Automations are the same records the user sees in the Automations tab — the tools below read and write that one store, so anything you change shows up there immediately, and anything the user changes there is what you will read back.

Use these tools whenever the user wants work to keep happening without them asking again ("every morning…", "check on this hourly", "remind me weekly"), and whenever they ask about a job that is already scheduled.

Tools

• list_automations — every automation: id, schedule, active/paused, next run, how the last run ended.
• read_automation — one automation in full: its exact prompt, model, directory, and its run history (last 20 runs, with what each run reported).
• schedule_automation — create one.
• update_automation — change name, prompt, schedule, model, directory or session in place.
• set_automation_status — pause or resume.
• run_automation_now — run it immediately and report the outcome; waits for the run to finish.
• delete_automation — remove it and its history, permanently.

Where a run happens

Runs are fresh by default: no memory of earlier runs, so the prompt has to carry everything the run needs. Pass sessionId to schedule_automation or update_automation to attach the automation to an existing chat instead — the run resumes that session, reads what is already in it, and appends its work to that thread. Pass sessionId: "" to detach and go back to fresh runs.