The Fetch: Week 15, 2026
AI coding receipts, smarter browser terminals, diagram magic, DuckDB cloud vibes, and content pipelines that actually ship
Codeburn: Finally, Receipts for AI Coding
github.com/AgentSeal/codeburn | License: MIT
The Motion: Token Spend Gets an Audit Trail
AI coding bills have gotten weirdly opaque, and Codeburn lands right on that pain. It reads local session data from Claude Code, Codex, and Cursor, then turns the mess into an interactive terminal dashboard with one-shot rate, 13 task categories, and provider-by-provider cost breakdowns. The interesting part is that it is not another wrapper or proxy. It watches what already happened on disk, classifies retries, and shows where tokens disappeared across models, tools, projects, and MCP servers. That clarity is catnip right now as more teams realize vibe coding still has a budget line.
The Wave: The CFO Arc for Dev Tooling
Codeburn feels early, but the direction is very obvious. As coding agents become normal, developers will want observability that feels as native as git status, not another SaaS tab. This has the right shape for solo builders tracking burn, platform teams setting norms, and anyone comparing Claude, Codex, and Cursor without guesswork. The next move would be making the provider plugin system the star, because support for every new agent tool could turn this from a useful tracker into the default scoreboard for AI-assisted development. Honestly, that ceiling is huge.
Stars: 1,672 | Language: TypeScript
Fireworks Tech Graph: Diagram Work Finally Got Interesting
github.com/yizhiyanhua-ai/fireworks-tech-graph | License: MIT
The Motion: Technical Diagrams From Plain English
Fireworks Tech Graph turns natural language into polished technical diagrams, then ships both SVG + PNG output without the usual formatting pain. That alone is useful. The interesting part is the stack of opinionated structure behind it: 14 diagram types, 7 visual styles, built-in AI/Agent domain patterns, and a semantic arrow system that makes flows read like actual systems instead of random boxes. People are starring it now because AI tooling is making more architecture docs than ever, and nobody wants to hand-tune Mermaid or drag shapes around for every RAG, multi-agent, or tool-call diagram.
The Wave: This Could Become the Default Diagram Skill
This feels like the kind of repo that sneaks into every serious AI workflow once teams realize screenshots from whiteboards are not documentation. Fireworks Tech Graph already has a strong lane with agent architectures, memory systems, UML, and branded styles that look ready for docs on day one. Honestly, that combo is sticky. The next move is simple: make the prompt-to-output path even more predictable with more canonical templates, more before-and-after examples, and tighter regression tests across styles. That would make this ridiculously easy to trust in product docs, blog posts, and internal design reviews.
Stars: 2,905 | Language: Python
Wterm: The Browser Terminal Finally Feels Right
github.com/vercel-labs/wterm | License: Apache-2.0
The Motion: DOM Beats Canvas Here
Wterm is a web terminal that takes a very different route: DOM rendering instead of the usual canvas-heavy approach. That means native text selection, copy and paste, browser find, and accessibility all show up without weird hacks. Underneath, the Zig + WASM core keeps things fast with a tiny parser binary, while dirty-row tracking only redraws what changed. The timing makes sense. More teams want terminals inside docs, dashboards, AI tools, and browser-based dev environments, and Wterm feels built for that exact moment.
The Wave: Quietly Becoming the Embedded Default
This has the shape of a repo that could spread fast across frontend teams, especially with @wterm/react, WebSocket transport, and even just-bash for in-browser shell demos. The interesting part is that it is not chasing terminal nostalgia. It is making terminals behave like normal web UI, which is way more useful than it sounds. Anyone building cloud IDEs, infra dashboards, agent consoles, or interactive docs should be watching. The next move that would make this unstoppable is a deeper showcase around production-scale performance and compatibility, especially for apps pushing heavy scrollback and full-screen terminal workflows.
Stars: 372 | Language: TypeScript
OpenDuck: MotherDuck Energy, Open Source
github.com/CITGuru/openduck | License: MIT
The Motion: DuckDB Cloud Without the Black Box
OpenDuck takes the very specific magic people love about MotherDuck and makes it hackable: differential storage, dual execution, and a clean openduck: attach flow that makes remote databases feel local inside DuckDB. The interesting part is how deep it goes. This is not another generic SQL proxy. Remote tables show up as native catalog entries, queries split across laptop and worker, and only intermediate results move over the wire via gRPC and Arrow IPC. Stars are showing up now because the DuckDB crowd has wanted this exact architecture in the open for a while.
The Wave: DuckDB Infra Builders Are Going to Swarm This
This feels like the start of an open stack for teams that want DuckDB to escape the laptop without losing the local-first UX that made it blow up. It should matter to data infra tinkerers, self-hosting teams, and anyone building analytics products on top of DuckDB who wants cloud behavior without vendor lock-in. Honestly, the repo is early, but the direction is sharp. The next move that would make this unstoppable is smoothing setup fast, especially around extension install and unsigned builds, because this kind of project wins when the first remote attach feels almost boring.
Stars: 367 | Language: C++
GEOFlow: AI Content Ops, Actually End-to-End
github.com/yaojingang/GEOFlow | License: Apache-2.0
The Motion: From Prompt to Published Site
GEOFlow is not another thin wrapper around an LLM. It stitches multi-model content generation, task scheduling, material management, and a draft-review-publish workflow into one PHP system that can actually run a content operation. That matters right now because GEO and SEO teams are trying to move past one-off article generators into repeatable pipelines. The interesting part is that it ships the boring but necessary stuff too: queues, retries, publishing rules, front-end article output, and OpenAI-compatible model support. Honestly, that full-chain setup is exactly why stars are showing up fast.
The Wave: Built for the AI Publishing Stack
This feels early, but very pointed. GEOFlow could become the default self-hosted backbone for teams building automated content sites, internal publishing backends, or niche SEO farms with human review still in the loop. The repo already understands that content ops is more than generation. It is prompts, assets, approvals, and distribution. That makes it interesting to founders, growth teams, agencies, and indie operators hunting for control instead of SaaS lock-in. The next move that would make this unstoppable is tighter onboarding around production templates and best-practice workflows, so new users can go from Docker launch to a working content pipeline ridiculously fast.
Stars: 649 | Language: PHP