CodexWorkWorks & notes
What could you
make next?
A small book. A workshop. A decision people can act on. Open something finished, borrow a direction, or read for the pleasure of a good idea.
A weekend. A small book. A lovely thing to keep.
Turn what you know into something you can teach.
Make your case, not just a slide deck.
Make something that feels like yours
A small book, a workshop, a print or a subject you want to understand. Open the work before deciding what to try.
A weekend, small enough to keep
Turn scattered notes and small memories into an illustrated book. Open six finished pages, a shorter gift edition, and the originals to make your own.
A workshop from what you know
An hour, a phone and three things worth noticing. A complete photo walk becomes a rainy-day workshop, with editable host guides and activity cards.
The Last Print
A small print shop, one message worth keeping, and the white space around it. Make a print, take its editable original, or change it with your Agent.
The question you can answer tomorrow
A small learning notebook for the gap between recognising an explanation and being able to give one. Try the Moon lesson, then bring your own notes.
After the Beautiful First Draft
What matters after generation: choosing a medium, preserving an intentional edit, and judging the whole result.
A route is more useful than directions
One public Agent-made map shows why the visible result, the data you can take away and the record of how it was made are three different things.
Make a better-informed decision
Follow the evidence into a presentation, a buying choice or the rows that need attention.
Four files. One decision to make.
An editable six-slide presentation, a cost change, and the source review that made the final companion usable.
Why the buyer chose a plan that costs SGD80 more
Four quotes, one explicit tradeoff—and a changed quote that makes the original decision impossible.
Seven Rows to Inspect: Reading a Spreadsheet Run by Its Exceptions
In one recorded synthetic trial, the exception log showed what followed a rule and what still needed an answer. That distinction matters more than a tidy file.
Keep a project moving
Carry the useful work forward when dates, permissions or people change.
What Friday’s handoff must keep for Monday
A ready file, a requested delivery and partial cover each mean something different. A fictional equipment desk shows what must survive a changed week.
When the schedule is full and the need isn’t covered
Capacity drops and a safety request arrives. A fictional desk shows why a replan must keep the requests it cannot schedule.
The Brief That Outlasts the Chat
An ongoing agent needs more than memory. Its brief becomes something you can shape as the project—and your judgment—changes.
Make recurring work easier
See when a saved brief is enough, and when a small local workflow earns its place.
Pick up where the work changed
A saved responsibility, two real checks, and a reason not to run the same job again.
Let the model read. Let the code count.
Two recorded runs on fictional feedback, a local workflow you can inspect, and reports that lead back to every item.
Handing Over a Weekly Watch: What an Agent Needs Before It Can Own a Responsibility
A recurring job fails at the handoffs: where it reads, where it remembers, where it delivers. Here is a complete template, built around a fictional three-page watch.
Understand what is changing
Read about the move from a chat answer to files, shared surfaces and continuing work.
The Work Left the Chat Window: What to Specify When an Agent Touches Files, Tools and Time
Between July and October, the product pitch moved from better answers to ongoing work. The skill that matters now is specifying input access, durable state, approval and delivery.
Stop Describing the Change. Start Pointing at It.
AI agents are growing places to work: live tables, file panels, shared pages and small hosted tools. Here is how those surfaces differ.