Dev log #19 WebRTC v2 flows, agentic orchestration, and a perfectly synced vault

This week was a high-output sprint across the stack—from low-level p2p networking in Python to refining agentic workflows in TypeScript. I pushed 53 commits and opened 13 PRs, maintaining a perfect 7-day streak while balancing deep protocol work with personal knowledge management.

TL;DR

I didn't really intend for this to be a "build everything" week, but that’s exactly where the momentum took me. Between hardening WebRTC implementations in py-libp2p and chasing down edge cases in agent orchestration, I managed to ship 53 commits and keep my daily streak alive for the full seven days. The stats show a heavy tilt toward new code—over 12,000 additions—as I laid the groundwork for better telemetry and more robust p2p networking.

What I Built

Deep in the Networking weeds: py-libp2p

Most of my "deep work" hours went into py-libp2p. Networking code is unforgiving, but incredibly satisfying when it clicks. I spent a significant chunk of time in libp2p/kad_dht implementing configurable subnet-diversity limits and table-wide IP-group caps. If you've ever dealt with Sybil attacks or just messy peer distributions, you know why this matters—it’s about making the DHT resilient, not just functional.

On the transport side, I was neck-deep in libp2p/transport fixing WebRTC issues. I had to guard private-slot writes and ensure we’re using close_peer_connection at every production site to avoid hanging resources. I also spent time on a tricky Windows-specific bug where we needed to listen on a concrete non-loopback interface for tests to actually pass.

Hardening Reachable & Breakscale

I’ve been refining Reachable, specifically making the "Ask" feature behave more like a natural conversation. I had to harden the store behind it to ensure state doesn't drift when the UI gets complex.

Over at breakscale, I hit a weird one: Vitest failing on Node 26 because of jsdom's localStorage implementation. I opened an issue, tracked it down, and pushed a fix to put localStorage back where it belongs. I also shipped a feature to improve design descriptions—focusing on what a design is made of rather than just its dimensions. It’s a small UX shift, but it makes the tool feel much more intuitive.

The Digital Brain: obsidian-vault

I treat my obsidian-vault like a production repo, and this week it saw 35 commits. I was mostly syncing UI states and fixing templates. I noticed a bug in my "Concept" template where the parent pointer was recursively pointing at the template itself (classic meta-mess). I also logged three separate stream sessions, which has been a great way to document my thought process while I code.

Pull Requests & Orchestration

I opened 13 PRs this week, and while some are still in flight, they represent a lot of the "glue" work I do across the ecosystem.

A lot of my focus was on agent-orchestrator. I’m working on carrying request IDs into daemon-emitted events to make telemetry actually useful. There’s nothing worse than seeing an error in a log and having no way to trace it back to the original trigger. I also fixed a dev-server proxy issue where it was pointing at the wrong daemon—one of those "how did this ever work?" bugs that felt great to squash.

In the corsair repo, I’ve been on a mission to improve reliability and performance. I opened PRs to:

• Cover verifyHmacSignature with proper unit tests (security code without tests is just a disaster waiting to happen).
• Add database indexes on corsair_entities and corsair_accounts query paths. As the data grows, those sequential scans were starting to hurt.
• Clean up CLI error handling so async command failures don't just dump unhandled promise rejections into the terminal.

Issues & Community

I opened 7 issues this week, mostly as a way to "work in the open." When I find a bug in agent-orchestrator (like the Connect Mobile tailnet proxy stranding processes on ungraceful exits) or a performance bottleneck in corsair, I document it before I fix it. It helps me stay organized and gives the maintainers a heads-up on what I’m poking at.

One specific bug I’m still tracking is in omarchy, where selecting the default agent somehow triggers a version downgrade because of a mise release cooldown. It’s a weird interaction between the version manager and the agent logic that I’m hoping to resolve next week.

Tech Stack & Vibe

This was a polyglot week, but Python and TypeScript were the clear winners.

• Python: 84MB of code touched (mostly libp2p internals).
• TypeScript: 58MB of code across frontend tools and CLI utilities.
• The Mix: A bit of Lua for my nvim config updates and some Shell/Makefile glue to keep the CI pipelines happy.

With 12,205 additions against 1,500 deletions, this was definitely a "growth" week. I wasn't just cleaning up; I was shipping new features and expanding test suites. The 7-day streak wasn't forced—when you're bouncing between p2p protocols and AI agents, there's always one more thing you want to tweak before calling it a day.

What's Next

Next week, I’m planning to close out those WebRTC v2 PRs in py-libp2p. The specs are solid, but the implementation details around data-channel framing as a byte stream are still a bit finicky. I also want to get those corsair database indexes merged and see the real-world performance delta.

And of course, more streaming. I’ve found that logging my sessions in Obsidian has made me much more intentional about the code I write. If I have to explain it to a "future me" in a log, I'm less likely to take the lazy shortcut.

Catch you in the next push. Keep hacking.

---

Yash K Saini — Engineer, building in public — AI/ML, low-level (Rust/C/C++), and open source.

GitHub · X · LinkedIn · Portfolio

_{Generated by DevNotion}