I think we still skew back to an insanely high input token ratio when you consider agentic loops. For example, when I see the tools I use do a web fetch or a search or other tool use, it's an incredibly high number of new input tokens.
Speaking of which I remember Chris Barrie (who played Rimmer) lamenting some of the filming of Red Dwarf and how he struggled to and gave up on hanging out with Craig Charles (Lister) and Danny John-Jules (Cat) because he'd be tired and ready for bed and they'd just be getting started. And then they'd show up sometimes straight from the clubs to shooting the next morning, or sometimes drunk still, or hungover.
Craig Charles nicked my lighter in Oscar's nightclub in Plymouth in roughly 1991. I wouldn't have minded but it was my Dad's Zippo (RAOC, 7th/11th Armoured Brigade). He asked for a light, wandered off with it and then vanished, whilst I was distracted ahem.
I don't want to say Yes... but... given all of these tools are mostly built with JS and wrapped in a TUI we could probably go some way to having it run in the browser. There are fewer and fewer Node based APIs that haven't got a way to run in the browser.
It looks like co-do platform sandboxes the WASM tools, meaning you can't introduce a custom tool that allows pulling in remote data. How would you go about, say, adding custom mcp servers into a tool like you've created? Super interesting!
Author of the linked post here, years ago there was a thing called "Magic iframes" that would allow you to move an iframe between windows - like a Service Worker before ServiceWorkers. I was always amazed by some of the things you could do, but now it seems we forget about iframes :D
reply