{"posts":[{"id":16,"slug":"claude-code-in-the-desktop-app","title":"claude code in the desktop app","kind":"post","body_md":"i've been running claude code entirely in the claude desktop app all day today, and not standard warp.dev setup i've been usually using.\n\npinning works. groups work. forking works. the side conversation thing for quick btws is useful. and the build in browser - this saved me from so many claude group tabs on chrome!\n\none thing i couldn't do was the `!` terminal commands where it watches output and adapts. but honestly that's been fine — it forced me to review and plan the next step more carefully before handing it back. probably ended up with better code.\n\nso far so good.  lets see if i'll go back.","tags":"","url":null,"date_label":null,"published":1,"created_at":"2026-07-20 10:23:45","updated_at":"2026-07-20 10:23:45","publish_at":null},{"id":10,"slug":"the-unseen-stack","title":"the unseen stack","kind":"post","body_md":"most of what makes software actually work is invisible — the jobs, the caches, the little tools i build for myself, the infra and experiments that never make it into a demo.\n\nthis is where i show that layer. i can be free about it here because none of it is anyone's but mine — no client, no employer, just what i run.\n\nit's built in public and mostly built with ai. expect teardowns, benchmarks, half-finished ideas, and small live tools you can actually hit. no time for real blogs, so it's just notes.","tags":"","url":null,"date_label":null,"published":1,"created_at":"2026-07-19","updated_at":"2026-07-19 07:15:26","publish_at":null}]}