Category Archives: AI

Claude Code “Prompt Cache Has Likely Expired” (What It Means)

Claude Code VS Code panel showing Idle 1h 49m, the prompt cache has likely expired, re-cache about 586k tokens, with a red cache clock in the footer

Summary: Claude Code’s “prompt cache has likely expired” notice means your session sat idle longer than the prompt cache lasts. As of Sep 2026, by default, that’s 1 hour on Pro or Max while you’re within your included usage, and 5 minutes if you’re using an API key, a cloud provider, or usage credits. Your conversation is still there, but your next message will likely re-process all of it once. That turn can be slower and cost you a LOT

Open WebUI Web Search Not Working? It’s Off By Default (and how to fix it!)

Summary: Open WebUI ships web search off, and there are two separate ways to turn it on. For one chat: click the four-diamond Integrations icon right of the + and flip Web Search on. For every chat: Settings > Interface > Web Search in Chat, set it to Always, then Save.(not Admin Settings, which is where I looked first) Verified on Open WebUI 0.11.0, August 21 2026. Option 1: Turn It On For One Chat Here’s the whole message box.

Claude Code or VS Code Still Showing Opus 4.8? How to Switch to Opus 5

Anthropic shipped Claude Opus 5 on July 24, 2026. It is the new default model on Claude Max and the strongest model you can pick on Claude Pro. So why does the model picker in your VS Code panel still say Opus 4.8?! Before you go digging through your account or your plan, check the version. Opus 5 requires Claude Code v2.1.219 or later, and the list of models in that picker is compiled into the build you have installed.

RTX 5090 R vs a cheap 4060 for render fleet usage

Bar chart comparing WanGP image to video render time per clip on RTX 5090 versus RTX 4060. Light clip 42 seconds versus 205 seconds, heavy clip 101 seconds versus 703 seconds.

Summary: I generate image-to-video (i2v) clips for a software project on a small consumer level GPU fleet: a flagship RTX 5090 and a cheap, always on RTX 4060. On a controlled raw render test the 5090 is about 5x faster per clip. But in a real overnight run where the two cards carried very different loads, their completion rates were only about 1.6x apart, and the 4060 finished a 74-clip batch in a reasonable 4.6 hours. Also, at the end

How to Set Up a SSH Connection in Claude Code Desktop

Summary: Claude Code’s desktop app can SSH into a remote machine and run sessions there against your repo, MCP servers, and ~/.claude config. Setup is a four-field dialog, assuming ssh user@host (where user is your username and host is the hostname or IP) already works from your terminal. The non-obvious caveat: session history is siloed. The desktop app, the CLI on the remote, and the VS Code extension (if you use it) on the remote each keep separate session lists.

Codex CLI feature protip /statusline

TL;DR: There are a few ways to check your ChatGPT Codex usage, including: the web analytics page (covered in yesterday’s post) and the Codex CLI’s own status line, which can put live 5-hour and weekly percentages right at the bottom of your terminal session. The CLI method is easy to miss if you don’t have it enabled, thankfully it is super easy and configurable with the slash command /statusline. Codex CLI’s /statusline menu. Toggle the items you want, then press

How to Check Codex Usage in ChatGPT (Plus, Pro and Credits)

Summary: ChatGPT’s Codex has its own usage analytics page at https://chatgpt.com/codex/cloud/settings/analytics, separate from the main ChatGPT settings. You need to be logged into your ChatGPT account first. The page splits your Codex usage into three meters: a 5-hour rolling limit, a weekly limit, and pay-as-you-go credits. Here is an example screenshot: Important update (September 5, 2026) GPT-6 Astra landed in Codex on September 3 and it is hungry. OpenAI’s rate card gives Plus roughly 5 to 45 Astra messages per

Codex /goal feature (TESTED)

Summary: Codex’s new /goal mode lets you hand it a long-running task and walk away. From there it loops plan → act → test → review until your stop condition is met, or your weekly quota taps out. Currently it takes a two-line config edit to enable, then prefix your prompt with /goal. This is very much in line with what the reddit crowd does with a lot of their homebrew scripts and it opens some fun possibilities! Worth turning

« Older Entries