[bug] Playground config does not refresh after creating a schedule

[junaway]

After an agent calls create_schedule, the config section in the playground does not show the newly added trigger until the page is refreshed.

The expected behavior is for the config section to update immediately after the schedule is created.

[linear-code]

AGE-4071

[dosubot]

This looks like a cache invalidation issue. The playground config section relies on SWR cache for the trigger list, and after create_schedule completes, that cache isn't being properly invalidated — so the new trigger only appears after a full page refresh.

For context, PR #5259 previously addressed a similar problem by dismissing the schedule/subscription drawers after creation and refreshing the trigger list via mutation cache invalidation. The current bug suggests the refresh path isn't being triggered when create_schedule is called as an agent tool (as opposed to through the drawer UI).

The root cause is likely that the agent tool execution path for create_schedule doesn't call the same SWR mutate() that the drawer-based creation flow does. Compare with commit_revision, which solves this by having the backend emit a data-committed-revision SSE event that the playground handles via switchEntity() [1]. No equivalent SSE event exists for schedule creation.

A fix could either:

1. Add an SSE event (similar to data-committed-revision) that the playground listens for after a schedule is created via an agent tool, triggering a trigger-list revalidation.
2. Have the frontend detect create_schedule tool calls in the stream and explicitly invalidate the trigger list SWR cache on completion — similar to how the testset drawer calls mutate() after creation.

Also worth noting: issue #5529 reports a related problem with scheduled trigger updates failing in the agent playground, which may share the same underlying cause.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.