<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>sigh.dev - #ai</title><description>Scott Cooper on TypeScript, React, open source, San Francisco, and the web. - Posts tagged with &quot;ai&quot;</description><link>https://sigh.dev/</link><item><title>Meta’s Muse is fantastic for web scraping</title><link>https://sigh.dev/posts/metas-muse-is-fantastic-for-web-scraping/</link><guid isPermaLink="true">https://sigh.dev/posts/metas-muse-is-fantastic-for-web-scraping/</guid><description>All-you-can-scrape for $80 a month.</description><pubDate>Thu, 01 Oct 2026 07:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I haven’t found much use for the personal assistant part of Muse. People on X (Twitter) keep using these assistants to order DoorDash or something. I order DoorDash like five times a year, so that’s not going to speed anything up for me. I also don’t get many emails, and managing my appointments is easy enough already.&lt;/p&gt;
&lt;p&gt;What I do need is a bunch of data from Reddit and YouTube and a boatload of cheap AI tokens. That’s where Muse comes in handy. I’m building &lt;a href=&quot;https://fullsets.fm&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;fullsets.fm&lt;/a&gt;, a side project that aggregates professionally recorded concerts (festival livestreams, Tiny Desk, etc.), organizes them by artist, and extracts tracklists. I’m looking for complete performances with good audio and video.&lt;/p&gt;
&lt;p&gt;I’ve got a pipeline that uses Luna and Gemini 3.8 via Gemini Studio to cheaply determine whether a YouTube video has the quality and content I’m looking for. What I don’t have is a good way to find the videos in the first place. I can scan a single YouTube channel for qualifying videos, but I need a way to find all the weird little channels, like T-Mobile Europe, that have for some reason uploaded a few random concerts. There are high-quality concerts scattered across all these little channels, and that’s part of why I built fullsets.fm (a work in progress).&lt;/p&gt;
&lt;p&gt;Muse helps me find those channels and videos. I’ve also got it at the other end of the pipeline, helping with artist matching, reviewing what Luna and Gemini output, and making a final decision to approve or reject each video.&lt;/p&gt;
&lt;p&gt;I can tell Muse to scan Reddit and YouTube for 1,000 videos matching my criteria, or build a list of artists who have ever played at Coachella and then go through them one artist at a time, searching YouTube for matching concerts. It sits there and spins until it’s done, punishing those websites with a machine in the cloud that has seemingly endless bandwidth and a decent CPU.&lt;/p&gt;
&lt;p&gt;I paid $80 for a month of Muse, and I’ve had it use a few billion tokens a week on this work. A lot of the time, it also seems not to count token usage at all. Their model (Muse Spark 1.3) is pretty mediocre at writing, and I would never use it to code, but I’m finding it really useful for this Gemini Flash-style workload. They seem happy to give me effectively unlimited tokens and a managed VM with Chrome.&lt;/p&gt;
&lt;p&gt;I worry about what will happen when someone points Muse at my own websites. These agents don’t sleep, and they can pretend to be real users extremely well. If it’s not fast enough, you can spin up more processes.&lt;/p&gt;
&lt;p&gt;Anyway, I see why &lt;a href=&quot;https://www.theverge.com/tech/998078/amazon-blocks-meta-muse-ai-agent-shopping&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Amazon blocked it already&lt;/a&gt;. Let’s say my goal was dropshipping or something. Could I scrape thousands of Amazon pages all day long? I don’t know where this leads, but we’ll likely see more websites block Muse unless Meta prevents abuse. There are still some early rough areas of Muse, jobs will freeze in the middle, communication with this somewhat shitty model can sometimes be frustrating and I’m not sure the UI makes much sense when running multiple jobs that are using the browser.&lt;/p&gt;
&lt;p&gt;If this post makes you want to try it out, my &lt;a href=&quot;https://muse.ai/join&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Muse&lt;/a&gt; referral code is &lt;code&gt;69WSDQ&lt;/code&gt;. Enter it in Settings within 48 hours of signing up and we both get a billion tokens.&lt;/p&gt;
&lt;figure data-breakout=&quot;wide&quot;&gt;&lt;a class=&quot;content-image-link&quot; href=&quot;./concert-refinement.png&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;img alt=&quot;A retro computer classifying concert recordings in an empty office&quot; title=&quot;Click to open in new tab&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1774&quot; height=&quot;887&quot; src=&quot;/_astro/concert-refinement.BHKU3j9T_ZE6FmC.webp&quot; srcset=&quot;/_astro/concert-refinement.BHKU3j9T_9dUYm.webp 640w, /_astro/concert-refinement.BHKU3j9T_2w0Wh3.webp 750w, /_astro/concert-refinement.BHKU3j9T_b94WY.webp 828w, /_astro/concert-refinement.BHKU3j9T_Z2i2eEN.webp 1080w, /_astro/concert-refinement.BHKU3j9T_2moAbb.webp 1280w, /_astro/concert-refinement.BHKU3j9T_Z2pvlA6.webp 1668w, /_astro/concert-refinement.BHKU3j9T_ZE6FmC.webp 1774w&quot; /&gt;&lt;/a&gt;&lt;figcaption class=&quot;image-subtext&quot;&gt;AI-generated image inspired by Severance&lt;/figcaption&gt;&lt;/figure&gt;</content:encoded><category>ai</category><category>web-scraping</category><category>fullsets</category></item><item><title>Making React Testing Library Tests 43% Faster</title><link>https://sigh.dev/posts/making-react-testing-library-faster/</link><guid isPermaLink="true">https://sigh.dev/posts/making-react-testing-library-faster/</guid><description>Three fixes made one React test file 43% faster without changing the tests.</description><pubDate>Thu, 20 Aug 2026 07:00:00 GMT</pubDate><content:encoded>&lt;p&gt;React Testing Library’s &lt;code&gt;getByRole&lt;/code&gt; is the correct way to test a form. It checks that fields have the roles and accessible names a user relies on, so a passing test tells me the form is at least minimally accessible and labeled correctly. That takes more work than &lt;code&gt;querySelector&lt;/code&gt;: it has to find candidates, work out their implicit roles, filter inaccessible elements, and calculate accessible names. On a large DOM, that can be a lot of work.&lt;/p&gt;
&lt;p&gt;It’s Sentry’s annual HackWeek, and alongside my more standard project I wanted to burn some GPT-5.6 Sol tokens on something useful. I started poking at one expensive React test file to see how fast I could make it without rewriting it. No replacing &lt;code&gt;getByRole&lt;/code&gt; with &lt;code&gt;getByTestId&lt;/code&gt;. No swapping out &lt;code&gt;userEvent&lt;/code&gt;. The tests should stay exactly the same while the libraries underneath them get faster.&lt;/p&gt;
&lt;h2&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#the-result&quot;&gt;The result&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;I used &lt;a href=&quot;https://github.com/getsentry/sentry/blob/c73856753969efc2e12f13363c4db17a3b80849c/static/gsAdmin/components/provisionSubscriptionAction.spec.tsx&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;a real Sentry test file&lt;/a&gt; built around a large form.&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Setup&lt;/th&gt;&lt;th&gt;Time&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Sentry’s current jsdom 26 setup&lt;/td&gt;&lt;td&gt;12.41s&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;jsdom 30 before these changes&lt;/td&gt;&lt;td&gt;17.18s&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;With the merged label and event changes&lt;/td&gt;&lt;td&gt;12.09s&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;With the DOMSelector fast path too&lt;/td&gt;&lt;td&gt;&lt;strong&gt;9.77s&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Together, the three library changes made the jsdom 30 version &lt;strong&gt;43% faster&lt;/strong&gt;. The final result was also &lt;strong&gt;21% faster than the current jsdom 26 setup&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#using-codex&quot;&gt;Using Codex&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;I started with a vague prompt. I’ve found Sol works well when given a lofty goal:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I need you to find a greater than 20% performance gain in running &lt;code&gt;getByRole&lt;/code&gt; on a larger DOM.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Codex came back with an 81% microbenchmark win from indexing implicit roles by tag. Great, except the benchmark was basically designed around the code it had just made faster. I had it patch the change directly into Sentry’s &lt;code&gt;node_modules&lt;/code&gt; and run it there. It did nothing. I then asked how much time the file actually spent inside role queries. The answer was less than 1% of the runtime, so even an 81% improvement there was not going to matter.&lt;/p&gt;
&lt;p&gt;Along the way I had to steer Codex away from:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;treating a microbenchmark win as the final result&lt;/li&gt;
&lt;li&gt;splitting the test file so Jest could spread it across more workers&lt;/li&gt;
&lt;li&gt;rewriting the tests to use cheaper queries or interactions&lt;/li&gt;
&lt;li&gt;hacking up React’s development runtime for a change I could never land&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The change had to speed up the machinery underneath the tests, and it had to belong somewhere I could actually send it.&lt;/p&gt;
&lt;p&gt;I pointed Codex at the subscription form test instead. This one spent about 29% of its time in role queries. Profiling led to jsdom rescanning the document for &lt;code&gt;input.labels&lt;/code&gt;. We traced the behavior past &lt;code&gt;dom-accessibility-api&lt;/code&gt;, which only asks the browser for &lt;code&gt;.labels&lt;/code&gt;, to the jsdom code doing the repeated scans. That became the first jsdom fix.&lt;/p&gt;
&lt;p&gt;From there I kept Sentry and each library in separate checkouts. Codex patched Sentry’s installed dependencies for quick A/B tests. If an idea survived in Sentry, it moved into the repository that owned the code and got its own tests and benchmark. We repeated that loop for the event-path and selector fixes.&lt;/p&gt;
&lt;p&gt;By the second pull request, I had Codex read the feedback maintainers had left on earlier changes to the same files. We used that to check whether the code matched the repository’s patterns, whether the benchmark only showed the best case, and which correctness cases the tests needed to cover. That produced smaller changes, broader benchmarks, and better tests before opening the pull request.&lt;/p&gt;
&lt;p&gt;My job was to make it prove each win in a real test, kill the weak ideas, and keep asking where the fix should actually live.&lt;/p&gt;
&lt;h2&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#stop-scanning-every-label-over-and-over&quot;&gt;Stop scanning every label over and over&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The biggest win came from how jsdom handled &lt;code&gt;input.labels&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Testing Library calculates accessible names when you write something like this:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;&lt;span&gt;&lt;span&gt;screen.&lt;/span&gt;&lt;span&gt;getByRole&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&apos;&lt;/span&gt;&lt;span&gt;textbox&lt;/span&gt;&lt;span&gt;&apos;&lt;/span&gt;&lt;span&gt;, { name&lt;/span&gt;&lt;span&gt;:&lt;/span&gt;&lt;span&gt; &apos;&lt;/span&gt;&lt;span&gt;Email&lt;/span&gt;&lt;span&gt;&apos;&lt;/span&gt;&lt;span&gt; });&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Calculating that name can read the &lt;code&gt;labels&lt;/code&gt; property for every candidate input. Before &lt;a href=&quot;https://github.com/jsdom/jsdom/pull/4237&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;this change&lt;/a&gt;, every input walked the entire DOM root independently to find its labels.&lt;/p&gt;
&lt;p&gt;If a form had 100 controls, jsdom could scan the same DOM 100 times during one query, changing only the control it was looking for.&lt;/p&gt;
&lt;p&gt;The fix builds one label-to-control index for the current root and shares it between all the controls. When the DOM changes, jsdom throws the index away and rebuilds it the next time someone needs it. The live &lt;code&gt;labels&lt;/code&gt; collections still behave like they should.&lt;/p&gt;
&lt;p&gt;Reading the labels for 100 controls went from &lt;strong&gt;60.52ms to 0.67ms&lt;/strong&gt;, about &lt;strong&gt;91 times faster&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#the-selector-fast-path-was-never-fast&quot;&gt;The selector fast path was never fast&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;jsdom uses &lt;a href=&quot;https://github.com/asamuzaK/domSelector&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;DOMSelector&lt;/a&gt; for selector matching. DOMSelector has a fast path for the selectors it supports in &lt;code&gt;matches()&lt;/code&gt;, but jsdom has two JavaScript objects representing the document: its internal implementation object and the public &lt;code&gt;document&lt;/code&gt; wrapper.&lt;/p&gt;
&lt;p&gt;The fast-path check compared those two objects with &lt;code&gt;===&lt;/code&gt;. They can never be equal. Every supported &lt;code&gt;matches()&lt;/code&gt; call coming from jsdom fell through to the slower general-purpose matcher.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/asamuzaK/domSelector/pull/309&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;The fix&lt;/a&gt; teaches DOMSelector that the wrapper and implementation object are the same document before doing the comparison.&lt;/p&gt;
&lt;p&gt;The matcher benchmark took &lt;strong&gt;89% less time&lt;/strong&gt;. A larger &lt;code&gt;getByRole(&apos;button&apos;)&lt;/code&gt; benchmark took &lt;strong&gt;42% less time&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Testing Library and jsdom call &lt;code&gt;matches()&lt;/code&gt; all over the place. The fast selector already existed; jsdom just never reached it.&lt;/p&gt;
&lt;h2&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#events-should-not-keep-searching-the-same-path&quot;&gt;Events should not keep searching the same path&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Dispatching an event means building a path from the target through its ancestors. jsdom then has to work out the correct &lt;code&gt;event.target&lt;/code&gt; at every stop, including shadow DOM cases.&lt;/p&gt;
&lt;p&gt;Before &lt;a href=&quot;https://github.com/jsdom/jsdom/pull/4242&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;this change&lt;/a&gt;, every stop searched backward through the event path to find its target. A deeper tree meant a longer path and more repeated searching through that path. jsdom also prepared listener state for elements that did not have a listener for that event.&lt;/p&gt;
&lt;p&gt;The fix records the effective target while building the path, then reads it directly during dispatch. It also skips the listener setup when nothing is listening for that event.&lt;/p&gt;
&lt;p&gt;Event throughput improved by &lt;strong&gt;12% to 36%&lt;/strong&gt;, depending on the depth of the tree and how many elements had listeners.&lt;/p&gt;
&lt;p&gt;That matters for React tests because &lt;code&gt;userEvent&lt;/code&gt; does not dispatch one event and call it a day. A normal interaction can produce a small parade of pointer, mouse, focus, input, and click events. Saving work on every event adds up across a test suite without changing how any listener sees the event.&lt;/p&gt;
&lt;h2&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#what-this-means-for-your-tests&quot;&gt;What this means for your tests&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Your test suite probably will not see the same improvement. This file happened to hit all three hot paths: a large labeled form, lots of semantic Testing Library queries, and plenty of user interactions.&lt;/p&gt;
&lt;p&gt;These changes matter most for tests with:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;large forms with many labels and controls&lt;/li&gt;
&lt;li&gt;lots of &lt;code&gt;getByRole&lt;/code&gt; queries using accessible names&lt;/li&gt;
&lt;li&gt;deep rendered DOM trees&lt;/li&gt;
&lt;li&gt;many &lt;code&gt;userEvent&lt;/code&gt; or &lt;code&gt;fireEvent&lt;/code&gt; interactions&lt;/li&gt;
&lt;li&gt;libraries that make heavy use of &lt;code&gt;matches()&lt;/code&gt; in jsdom&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;As of this post, the &lt;a href=&quot;https://github.com/jsdom/jsdom/pull/4237&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;label cache&lt;/a&gt; and &lt;a href=&quot;https://github.com/jsdom/jsdom/pull/4242&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;event-path&lt;/a&gt; changes have landed in jsdom, but neither is in a published release yet. The &lt;a href=&quot;https://github.com/asamuzaK/domSelector/pull/309&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;DOMSelector fast-path fix&lt;/a&gt; is still open.&lt;/p&gt;
&lt;p&gt;Thanks to jsdom maintainer &lt;a href=&quot;https://github.com/domenic&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Domenic Denicola&lt;/a&gt; for reviewing the vibecoded slop and merging both jsdom changes.&lt;/p&gt;
&lt;figure data-breakout=&quot;wide&quot;&gt;&lt;a class=&quot;content-image-link&quot; href=&quot;./label-bureaucracy.png&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;img alt=&quot;Four office workers searching a wall of filing cabinets&quot; title=&quot;Click to open in new tab&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1672&quot; height=&quot;941&quot; src=&quot;/_astro/label-bureaucracy.8JtL1BbV_Z1tYbiE.webp&quot; srcset=&quot;/_astro/label-bureaucracy.8JtL1BbV_ZNwYzG.webp 640w, /_astro/label-bureaucracy.8JtL1BbV_s2Wra.webp 750w, /_astro/label-bureaucracy.8JtL1BbV_ZvyLQD.webp 828w, /_astro/label-bureaucracy.8JtL1BbV_17vez0.webp 1080w, /_astro/label-bureaucracy.8JtL1BbV_gSOx2.webp 1280w, /_astro/label-bureaucracy.8JtL1BbV_ZJMoIs.webp 1668w, /_astro/label-bureaucracy.8JtL1BbV_Z1tYbiE.webp 1672w&quot; /&gt;&lt;/a&gt;&lt;figcaption class=&quot;image-subtext&quot;&gt;AI-generated image of four office workers searching a wall of filing cabinets&lt;/figcaption&gt;&lt;/figure&gt;</content:encoded><category>ai</category><category>vibecoding</category><category>typescript</category><category>testing</category><category>performance</category></item><item><title>You can just port things to Cloudflare Workers</title><link>https://sigh.dev/posts/you-can-just-port-things-to-cloudflare-workers/</link><guid isPermaLink="true">https://sigh.dev/posts/you-can-just-port-things-to-cloudflare-workers/</guid><description>Vibecoding, Vibeporting?</description><pubDate>Sun, 25 Jan 2026 08:00:00 GMT</pubDate><content:encoded>&lt;p&gt;This January I decided to double down on using up my &lt;a href=&quot;/posts/addicted-to-free-ai-credits/&quot;&gt;free ai credits&lt;/a&gt; by building a few projects on Cloudflare Workers. I’ve always really liked the idea of this platform that has cheap/free resources, but every time I build larger things on it I run into limits that make me frustrated and move to cheap vps hosting like fly.io or DigitalOcean.&lt;/p&gt;
&lt;p&gt;Is vibeporting a word? Maybe it should be?&lt;/p&gt;
&lt;h1&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#datasette-ts&quot;&gt;Datasette-ts&lt;/a&gt;&lt;/h1&gt;
&lt;figure&gt;&lt;a class=&quot;content-image-link&quot; href=&quot;./datasette.png&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;img alt=&quot;Datasette running on Cloudflare Workers&quot; title=&quot;Click to open in new tab&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1964&quot; height=&quot;1272&quot; src=&quot;/_astro/datasette.lR6-YtED_233bVL.webp&quot; srcset=&quot;/_astro/datasette.lR6-YtED_DHcnO.webp 640w, /_astro/datasette.lR6-YtED_1lQtBx.webp 750w, /_astro/datasette.lR6-YtED_ZYtjVw.webp 828w, /_astro/datasette.lR6-YtED_Z1T6aTX.webp 1080w, /_astro/datasette.lR6-YtED_Z1WrAH6.webp 1280w, /_astro/datasette.lR6-YtED_16XG7w.webp 1668w, /_astro/datasette.lR6-YtED_233bVL.webp 1964w&quot; /&gt;&lt;/a&gt;&lt;figcaption class=&quot;image-subtext&quot;&gt;A port of Datasette to Cloudflare Workers&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;Over holiday break, I was reading some of &lt;a href=&quot;https://simonwillison.net/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Simon Willison’s posts about AI&lt;/a&gt; and I checked where it’s currently possible to deploy it. You can deploy it pretty much everywhere but NOT on Cloudflare Workers, due to workers not really supporting much of Python’s ecosystem. I pointed Codex with GPT-5.2 Codex high/medium at the Datasette repo and had it break it down into README tasks and slowly do them one at a time. I’m not yet convinced by the crazy subagent stuff or that worktrees are worth it.&lt;/p&gt;
&lt;p&gt;As I got into it, it was clear I needed to narrow down the scope. Mr. Willison has built a very mature project that has a plugin system and a ton of features built-in and it depends on subdependencies that he also has published like sqlite-utils. Obviously, what I wanted is something that feels similar and runs on Cloudflare Workers. I picked up Drizzle, Hono, and Alchemy to handle Cloudflare deployments. I chose not to rebuild the frontend as a React SPA instead rendering something similar to the original Jinja templates using Hono’s JSX.&lt;/p&gt;
&lt;p&gt;Anyway, it ends up working pretty well. You can see a live demo at &lt;a href=&quot;https://datasette-legislators.sigh.dev/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;datasette-legislators.sigh.dev&lt;/a&gt; and the source is available below. I can’t say the code is in a good state, but it lives here &lt;a href=&quot;https://github.com/scttcper/datasette-ts&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;https://github.com/scttcper/datasette-ts&lt;/a&gt;.&lt;/p&gt;
&lt;h1&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#sesnoop&quot;&gt;SESnoop&lt;/a&gt;&lt;/h1&gt;
&lt;figure&gt;&lt;a class=&quot;content-image-link&quot; href=&quot;./sesnoop.png&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;img alt=&quot;SESnoop running on Cloudflare Workers&quot; title=&quot;Click to open in new tab&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;2712&quot; height=&quot;2030&quot; src=&quot;/_astro/sesnoop.C6_5umH9_6I98D.webp&quot; srcset=&quot;/_astro/sesnoop.C6_5umH9_Z7vDFx.webp 640w, /_astro/sesnoop.C6_5umH9_Z24bGBN.webp 750w, /_astro/sesnoop.C6_5umH9_1wFp8k.webp 828w, /_astro/sesnoop.C6_5umH9_Z8l2QN.webp 1080w, /_astro/sesnoop.C6_5umH9_ZhGSUF.webp 1280w, /_astro/sesnoop.C6_5umH9_Z1FyIf3.webp 1668w, /_astro/sesnoop.C6_5umH9_umF3j.webp 2048w, /_astro/sesnoop.C6_5umH9_Z1aKnlE.webp 2560w, /_astro/sesnoop.C6_5umH9_6I98D.webp 2712w&quot; /&gt;&lt;/a&gt;&lt;figcaption class=&quot;image-subtext&quot;&gt;A port of Sessy to Cloudflare Workers&lt;/figcaption&gt;&lt;/figure&gt;
&lt;p&gt;Another Cloudflare Worker port, this time of a Rails app called &lt;a href=&quot;https://sessy.do&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Sessy&lt;/a&gt;. I decided to rename it because I was going for a different vibe. I send a bunch of emails via SES for xmplaylist.com and I was looking into running Sessy to handle the bounces and complaints, however I can’t get myself to think about Ruby for more than 1 minute. So again I pointed Codex at the Sessy repo and a few other Cloudflare/Hono example repos and had it build out a monorepo where the worker handles the api and Cloudflare assets serves a React SPA frontend.&lt;/p&gt;
&lt;p&gt;I think what was hard to reel in was how much frontend it was willing to build before I could stop it and start bringing in shadcn components. Like it made a bunch of select components and things that were generally pretty ugly. So then you have to tell it to replace all the ugly things with premade shadcn + baseui components.&lt;/p&gt;
&lt;p&gt;This project took a bit more work to get working outside of pointing AI at the code. It made a number of Cloudflare mistakes, tests were difficult to get working 100% correctly. One example was that it put the webhook at &lt;code&gt;/webhook&lt;/code&gt; which Cloudflare would attempt to load as an asset since the worker is bound to &lt;code&gt;/api&lt;/code&gt; which is always a bit of a headscratcher until you remember how this all works. It was really cool getting to know how SNS works with SES and watching them flow into D1 is fun.&lt;/p&gt;
&lt;p&gt;I tried publishing this package to npm and it kinda works to deploy to cloudflare if alchemy is setup. Or you can run it locally with &lt;code&gt;npx datasette-ts@latest serve ./legislators.db&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;I don’t have a live demo, but you can check out the source code at &lt;a href=&quot;https://github.com/scttcper/sesnoop&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;scttcper/sesnoop&lt;/a&gt;.&lt;/p&gt;
&lt;h1&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#conclusion&quot;&gt;Conclusion&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Pretty happy with how both of these turned out. I didn’t exclusively use Codex on either of them, however Codex was the main driver 95% of the time. I think Codex w/ GPT-5.2 Codex on high or medium is a great model and through the team plan you can basically run medium as long as you want. I exhausted about 1 week worth of the plan I’m on for Codex for each project.&lt;/p&gt;</content:encoded><category>vibecoding</category><category>cloudflare</category><category>typescript</category><category>ai</category></item><item><title>I’m addicted to free AI credits</title><link>https://sigh.dev/posts/addicted-to-free-ai-credits/</link><guid isPermaLink="true">https://sigh.dev/posts/addicted-to-free-ai-credits/</guid><description>Free models, free credits, free VS Code forks. I’m using all of it while it lasts.</description><pubDate>Sun, 14 Dec 2025 08:00:00 GMT</pubDate><content:encoded>&lt;p&gt;You might be too late to enjoy the era of $5 Ubers in SF, but you can still get a ride for free with AI. I’m absolutely hooked on using any available free AI models. Cursor will randomly announce that a new model is free for a week or whatever and I’m fucking there. Remember that time SOTA models were available for free? That was last week, and it’s hard to say how long this sort of spending will continue.&lt;/p&gt;
&lt;p&gt;Opus 4.5 was free for a while, and it did get me hooked on the model. I had tried Sonnet 4.5 a number of times but found it annoyingly cheerful and not as good as GPT-5.1 (granted GPT-5.1 came out way later). Now that I’m faced with having to pay for Opus 4.5, I am certainly tempted and I can see why so many are willing to jump on Claude Code.&lt;/p&gt;
&lt;p&gt;GitHub’s Copilot is giving me their monthly free open source subscription to a limited Copilot plan. I like how they’re still using the old Cursor pricing billed by requests rather than tokens. You can get quite a few things done with that. Google’s antigravity is interesting, but so far it seems to expire before it gets anywhere. I think the one takeaway from chasing free credits is that all the VS Code forks are now basically the same, assuming they have a plan feature. The furthest behind might be Gemini’s VS Code extension, which is a fairly shit experience. I’ve tried some free models and bounced off because they produce more slop than anything useful. Grok’s models are all shit so far.&lt;/p&gt;
&lt;h3&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#what-did-i-build&quot;&gt;What did I build?&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;I launched a paid plan for &lt;a href=&quot;https://xmplaylist.com/pricing&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;xmplaylist.com&lt;/a&gt; and improved a number of my open source projects. I’d say the best use of these free credits has been nice little admin pages that I never would have spent time building. I can point the agent at enough examples that it needs hardly any direction to get it done. I only really do TypeScript in my free time and I’m sometimes jealous of the Django admins in other languages. Slop together a similar admin with TypeScript and &lt;a href=&quot;https://orm.drizzle.team/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;drizzle&lt;/a&gt; and you’ve likely got a better dev experience than any Django app.&lt;/p&gt;
&lt;p&gt;I’m sure the free tokens will be locked down soon. I’m riding around as much as I can.&lt;/p&gt;
&lt;h4&gt;&lt;a class=&quot;not-prose&quot; href=&quot;#some-random-predictions-for-2027&quot;&gt;Some random predictions for 2027:&lt;/a&gt;&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;People will use smaller models to save money and because they’ve caught up in performance. I’m hopeful for Gemini 3 Flash and not hopeful for SOTA getting cheaper.&lt;/li&gt;
&lt;li&gt;Cursor will have to drop the price on their composer-1 model (which works great)&lt;/li&gt;
&lt;li&gt;At least 2 more VS Code forks will launch&lt;/li&gt;
&lt;li&gt;I’ll still be chasing free SOTA models&lt;/li&gt;
&lt;li&gt;Grok will continue to be 2nd rate&lt;/li&gt;
&lt;li&gt;I’ll actually pay for a personal plan from some provider&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;TODO:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;try windsurf&lt;/li&gt;
&lt;/ul&gt;
&lt;figure&gt;&lt;a class=&quot;content-image-link&quot; href=&quot;./uber-2017.png&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;&lt;img src=&quot;/_astro/uber-2017.Dy9Ys4ZO_Z1Cg7kp.webp&quot; srcset=&quot;/_astro/uber-2017.Dy9Ys4ZO_ZDflhY.webp 640w, /_astro/uber-2017.Dy9Ys4ZO_Z220fcE.webp 750w, /_astro/uber-2017.Dy9Ys4ZO_21KIiX.webp 828w, /_astro/uber-2017.Dy9Ys4ZO_Z1epGIr.webp 1080w, /_astro/uber-2017.Dy9Ys4ZO_Z1Cg7kp.webp 1272w&quot; alt=&quot;5 dollar uber&quot; title=&quot;Click to open in new tab&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1272&quot; height=&quot;1026&quot; /&gt;&lt;/a&gt;&lt;figcaption class=&quot;image-subtext&quot;&gt;five dollar uber in sf circa 2017. Currently $17 for the same trip&lt;/figcaption&gt;&lt;/figure&gt;</content:encoded><category>ai</category><category>typescript</category><category>vibecoding</category></item></channel></rss>