Video wird geladen...
Video konnte nicht geladen werden
I ported Vercel's fx coding agent to Windows 98 it talks to an LLM over a 56k modem and supports computer use (via MCP.exe) I now proudly run my own gamedev studio from 1999 my agents email each other in Outlook and store code on a network drive (git... show more
31,848 Aufrufe • vor 28 Tagen •via X (Twitter)
20 Kommentare

@vercel clippy was an agent the whole time. he was just 30 years early and nobody gave him tool access

💯 I highly recommend this 1999 paper from Microsoft Research where they were trying to build a model to predict if an "agent" needs to wait or intervene and make action. something like that is just one jev call today. sadly they didn't get to release it "Principles of Mixed-Initiative User Interfaces" by Eric Horvitz

@vercel ok this is going on the reading list. funny how in 99 the hard part was the model and now its mostly deciding when the agent should shut up

@vercel modem screech on every tool call would be elite

@vercel This looks so good 🤩

@vercel how long does one answer take over the modem? I'd want time to go make tea while the agent thinks

@vercel it's not that bad surprisingly! I had to speed up the video ofc, but text responses are ok. computer use was obviously much slower, for that I had to plug it into ethernet

@vercel Someone picking up the landline is the new rate limit 💀

@vercel does the 56k modem latency make the agent unusably slow, or is the model small enough that request/response still feels real-time?

@vercel The network drive was the shared context window all along.😂

@vercel minesweeper as the eval is perfect. what happens when the modem drops mid tool call, does it resume or redial and start over

@vercel A file checkout flag fits this setup: one agent owns an edit until it checks the file back in. Outlook can carry the handoff, while the network drive keeps two agents from overwriting each other’s work.

@vercel A bundle of X, Grok and Cursor in one Xpass is the rare leak where the pricing tiers are the product.

@vercel Wow!

@vercel the 56k modem is the part that'll actually kill you. tokens over dialup is a special kind of patience

@vercel Congrats on porting the fx coding agent to Windows 98. Love this, getting it to talk to an LLM over a 56k modem with computer use is great work.

@vercel a 56k modem is the right speed for waiting on an llm

@vercel this accidentally shows the whole architecture: a mailbox for messages, a network drive for state. multi-agent fleets in 2026 are still built from those two pieces — we just renamed them bus and object storage.

@vercel a 56k modem is an accidental stress test for the agent loop, anything that assumes fast round trips will show up immediately

@vercel Wow 😳

