Set It Once, Run It Daily: A World Cup Results Page on Autopilot

Every example so far has been a one-off task: write a prompt, hit run, watch it finish once. Routines are the other half of CTRL NODE — the same agent, the same instructions, firing automatically on a schedule instead of waiting for you to click a button. This time we'll also switch providers: instead of Claude, we'll build the whole thing with GitHub Copilot.

The goal: a single HTML page that shows the latest World Cup results and group standings, regenerated every morning at 9am, with zero manual steps after setup.

1. Project and agent

Same starting point as always — a new project, this time with Copilot as the agent type instead of Claude, pointed at a working folder (mundial in this example).

Register one agent inside that project — call it whatever makes sense (agente mundial here) — and pick the model. We used Sonnet 4.6 for this one; Copilot supports the same model selection as every other provider. Wait a few seconds for the agent to come online, and it's ready.

2. Create the Routine

A Routine needs a name, a description, and instructions — the same shape as a task, just meant to run repeatedly instead of once:

Create or update a page in the working folder called mundial. Build it as
a single HTML file with inline styles. Modern, dark theme.

Top row: results from the last three days.
Below that: group tables for each country.

Fetch the data for real and hardcode it directly into the page.

This is the part that matters for a Routine that's supposed to update the same file every day instead of creating a new one each time: pick Work Directory mode, pointed at the folder where the page already lives. Every run overwrites the same mundial.html in place — there's no accumulation of dated output files to clean up later.

3. Set the schedule

Pick when it runs. We used the daily preset, 9am:

That's the whole Routine defined. From here it would just wait until tomorrow morning and fire on its own — but you don't have to wait to see it work.

4. Run it once, manually

Every Routine has a manual trigger, so you can confirm it behaves correctly before trusting it to run unattended. Hit it, and the underlying task starts immediately — same Agent Activity stream you'd see from any task, because a Routine is a task under the hood, generated fresh on each firing.

Worth knowing: every Routine is actually a single-node workflow with a trigger node attached. If you open the workflow view, you'll see that node executing, and a run history listing every past execution — same infrastructure as multi-step workflows, just simplified down to one step.

5. Check the result

Once the agent finishes, the task's Result panel summarizes what changed, and Files shows the actual output. Since the workspace is Work Directory mode, this is a live remote view of the real folder on the machine running Bridge — not a copy.

From the file browser you can download the whole thing as a ZIP, open the HTML directly, or view it fullscreen right in the browser — results table populated with real match data, standings current as of that run.

6. What happens next

Nothing — and that's the point. Tomorrow at 9am the same Routine fires again, rewrites the same file with whatever's changed, and the page you're looking at is always current without you opening the dashboard. Set it once; it runs until you pause it.

The provider doesn't matter to any of this — swap Copilot for Claude, Gemini, or any other supported agent, and the Routine behaves identically. What makes it useful is the schedule plus Work Directory mode: the same file, updated in place, on a clock you don't have to remember.