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

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/ 🧵

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…

Best uses of smithers so far - Burns — Workspace-first local control plane for authoring, running, and supervising Smithers workflows (web/desktop/CLI) github.com/l3wi/burns - Ralphinho — Multi-agent dev workflows that turn RFCs into landed code and automate code review github.com/enitrat/ralphinho - Cairo Coder — AI-powered Cairo smart contract generator using a RAG pipeline with Smithers orchestration github.com/KasarLabs/cairo-c… - Agentix — Opinionated RFC-to-production workflow orchestrator with DDD/BDD/TDD and merge queues github.com/AbdelStark/agenti… - Era — Generic reusable multi-phase dev workflow engine (research → plan → implement → test → review) github.com/ClementWalter/era - Local Isolated Ralph — Kubernetes-native runner for Smithers workflows as isolated K8s Jobs/CronJobs github.com/SamuelLHuber/loca…

It sounds so gimmicky AI Orchestration framework via React But hear me out, Smithers is secretly the best-in-class agentic orchestration framework In this 🧵 I answer two questions 1. Why you even need an orchestration framework? 2. Why that orchestration framework should be smithers 🧵 1/18

Proudly introducing JJHub A new code platform for agentic engineering teams 🧵 1/n

You should use Voltaire over alternatives because I love zig and learned what good zig looks like This alternative zig library screenshotted below lists "comptime-first" as a reason to use their library over alternatives like Voltaire. comptimeSelector("transfer(address,uint256)"); This is a bad practice in zig. Libraries should not declare library functions as comptime. Why? Because any function can be used in comptime or runtime using comptime keyword comptime selector("transfer(address,uint256)"); Also, even if you don't explicitly declare comptime LLVM in both zig and rust will be smart enough to constant fold here I won't name and shame this library because I think they mean well and I support all OSS builders.

I don't think I ever shared this one We have a repo that autogenerates chain constants in zig ts and golang from @DefiLlama chainlist github.com/evmts/chains

I have a lot of unreleased projects. Should any of these get released?

We are going to see if we can build an ethereum full client fully with AI 🧵

Building robust custom indexers with voltaire-effect is so nice. Come for the abstractions stay for the incredible visibility and monitoring you can get

I could see myself using this feature. I can just ask the agent to unapprove token allowances It's like miniapps on demand using voltaire-effect