All Articles
Connected, but the Body Stops Halfway. Measuring Header-Only, Total, and Idle Timeouts on the Same Response
You added a timeout to fetch, yet the loading indicator never goes away. I reproduced a response whose body stalls halfway on a local server and measured header-only, total, and idle timeouts under identical conditions. Runnable test code included.
Remembering What the AI Decided: Four Marks in the Cache Key Paid Off on Model-Swap Day
A small on-device cache for AI answers, with the model name and prompt version in the key so old answers vanish on swap day. TypeScript plus simulated results.
Sending temperature to the Claude API Now Returns a 400 on the New Version. Finding Every Spot in Your App
Claude API version 2026-10-21 returns a 400 if you send temperature, top_p or top_k. When it hits you, a script to scan your app and SDK setup, and the order to fix things in.
Is Your Rork App Still Calling Sonnet 4.5? Finding Out Before November 30
Claude Sonnet 4.5 is scheduled to retire from the API on November 30, 2026. A small script to find leftover model IDs in your app, and the order to fix them in depending on where they live.
Rork's Design Mode or Plan Mode? Sort It by What You Are Unsure About: the Look or the Scope
How to choose between Build, Plan, and Design in Rork by what you are unsure about. Three questions, three examples, what the free plan can settle, and how to write a first message.
When Rork's Fix Breaks the Screen Next Door: Choosing Between Undo, Revert, and Edit Message
When an AI fix in Rork backfires, three questions tell you whether to Undo, Revert, or Edit message. Going back costs no credits; here is what it cannot bring back, and how to ask again.
Before You Type "Connect Supabase": The Two Values to Copy, and the One You Must Not
Rork asks for just two things before you type Connect Supabase in chat: a Publishable key and your project link. Here is where to copy them from, how to avoid pasting the secret key that sits on the same screen, and a small script that checks the values locally first.
Before You Ship an AI-Made App Icon or Image: A Ledger and Four Checks
Can you ship an AI-generated icon or illustration as is? Before deciding, run four checks: a provenance ledger, the tool's terms, resemblance to existing work, and store size rules, with a working script.
Three checks to run before you ask the AI again about a black preview screen
When a fresh Rork preview opens to a black screen, split the problem into three layers — device, rendering, native — before sending the same fix request again.
Take the Prompt Out of the App: An Edge Function Gateway With the Guard on the Output Side
A system prompt shipped inside your app is readable from the day it ships. This walkthrough moves the prompt into a Supabase Edge Function, lets the client name only a task, and puts the guard on an output allowlist, with tested code.
Sonnet 5.5, GPT-6.1 Sol, or Opus 5.5? I Decide by the Kind of Fix Before I Pick the Model. A Week of Logging Where My Rork Credits Went
After Rork's model menu settled into Sonnet 5.5, GPT-6.1 Sol, and Opus 5.5, I sorted my fixes into three kinds and assigned a model and effort level to each. Here is how I read the changelog, the tiny ledger that tracks where each credit goes, and the rule I drew from a week of entries.
Keep Fixing in the Same Thread, or Restore and Rephrase? What I Learned Fixing One Rork Bug Both Ways
When a Rork fix request fails for the third time, do you keep going or use Restore and ask differently? I fixed the same bug both ways and compared round trips, leftover code, and where I now draw the line.