Well, well, well, it seems to be happening much quicker than originally thought. I’m about 70% done with this already! I still like Claude Code more, but Codex is more efficient at testing the UI in its browser than Claude Code. And the in-browser cursor, which is 100% independant than the Mac cursor, is super cool to see in action.

So far so good with OpenAI Codex. I prefer Claude Code’s look and feel, but Codex seems more like something Microsoft would build: plain, without soul. My data model is completed and implemented in AirTable. The basic web UI is running, but is lacking many basic operations like create, update, and delete for tasks, projects, etc. It took me less than two hours to deplete my token allotment. It’s a slower rate than with Claude Code… but still, it’s quickly gone.

Yesterday, I was criticized for adding an AI-powered feature to my Microblog frontend. It was suggested that, since AI can generate blog post titles, I might appear lazy. I explained that I’m not a native English speaker and sometimes need help with writing. Is that really wrong? For those using spell checkers and grammar checkers, are they lazy, too? At what point do the tools we choose to develop and utilize indicate our laziness?

iOS 27 to Let Users Generate Wallpapers and Build Shortcuts With AI — MacRumors

Bloomberg says the Shortcuts app has a prompt that says “What do you want your shortcut to do?” with a text field to enter a description. Shortcuts that are created using AI are then automatically installed and immediately available for use.

If true, I can’t wait to try it out! Shortcuts are out of reach for me. Too complicated, bad editing experience. With AI, this could flip the table and make them usable for me!

I made a small but useful improvement to my Micro.blog frontend: I added a Suggest Title option right to the title field. The prompt sent to Antropic’s cheapest model is:

Suggest a short, compelling blog post title for the following content. Reply with only the title, no quotes, no explanation.

This blog post was created to test the feature. Worked on the first try.

I struggle with my current AI usage because I frequently reach my token limit¹. I see two options: upgrade to a bigger plan² or use the limit as a signal to shift my approach—try something different or adopt a new strategy in real-time. A few years back, I didn’t rely on AI at all for my creative work. Now, with AI’s vast potential, I have found new creative possibilities that depend on it, so it’s hard not to upgrade or buy more.

Continuing my experiment with using my Craft Daily notes, I discovered and experimented with Claude Cowork Live Artifacts. These are interactive HTML-based dashboards that can be automatically updated on a schedule or on demand. This one is built using the Craft Daily notes data and presented inside Claude Cowork. I already have a big dashboard that I have created and hosted on Vercel, so it’s a different approach, a much more expensive approach because Claude Cowork consumes tokens after each update.

Since last year, I’ve been tracking my daily creative activities using Craft Daily Notes. Today, I tried out Claude AI and asked it to create a visual timeline for a specific day (yesterday in this case). Pretty interesting, isn’t it? Useful? I’m uncertain. I enjoy experimenting with digital tools and AI; it really elevates the experience. The challenge is to automate this and have a consistent format from day to day.

I experimented this weekend with the YouTube APIs to realize how much the platform limits the exposure of its features. It’s a shame and reflects what the internet has become nowadays: a collection of private gardens.

Above all that, the setup of the APIs in Google Cloud seems obscure and unintuitive to me. Luckily, I always have Claude AI nearby to help me.