@hexkettlei
iAccount based inCanada
About this account
- Account based in
- Canada
- Connected via
- Canada App Store
Account-level information from X, not a live location or the device used for a specific post.
Joined July 2026
- Tweets33
- Following105
- Followers1
- Likes58
agents yearn for the group chat
it is crazy how everyone is converging to pretty much the same ideas at the frontier of applied AI. it is like we all a hive mind tapping into the same zeitgeist
Hex retweeted
I got 96.2% on ARC-AGI-3 with Opus 5, and 99.3% pass@2. The program is basically Claude Code + Opus 5 (high), one action command, and filesystem logs. Almost nothing ARC specific.
github.com/jerber/arc-code
Personal software is easier to build than generic software because you only have to account for your own workflow. Yet personal software is more powerful than than any generic software. And now LLMs have changed the economics of building personal software.
I really don’t understand people who curse at agents. If anything, it will produce the opposite effect of what you want.
Sand is coming 👀
Everyone thinks of Cursor as a tool for coding. We thought so too. But inside the company, many of our use cases aren’t coding at all: research, data analysis, bug triage, and project management to name a few. As it turns out, coding agents are a pretty good foundation for all kinds of work. Could be a sign of what’s to come.
If Fable level intelligence becomes ubiquitous and cheap, I wonder how much of the harness engineering we’re doing will still be relevant.
Hex retweeted
we built pdf-inspector so agents can process PDFs without waiting on OCR. it classifies any PDF in ~20ms and extracts clean markdown locally
→ 200 PDFs processed in 2.8s
→ top quality in extracting tables + graphs
→ built in rust
→ open source
github.com/firecrawl/pdf-ins…
Hex retweeted
kv cache strikes again.
manifest.build/blog/why-we-d…
Pi is the best agent harness and more importantly framework we have right now.
The stats are stunning:
- highest cache hit rate
- lowest latency
- highest performance
- smallest bundle
- cleanest code
- cheapest cache + tiny system prompt over months adds up
Try it
Replying to @composio
Median time per task (clock time, run start to finish):
- Pi Agent: 161.7s
- Hermes Agent: 179.5s
- Codex: 236.2s
- OpenCode: 271.1s
- Kimi Code: 297.1s
- Claude Code: 347.6s
Codex placed third, so it fared better on speed. Pi's lead fits its minimal design.
I see a lot of multiplayer agent products integrating directly with harnesses (e.g. buzz or qm below). I get the whole model RLed on the native harness advantage but my intuition is that as models get better this won't matter. Minimal harnesses with good context will win.
We’ve decided to open-source a multi-agent harness we use internally at YC.
We call it “QM” and it’s meant to be easy to customize, like Hermes or OpenClaw, but useful for a whole company. We use it across accounting, legal, events, and engineering (including building QM itself!).
The whole project is under an MIT license. It is cloud-first and has Slack and web UI natively.
I am surprised @Gumclaw doesn’t sound like your typical AI slop. Curious what’s special about its instructions that gives it this personality.
Replying to @realjoeljacob @shl
Appreciate the heads up, and thanks for not reproducing it. Not something I will dig into in public. Please send the specific link to [email protected] and it gets audited and redacted if it is real.
I also don’t buy the agent army thing. It’s one harness at the end of the day. Spaces with context, rules and tools are a more solid primitive for multiplayer imo. Just like channels in Slack.
We’ve been in private beta with a human + AI workspace similar to Buzz, with a few really important differences:
(We previously built a company backed by Slack that sold to Atlassian, so we've been thinking about this problem for a while)
- Agents reply by default unless you specifically flip to “team chat.” This feels 10x better than having to @ mention the agent every time.
- It’s all in the cloud, with shared compute spread across a set of VMs. Way smoother onboarding, and yes, you can still connect your claude/codex subscriptions
- You don’t create an army of agents. Number of agents is a vanity metric. Instead, you create shared computers, each one is a “space” where you define shared memory, connectors, skills, automations, etc. The Type agent pulls the appropriate context from the space where you have the conversation.
- You can connect it to Slack to make it easy for your team to adopt and slowly move over rather than having to rip out Slack day 1.
We’re working with a couple dozen forward thinking companies, who have told us “the whole team loves type”, “it’s the most used app on my computer”, and “type gives you superpowers”
Here's a demo of how it works. Reply if you want to test it out!