How a scheduled job finds its workspace
Open WebUI released version 0.13.3 on November 8 with support for coding agents in its automation editor. The project says an operator can choose where the job runs by saving a terminal and directory, then picking an agent available in that environment. A recurring job can therefore open the same workspace each time without someone starting a new interactive session.
The release notes say Open WebUI checks whether it can still use the terminal and agent before running a job. Removing the terminal or changing what agents it exposes can interrupt a schedule even when the schedule itself still exists. Agent jobs deliver results into a chat. The project says channel destinations are still available for automations that use ordinary models.
What operators can check before relying on it
A practical first run would point the agent at a dedicated working directory and ask for a read-only report, then check the resulting chat before entrusting the schedule with writes. The directory sets the starting location, so teams should review what the underlying agent and terminal can access before assigning an unattended job.
The release announcement gives no separate fee for the scheduling feature and lists no country restrictions. A self-hosted installation still needs a compatible terminal and agent. CGH reviewed the release and implementation changes and did not run a job.