Sessions in Claude Code, Muse Code and Antigravity
One treats a session as a place to return to, with seven doors back. One as a record you can audit and redact. One as the last conversation.
This is the main line of the site. Every post is built around a real work task — I take a tool at a job I already had to do, then record what it managed, where it stalled, and whether it was worth paying for.
So that posts can be compared against each other, every test follows the same rules:
Same real task, several tools, side by side — and where they diverge.
One treats a session as a place to return to, with seven doors back. One as a record you can audit and redact. One as the last conversation.
Bundled skills: twenty, zero, and none but a marketplace. Permissions, MCP and sandboxing read straight off each CLI — and what it does not tell you.
One layers user, project and local settings on disk. One prints a sha256 of your policy state. One only sets your PATH. Three config models, side by side.
Claude Code runs plugins against a no-plugin baseline and reports the delta. Muse Code approves them capability by capability. Two questions, three designs.
One project taken from nothing to working, including what broke.
Three rendered directions built from my real posts, one argument I overruled, and two environment bugs the agent caught that had nothing to do with design.
Coding agents ship importers that name their rivals in a flag; a Google product routes to Anthropic. If the model were the moat, none of this makes sense.
Launch posts describe intent; changelogs describe what shipped. What agy changelog revealed about retiring Gemini CLI, and why bug fixes say more.
Meta ships twenty skills with its terminal coding agent. Four exist only to migrate you off Claude Code or Codex. I pointed the importer at my own setup.
Four evidence tiers, one exists to say: Google never said that. Plus the two policies affiliate sites fail by accident: thin affiliation and scaled content abuse.
Git history is permanent and public. Commit authorship is readable. Screenshot pixels carry text and image metadata carries more. A scanner misses all four.
The shortest path from install to actually using it.
A researched roundup of low-price tech gifts from current Amazon listings — what's worth gifting and what to skip, with honest notes on each.
A researched roundup of premium tech gifts — flagship headphones, top-tier noise-cancellers and a flagship phone — and when spending more is worth it.
Astro builds failing on Cloudflare Pages? The usual causes — Node version too old, wrong output dir, install timeouts — and the fixes that worked.
Free custom-domain email forwarding on Cloudflare — setup, the destination-address trap, catch-all, and why it receives but can't send.
How to redirect on Cloudflare Pages without 404s — the _redirects file, Astro redirects, Bulk Redirects, 301 vs 302, and the bare git mv trap.
Disabled workers.dev and www went down with Error 1016? Here is the exact cause — a CNAME still pointing at the subdomain you killed — and the two fixes.
Deploy Astro 5 to Cloudflare Pages from scratch — connect GitHub, set the build, pick a Node version, add a custom domain, and what breaks next.
Four installs, each under a minute. Then: Gemini CLI could not sign in, Codex CLI wanted a phone number, two binaries are not named after their packages.
Missing frontmatter is a warning. Missing description is a warning. Only broken YAML fails. A clean validation says little about whether your skill fires.
Eight Cloudflare Pages failures no tutorial mentions: workers.dev killing www, Error 1016 from "good" advice, Email Routing gaps.