First light.

Day one was version 4.2.

The first commit landed on a Sunday night. Its message promised to scaffold “the full Allie pipeline, all 12 phases,” which is a lot to ask of a Sunday. Two days later the back office arrived already calling itself version 4.2.0. There was never a version 1. Optimism was the first thing I shipped.

The idea fit on a sticky note. You paste your website. An assistant named Allie learns your brand, plans your week, writes the posts, designs them and publishes them, and you approve what goes out. Building it did not fit on a sticky note.

Every post was a web page in disguise.

April was 558 commits, and every one of them felt like progress. Onboarding learned to lift a logo straight off a website. Stripe arrived. Image generation got a waterfall: when the best model stumbled, the next one caught the post. And every graphic Desklight made was secretly a web page, laid out in a hidden browser and then photographed.

It looked great in demos. It was also the thing I'd spend the next five months replacing.

The job description, in full.

Being a solo designer who codes means every design review is a meeting with yourself, and both of you are stubborn. The designer wants nine directions. The engineer wants one, tested. Let the designer win too often and the code pays for it. Let the engineer win and the product starts to look like a settings page.

Then there are the jobs nobody pictures when they picture a startup: a privacy policy, refund terms, cookie consent, a security review, and the app review every platform runs before it lets software post on your behalf. Each one wants screen recordings and a reason for every permission. None of them care that you also have a renderer to replace.

The busiest month had a cast.

July was 700 commits, the busiest stretch of the year, and by then I wasn't really working alone. I was directing a rotating cast of AI coding agents, mostly Claude, with Codex and a few others taking shifts. I write the brief, set the bar and review every change. They're fast, tireless and extremely literal.

Literal has consequences. One agent, tidying up, rewrote the project's history right over another agent's work. The rule that came out of it still sits in the project's instructions: nobody rewrites history. Not even to be neat.

July also produced my favourite commit message of the year, from the night the new editor first booted: “IT RUNS.” The same commit retired a Size control that had never resized anything. We'd taken to calling it the Size placebo. Later that month we found four separate pieces of code, each with its own opinion about which font your brand uses. They did not always agree. Now there's one.

August was quiet.

Twenty-seven commits, the whole month, all of them on three days. The most important one removed a middleman: every connection to your social accounts became our own, built directly against each platform instead of through a third party. Fewer moving parts, and one fewer company holding your keys.

The same day, publishing learned to wait for you. You choose what goes out. Publish reviewed posts yourself, or explicitly enable supported publishing automations. LinkedIn posts still need your confirmation.

Rules, not pictures.

September is when the web-page renderer from April finally went. In its place is a composition engine that treats a design as a set of rules instead of a picture. It lays a post out again for every size rather than cropping it. It keeps words off people's faces. In the modern designs it measures every line of text on a photo against the actual pixels behind it, and if a line can't reach 3:1 contrast, you hear why before anything is published. On September 30 the old renderer was deleted under a commit message that reads like an exhale: “One pipeline.”

September also brought a new identity (the ember D at the top of this page), a security review that closed holes around billing and access, and a pass through this website that removed every claim we couldn't back up. I'm prouder of that last one than of most features.

And on September 25 a routine cleanup command followed a shortcut it shouldn't have and deleted real source files. That one earned a permanent rule too: list the links before you delete anything.

Every guardrail in Desklight was paid for by something going wrong first. The rules don't read like wisdom. They read like dates.

What it became.

Hearth Bakery doesn't exist. I made it up for this note, and the baker and the shop are generated. Then I ran its morning post through Desklight's six modern designs: same photo, same words, each set in the bakery's own colours. The layouts and the refusal below are exactly what Desklight produced.

Five of them took it. The sixth, Portrait depth, turned it down. With this photo its headline couldn't reach 3:1 contrast in either tone, so instead of handing over a post you'd squint at, it said so and suggested another photo. I didn't stage that. It's September's check doing its job. Culture collage had already sent back my first headline, a longer one, because it wouldn't fit at a readable size. The one you see is the shorter one.

Portrait depth

Refused.

“In this design and the brand's colours, the headline would not read against what is behind it (28% of it reaches 3:1). Try the other tone, another photo, or another design.”

The light tone did worse, at 22%.

Open any of them and it comes apart into layers, grouped the way a designer would group them. Click once to select a group, double-click to go inside, and recolour everything that shares a colour in one move. It works like Figma because I kept asking for exactly that until it did.

One more thing.

I said the feature list was closed. The day after I wrote this, I shipped one more thing anyway: Insights. Until then, Desklight's story ended at Publish. It could take a post from a blank page to your feed, and then it went quiet about what happened next.

Insights reads supported account and post results live, marks the days you posted, and turns what your audience did into your next two moves. One click hands a move to Allie as her next brief. Availability follows each publishing connection’s approval. X results read live today, as far as X’s API plan allows; the other supported channels open as each platform’s review clears, and LinkedIn results aren’t supported yet. Each brand also gets a branded monthly report you can preview in Insights.

It reads the numbers live and keeps none of them. It tells you whose account they came from. And the footnote says what I'd want any tool to tell me: clicks are not sales.

I know. Scope. But this is the piece that turns posting into getting better at it.

Lights on.

Desklight opens to everyone on Tuesday, November 17, 2026. Between now and then: screen recordings for the platform reviewers, and fixing whatever writing this note made me notice.

If you run a business mostly on your own, the posting is the job that waits until everything else is done. Desklight is built to take it off your desk.

Questions.