fucory

17.1K posts

fucory banner
fucory

fucory

@FUCORY

Building - JJHub, Smithers, Tevm, Voltaire,

San Francisco, CA Katılım Mart 2011
1.6K Takip Edilen4.2K Takipçiler
Sabitlenmiş Tweet
fucory
fucory@FUCORY·
Proudly introducing JJHub A new code platform for agentic engineering teams 🧵 1/n
fucory tweet media
English
10
8
81
7.6K
fucory
fucory@FUCORY·
Breaking! Anthropic acquires pip install
English
0
0
9
218
Kris Kaczor 🦆⚡️
Kris Kaczor 🦆⚡️@krzKaczor·
@FUCORY AI powered CI checks are really intriguing. Recently I've started exploring @continuedev. For now I use them mostly to enforce again some things from AGENTS.md. Do you have some inspiring examples?
English
1
0
2
79
fucory
fucory@FUCORY·
The power of Smithers is gonna really be unlocked when people start combining it with jjhub JJHub is like if we took github actions, replaced yaml with typescript, and made the workflows super fast to run locally and in the cloud. In this world you want your workflows to be composable reusable and easy to improve over time. You start with a simple set of high impact workflows - ReproduceBug - CIChecks - VerifyDeploymentSuccess - ReviewPr You run these checks developing with clankers both locally and in cloud Engineers invest time into improving the workflows over time. They factor out reusable pieces to build more sophisticated workflows. Just one step at a time. Slow careful evolution 12 months later that engineering team will have a secure, robust AI automated set of workflows improving the velocity and quality of the codebase unlike any engineering teams before
fucory tweet media
English
1
2
17
786
fucory
fucory@FUCORY·
I feel 100% confident Tempo will ship state channel solution or something of similar flavor Why? Because if Tempo doesn't ship a state channel solution I don't trust they actually know what they are doing. But I would bet they know what they are doing
English
4
0
40
7K
fucory
fucory@FUCORY·
@sameandnot @agenticklabs Yea you can also use the CLI agents like Pi Amp ClaudeCode Opencode or Codex Your API got some things I should have been doing better so if you notice anything where you think your approach was much better open issue and I'll definitely make any changes you suggest
English
0
0
1
35
Ryan Lindgren
Ryan Lindgren@sameandnot·
@FUCORY @agenticklabs This looks really cool. I’m not very familiar with JJ but from what I understand of it this approach makes a lot of sense. Agents are run with ai-sdk under the hood, yeah?
English
1
0
1
23
fucory retweetledi
fucory
fucory@FUCORY·
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
fucory tweet media
English
5
8
32
6.2K
Samuel 🦤 (🧱,🔥)
Samuel 🦤 (🧱,🔥)@samuellhuber·
@MiniMax_AI @ryancarson in case you're code factory doesn't do this, it's likely a helpful overview for you cc @FUCORY re agents reading transcripts + metrics from smithers flows, updating the workflow / agent (e.g. pi extension writing on the go) -> it hot reloads and they watch for eval.
English
1
0
2
4K
MiniMax (official)
MiniMax (official)@MiniMax_AI·
Introducing MiniMax-M2.7, our first model which deeply participated in its own evolution, with an 88% win-rate vs M2.5 - Production-Ready SWE: With SOTA performance in SWE-Pro (56.22%) and Terminal Bench 2 (57.0%), M2.7 reduced intervention-to-recovery time for online incidents to 3-min on certain occasions. - Advanced Agentic Abilities: Trained for Agent Teams and tool search tool, with 97% skill adherence across 40+ complex skills. M2.7 is on par with Sonnet 4.6 in OpenClaw. - Professional Workspace: SOTA in professional knowledge, supports multi-turn, high-fidelity Office file editing. MiniMax Agent: agent.minimax.io API: platform.minimax.io Token Plan: platform.minimax.io/subscribe/toke…
MiniMax (official) tweet media
English
187
405
3.3K
1.7M
fucory
fucory@FUCORY·
I imagined myself working there. I'd think about the trust assumptions of stablecoins. I'm generally a product first person. And state channels produces the best product. I would have felt very strongly about this to the point where if I couldn't convince leadership that this is the correct path I would lose faith in leadership and leave So that combined with knowing leadership does in fact know what they are doing made it clear to me it's inevitable
English
0
0
10
469
Sebastian Bürgel
Sebastian Bürgel@SCBuergel·
A billion Wei idea for all you fancy VCs here: An Ethereum node that just works. Not stateless. No GigAgAss. No L2. No zk. But an unbelievable killer feature that nobody tried yet: You can query state and logs and the node (a) always responds with sub-minute latency and (b) actually responds correct data. I'm happy to invest the first 10k Wei myself.
English
10
4
60
8.2K
fucory
fucory@FUCORY·
I was an external contributor to that team and one of their biggest users. Because of the team getting laid off that is what forced me to build Guillotine before guillotine I was using ethereumjs as my evm implementation That plus performance was a 2nd reason I needed to build it
English
1
0
3
20
Sebastian Bürgel
Sebastian Bürgel@SCBuergel·
@FUCORY @samuellhuber Interesting, thanks for that. Suggestion: add this to your bio - it's hard to find here. IIRC there was some drama around the Ethereum JS team getting laid off from EF last year, is that the revival of those efforts or entirely separate?
English
1
0
2
26
fucory
fucory@FUCORY·
@sameandnot @agenticklabs Very cool! I'm building jjhub.tech to try to get this type of orchestration running in easy to manage containers in an alternative github. If we got similar interests might be an opportunity to collaborate
English
2
0
2
38
Ryan Lindgren
Ryan Lindgren@sameandnot·
@FUCORY @agenticklabs I did… Smithers likewise looks very cool! And I love the name. :) When I said “should have” what I really meant was “wish you had”! It’s exactly the kind of higher order system I built agentick to be able to support. I am using it to build github.com/agenticklabs/t… WIP
English
1
0
1
34
fucory
fucory@FUCORY·
@sameandnot @agenticklabs Looks cool! I think smithers is a bit of a higher level of abstraction than this. This looks useful for managing context windows at a low granular precise level and likely would work with smithers with minimal effort Did you build it?
English
1
0
0
43
fucory
fucory@FUCORY·
tevm.app is an abandoned project. A block explorer I built in 2 days using voltaire The Tevm universe is vast We got the original tevm: github.com/evmts/tevm-mon… We got voltaire: github.com/evmts/voltaire We got guillotine and guillotine-mini: github.com/evmts/guilloti… We got zevm (unreleased but likely next week) which includes light client consensus and lightweight way to sync and index There is also friends of tevm @trueblocks that has a powerful indexer I used in my prototypes of a local first fast syncing ethereum node
English
1
0
0
18
fucory
fucory@FUCORY·
@shazow Actually nvm only the people who bet on openclaw are rich
English
0
0
0
27
fucory
fucory@FUCORY·
@shazow My longing of electrobun 2 years ago and Effect.ts 4 years ago would have made me rich
English
2
0
1
39
fucory
fucory@FUCORY·
Understandable! I spent a lot of time playing with a builder pattern, Effect.ts, a python decorator pattern, and more and tried really hard to find any pattern better than JSX. They were all not a peak as JSX though The exception is TOON works great for simple scripts so we support that
fucory tweet media
English
0
0
1
30
dinos
dinos@din0s_·
@FUCORY sorry i just get PTSD looking at react syntax
English
1
0
1
9
fucory
fucory@FUCORY·
The key is to just constantly look out for repetitive things you can abstract. Start with things smaller than smithers. Maybe set up a postcommit hook to have an llm review the code. Maybe use bun to just create a super simple script or make some custom pi plugins. Abstract prompts you repeat a lot into reusable skills. As you climb that ladder of automation eventually the problems smithers solves will appear and why you should use it becomes obvious
English
1
0
1
27
caso
caso@casoxbt·
@FUCORY that said, i guess the next level would be - defining bigger (and/or more) tasks so i have to manually run less often the loop, and handling to agents - having a proper tasks system but still no idea how to make smithers fit here
English
1
0
1
25
fucory
fucory@FUCORY·
@kartojal Yes I've built this workflow using linear in past
English
0
0
1
24
kartojal
kartojal@kartojal·
@FUCORY can i use smithers to watch Jira tasks and proceed to plan the task, them work (code) on it in autopilot, test it, and review the output too?
English
1
0
1
18
powdr labs
powdr labs@powdr_labs·
Announcing powdr-wasm! powdr-wasm is an optimized zkVM for WASM, built on top of @openvm_org and the novel 𝑐𝑟𝑢𝑠ℎ ISA. Early benchmarks already show 1.5x fewer trace cells & faster proof times compared to RISC-V (OpenVM). It also supports Go guests via WASI! 👇
English
7
12
88
12.6K