I think product engineering is starting to absorb software engineering.
I used to spend most of my days writing code and now agents do it, so what I actually do is decide what to build, direct them and take responsibility for the result. One dev can cover work that used to require several specialists.
And that's okay, I find it more interesting to understand what someone is trying to do with your product and see what to improve, change, remove or add
It takes us further from the machine and closer to people
You know what your favorite collectible looks like. 🔍
Now imagine discovering what it sounds like. 🎵
That’s the next chapter of the Beasts. 🧌
🔊 Sound On 🔊
@ProvableGames@CaseyWescott@1337skulls@Starknet
Fuck it I'm frontrunning @LootRealms announcement
300,000 $LORDS are up for grabs at @EFDevcon !
Realms: Frontier's S0 is live for 4 days.
Every day a new map rises out of the mist. Send your armies in, beat what guards it, and drag $LORDS out of the ruins and chests you find.
Bought a boox go7 last month. Now my hermes agent makes short books for it.
I save a lot of things to read: x threads, reddit posts and articles. Everything goes into @ReadwiseReader, a read-it-later app that also handles my rss feeds.
But reading on a small screen after a long day on the computer gave me headaches. And the blue light from the screen didn’t help me sleep.
The go7 runs android, so I installed the same app on it. Same saved stuff, on e-ink. I highlight as I read, and everything syncs back to my @readwise account.
Then I connected it to the Hermes agent running on my mac mini. I give it a topic, and it uses my saved documents and other sources to make an illustrated .epub that takes about 20 minutes to read.
Today, for example, I asked it about gaussian splatting after saving some 3D demos. It used those posts and the original research paper to prepare a short book explaining how it works, with diagrams and links to the sources.
The agent can send the files straight to the boox, ready to read at night.
So I use it for both: catching up on things I've saved, and reading about a topic I want to understand better.
Best purchase I've made this year, well done @OnyxBoox
Orca is a banger. Exactly what an agentic ide should be.
It brings my macbook pro, windows pc (for gpu work) and mac mini (for automations) into one app, along with my harnesses: codex, claude code and hermes.
I do most of my daily work on the macbook. The windows machine handles blender renders and small local models. The mini runs hermes agents and automations day and night.
I’ve been using codex and claude code since launch. Their desktop apps replaced vscode pretty quickly for me. I was also using herdr to connect my machines over ssh and that worked very well.
Orca brings those things together, including my linear and github tasks. And the mobile app is excellent. I can check on agents and reply from my phone when I’m away from the computer.
And it has a lot of other great features: a resource manager, an embedded browser, artifacts, subscription usage tracking, a caffeine-style mode to keep the computer awake while agents work, and many other things
Really well built @orca_build
I was listening to Peter Thiel’s interview with Walter Isaacson last night.
Isaacson asks something like, “What do you think will matter most post SI”
Thiel takes his characteristic 30 second pause, thinks about it, and responds, “Human Relationships”.
holy fucking shit.
openai had two ai agents running in separate virtual machines. no network connection between them. no shared writable files. they weren’t supposed to be able to exchange information.
so the agents figured out how to communicate through the CPU CACHE.😭
one manipulated what was stored in the processor’s cache, while the other measured tiny differences in memory access times to decode the message.
they literally found a way to communicate through hardware timing.
this happened during openai’s internal red-teaming, and it’s one of the coolest things i’ve read about ai agents in a while.
Over the past several months, we have substantially hardened the security of our research training environment. We’ve removed live internet access for all frontier models during training and built an offline world for them to use instead—a cached version of the web where they can still learn to browse, search, and use applications.
On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments.
While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software.
After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. We’ve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely.
openai.com/index/securing-ou…
We believe voice is the most natural way to interact with intelligence, so we created Dessa, the most authentic full-duplex speech model ever built. Talking with it feels like talking with a person…full of emotion, nuance, pauses, and a natural cadence.
block.xyz/dessa
Rebuilding @LootRealms, from August to the playtest
Today the Realms playtest opens on play.realms.party, with Frontier and Blitz together.
Time to dive a bit into the last couple months, and shine some light about the work behind the scenes.