hrishi
The frontier is open-source today
Three years in amber: resurrecting WASM-AI from long ago
Hankweave: A runtime for data agents, designed for debugging
Long story short: we needed something to actually do brownfield agentic engineering with: something that made it easier to reason about what an agent will see in context at any point in time, remove and flush context often, clear handoffs, better primitives.
Something we noticed is that LLMs have started co-evolving with their harnesses - anthropic gets more training data from you using claude code, claude code gets new features from claude first, etc etc - so we decided to change the base primitive from the llm call to the agent loop. almost any harness - codex, opencode, etc - is supported, you just need to generate a shim using one of the hanks like we do.
So we ended up building a runtime that executes sequenced AI programs - blocks of prompts and code that get loaded into context, run, monitored and then torn down.
We’ve been using it for a while, open-sourcing it in case its useful. Maybe it’s our visibility set but there’s not much out there focused on reliable executions and doing less so you can think more.
It’s single agent threaded (no parallel agent things), designed for headless (we’re a data company), no MCP or skills things - our general policy has been ‘build what you NEED’ and we just haven’t EVER needed those things.
Have fun!
Read more about the idea behind it here: https://southbridge.ai/hankweave
Antibrittle Agents
Claude Code: An Agentic cleanroom analysis
Entropixplained
A solid pattern to build LLM Applications (feat. Claude)
The Web's Grain
Run Whisper+Mistral in the Browser with WASM
Add that to the fact that all user tests we've done have fared better with search and more verbose interfaces, and I wonder if we are both of us far from the target user profile.
Write for your colleagues, your partner, or just yourself, so you can clarify the streams of thought in your head and bang them against something.
Even if you never publish, you'll benefit. Chances are, you'll find a few you want to publish along the way.
Losing our product to button syndrome
I've wondered this myself for a long time, before realising that titles like these get most of the attention, enough to rise to your feed.
If this was indeed 'Consider using /events', chances are you'll never see it.
PhD Student discovers a new type of Water Splitting
I speak four languages fluently, and 'OK', 'Abort', 'Retry' and 'Load' are some of the hardest things to translate.
Clearing out the lists make a big difference. I'm reminded of a video I watched [1] where deleting photos more often made it easier for the author to remember his life better. I've been trying it more, and he's right - it works!
The part about anecdotes hit home, where I'll remember the description for something but not the name, or the name and how it's connected but not enough to really explain it. "I remember it made sense when I was reading it, you'll need to trust me" is not that great.
Agree with the subcomments, the work involved becomes smaller and smaller as your brain gets better at it - somewhat like journaling. If you're willing to put in the extra work at the beginning, it's also a great memory booster. Your brain learns to understand that you intend to remember something, so the connections feel stronger. I definitely recommend it. Even something like a short journal at the end of the day makes a big difference.
The biggest thing is being okay with letting some things go - which has been hard for me, yet has made a huge difference. If you don't have the time to properly put it down to be remembered, accept that it's likely to be lost and move on. If it's important or interesting enough, your mind will remember without the need to save it.
It's a tiny, tiny slice of things that I can ever pull out of the knapsack. Either I've forgotten enough that I don't have enough metadata (or even that they exist), or I remember enough that I can just find it again.