cocoindex-io/cocoindex-code: A super light-weight embedded code search engine CLI (AST based) that just works - saves 70% token and improves speed for coding agent 🌟 Star if you like it!
A super light-weight embedded code search engine CLI (AST based) that just works - saves 70% token and improves speed for coding agent 🌟 Star if you like it! - cocoindex-io/cocoindex-code
vercel-labs/dev3000: Captures your web app's complete development timeline - server logs, browser events, console messages, network requests, and automatic screenshots - in a unified, timestamped feed for AI debugging.
Captures your web app's complete development timeline - server logs, browser events, console messages, network requests, and automatic screenshots - in a unified, timestamped feed for AI debugg...
alchemy — zero to production. TypeScript IaC on Effect.
Alchemy is the IaC tool that's actually TypeScript. Stand up your whole cloud in one program, type-check the IAM, hot-reload it locally, run tests against the real cloud, preview every PR, and ship dashboards & alarms in the same file.
lahfir/agent-desktop: Native desktop automation CLI for AI agents. Control any application through OS accessibility trees with structured JSON output and deterministic element refs.
Native desktop automation CLI for AI agents. Control any application through OS accessibility trees with structured JSON output and deterministic element refs. - lahfir/agent-desktop
Last week, a tweet went viral showing a guy claiming that a Cursor/Claude agent deleted his company's production database. We watched from the sidelines as he tried to get a confession from the agent:
Formatting an entire 25 million line codebase overnight: the rubyfmt story
This is the story of how our Developer Productivity team extended and rolled out rubyfmt, our Rust-based zero-config, ultra-fast autoformatter across the world's largest Ruby codebase.
My good mate Yaroslav wrote about his new solution for bundling a complete Bun runtime inside a gem - by all means, give it a read. A lot of points he makes are very sensible, but for a few months now I have decided that - for myself - I will not be using any frontend bundling nor JS runtime at all. Here’s how you can do the same. How useful is an asset pipeline? There is, in fact, just one sensible use case for needing an asset pipeline, and it goes as follows. You are running revision abc0 on two machines, box1 and box2 You make some glorious changes to your frontend code, and a new version gets prepared which requires those changes to be applied to the frontend assets your users get loaded You deploy revision def1 with those changes. Then, because you sensibly deploy blue/green, the following happens: box1 gets the new version deployed, and a user hits it and loads the root page. The root page includes a reference to scripts.js, which is served from the same application. The browser shoots out a request for scripts.js as soon as it sees it while HTML is coming down on the wire The request for scripts.js ends up not on box1, but on box2. That box is still running your older version - the user gets their assets loaded for the older application revision, and gets a broken experience.
Fixing JavaScript observability, one library at a time
Sentry is adding TracingChannel support to 44 JavaScript libraries upstream, replacing fragile monkey-patching with native observability that works across all runtimes.
An AI-generated projection of React's public API, shaped around what a TanStack Start app needs. ~9KB client, 2–3× faster on our workloads. Powers this blog today; capable of running tanstack.com end-to-end with no known regressions. An experiment, not a product. Not going into TanStack Start. Released, but not marketed.