Field note 01 · August 10, 2026

From code suggestions
to delegated work.

This is the first website I’ve built end-to-end with Codex. The code matters, but the more interesting change is how the work moved beyond the editor.

01

What I knew before

I learned to build and revise my recent applications with Copilot directly inside VS Code. That workflow made software feel approachable: describe an idea, examine the proposed code, make an adjustment, run it and repeat.

It was still an editor-centred experience. My attention stayed close to the file, the component and the immediate change. That was valuable—it taught me how to collaborate with AI without pretending the machine understood every decision.

02

What changed with Codex

With this site, the centre of gravity shifted from the current file to the whole project. We started with an empty folder and a direction: replace an old blog with a bilingual business card about AI, the products I’ve shipped and the experiments still on my workbench.

Codex worked across the job: shaping the information, writing English and Québec French, building the interface, testing production output, connecting GitHub and Netlify, setting redirects, configuring forms, analytics and consent, and investigating live DNS and email problems.

The difference, for me, wasn’t simply “more code.” It was continuity. The conversation could carry an intention through design, implementation, verification and deployment.

03

Agentic does not mean unattended

The process also showed me where autonomy needs boundaries. I still chose the message, the tone, the public claims and the moments when an external change was appropriate. Codex could inspect evidence, propose a next move and carry it out within permission—but I remained responsible for the direction.

Delegating the work did not mean delegating judgment.

That distinction matters. A useful agent should move the project forward, show its evidence and stop when a human decision has real consequences.

04

Tasks, skills and background work

I’m now exploring a different way to think about software work. A task is a concrete outcome. A skill captures a repeatable way to reach it. Background work lets a longer objective keep moving while I focus elsewhere.

Those ideas feel bigger than programming. They apply to research, operations, content and the small pieces of coordination that usually sit between an idea and a finished product.

05

What I’m taking forward

Copilot helped me learn the edit-and-iterate rhythm inside VS Code. Codex is helping me learn how to frame work so an agent can carry more of the journey. These are not absolute limits of either product; they describe how my own practice evolved.

This site is a modest project, but it is a real marker for me: the first time the AI collaboration extended from an empty folder to a live, bilingual product—and then stayed with the operational details after launch.

Explore official Codex workflows