I stopped postponing my public profile

I had been putting off building a public profile. The site itself was never the hard part. Choosing a stack, making it look right, configuring a server, wiring DNS, adding comments, and maintaining another project was enough friction to keep it on the list.

DHH, of Rails and Omarchy fame, calls the new agent era endless execution: ideas and experiments become immediately reachable. I wanted to test that on something I had failed to start.

I asked Codex for the simplest self-hosted blog stack. It presented the tradeoffs. I chose Astro with Markdown and Remark42 for comments. I also chose the domain, the visual reference, anonymous comments with spam controls, and a private GitHub repository.

Then I gave Codex access to the tools it needed and stayed in the chat.

Prerequisites

The starting point was small:

• a domain available through hcloud (Hetzner Cloud) with an API key that could update DNS
• a server reachable over SSH
• an existing reverse proxy on that server
• a GitHub account for the private repository and comment login

I also pointed Codex at a local project whose style I liked and supplied an exported chat as source material for the first post.

How it unfolded

Codex inspected the reference project and server, created the Astro site, matched the visual language, wrote the first article, created the repository, configured DNS, connected the existing reverse proxy, and deployed the static build.

When I asked for anonymous comments, it added Remark42 with rate limiting and a honeypot. When I wanted GitHub login too, it guided the OAuth setup and filled in the configuration. I only had to sign in and make the security sensitive clicks.

The process was not perfect or fully autonomous. My input carried the intent, taste, access, and final judgment. Codex handled the implementation and the glue between the filesystem, GitHub, DNS, and server.

What I have now

I did not just get a blog. I got a repeatable, agent driven publishing pipeline:

problem solved or discovery made
→ notes, transcript, or chat
→ concise Markdown article
→ build, commit, deploy, verify

It is not unattended automation. It is a collaboration loop. Whenever I solve a problem, build something fun, or find something worth sharing, I can give Codex the raw material and review the result at the level I care about.

That is what changed. The ideas were always there. The cost of executing them collapsed.