Just released evmstate, a TypeScript library to trace & visualize state changes on EVM chains, with human-readable labels (variable names, mapping keys, decoded values, etc).

You can now open SSH on a sandbox from Silo and connect from this machine or another. Works with a terminal or an agent harness, against a local or remote VM. github.com/0xpolarzero/silo/…

zhipu absolutley nailing pursuing the element that played in oss models favour from the HF incident masterclass in adpating goals and roadmaps to informatin as they come. anthro and oai neuter you cause they believe humans are more bad than good and they need to control every outcome. kimi and zhipu are there to serve you cause they beleive the future is built toghther in the open and no one person or group can pursue that. individualism and collectivism battling it out on the grand stage

Check out Tevm Test test.tevm.sh/

STRONGLY recommended reading You're in for a treat at the end, you won't even have to bookmark it for "putting it into practice later": it's a tool that lets your agent put it into practice for you...

Tokens are just intelligence, with enough intelligence you can solve anything

Monitoring has landed in Smithers 0.18.0! 🚀 We also shipped some of the most asked for features - Ability to share and use other users workflows - Node.js, Browser, Cloudflare worker, and Vercel support - And a lot more! 🧵

Only Smithers supports this feature: Time Travel No other orchestration framework is built from ground up to be this observable debuggable and durable while supporting multiple providers 1. Smithers saves "frames" to sqlite everytime updates happen 2. JJ snapshots the state of the file system every frame 3. The frame provides perfect visibility into what smithers is doing and why 4. You as the user can time travel back to any frame at any time reverting botht he file system and the state of smithers to that frame

Best way to make a harness is with smithers You get the holy trinity of orchestration for free: durability, observability and composability It makes your agentic systems durable, inspectable, and composable with clear coordination between agents, humans and programmatic code

LLMs still barely understand your intent, have no taste and require constant babysitting. You can't stay outside the loop for long on any complex-enough problem. It's still a dumb slop machine and it's great; you're still forced to learn from its poor choices.

Smithers 0.23.0 is here Everybody is talking about loops. Smithers users are already doing them This release ships a brand new docs site, usage quota features, and quality of life features 1/ 🧵

Has been a while since I wrote about agentic engineering, so this time around some learnings of maintaining Pi as a junior maintainer to @badlogicgames :) lucumr.pocoo.org/2026/5/24/p…

The bun rewrite is some of the most impressive harness engineering I've seen. @jarredsumner basically first invented his own minimal version of Smithers and then thoughtfully created what is a high quality zig to rust compiler utilizing llms Since it's one of the best examples of building a long running workflow I have seen I am busy porting it to using Smithers directly as a demo

gstack is one of the most interesting AI repos Hear me out, it points to a new kind of app: a Markdown app. - The language is markdowny agentic harness - The language is markdown - The app is the workflow. And it works! It works so well it's fair to ask "why smithers?". Clearly all workflows can just be human language skills. So what is the point of smithers? Is it not overengineering. To answer this question I migrated gstack to smithers. The results: - 31 gstack skills went from generated Markdown procedures to typed Smithers workflows. - The old workflow surface was ~42k lines of generated `SKILL.md`. - The new workflow surface is ~5.4k lines of typed `.tsx`. - Gstack skills can be composed as react components - Smithers resumability, inspectability, replayability, forking features, and UI all plug right in But most importantly, I didn't migrate the workflow. An agent did. The point of Smithers is agents love structure. And if you give your agent smithers it's ability to orchestrate itself for reusable long living workflows explodes. And since the programming model of smithers is so similar to React, agents are already great at intuitively know how to build complex workflows with smithers from their pretraining on React. So smithers isn't an alternative to Markdown app programming. It's a more powerful way of doing it. It allows your agent to communicate both in human language and real control flow in a structured way agents love Check out smithers docs: smithers.sh And check out gsmithers: github.com/smithersai/gsmith…

My most valuable insights in term of development with AI (and dev in general) come from @FUCORY (or from working with him). There is a good chance you wanna use smithers, and if you do you’re blessed, cause you’ll be able to shape it with your feedback, or customize it yourself.