Twitxy Saved

Felipe Arce

Verified account This account is verified. Learn more

@astherath

lead swe @ExowattEnergy ☀️ building agents that run on sunlight. ex-microsoft, fiu cs. miami. will talk about coding agents for free
Miami, FL felipearce.dev Joined November 2025
66 Following 4 Followers 13 Posts

Latest posts 4

Pinned post

Felipe Arce Verified account @astherath
Stoked that this is finally here! I can finally talk about some of the super cool infra we're doing at @ExowattEnergy!!

You can find my first post about Roadrunner, our alternative to Github Actions that cut down on cost and improved ci/cd time here:
whitepapers.exowatt.com/papers/roadrun…
whitepapers.exowatt.com Moving 199 repos off GitHub Actions in eight days — Exowatt Research After a three-hour GitHub Actions outage, we built Roadrunner, a self-hosted Woodpecker and Dagger deploy lane. Eight days later it was the default deploy path for 199 repos, with GitHub Actions kept...
Exowatt @ExowattEnergy 2d
Our software team has been doing amazing work this year

Physical AI is at the core of what we do, and the tools we built for it are too good to keep to ourselves

So today we're launching Broad Daylight, our new open source initiative. Read about it here:
whitepapers.exowatt.com/broad-daylight
View quoted post on X
Felipe Arce Verified account @astherath
Agreed for research work, but narrow goes further than people think. We fine-tuned a 14B on one of our tasks and it beat Opus 4.7, 0.975 to 0.625 F1, at about 1/49th the cost. A 1.7B running on a CPU at our site beat Sonnet 4.6 too
Allan Verified account @AllanatrixQ 2d
I’ve been super pro open-source models and all, but honestly, the frontier models still beat the open ones in quality. I’ve tried dozens of other models and fine-tuned them and post-trained the crap out of them, but for the kind of work I do and the heavy research infrastructure and ML work, frontier models still win. The open models are great for narrow tasks that don’t require too much open-ended reasoning, but not so much large-context tasks, and multi-step and branching work; otherwise, open models are sufficient.
View quoted post on X
Felipe Arce Verified account @astherath
One worktree per agent, and every agent claims the files it's about to touch on a shared board before editing.

We learned it the hard way yesterday - 13 agents on one shared checkout, and one ran git reset --hard over another agent's unpushed commit.

Of the 4,732 collisions that board has flagged, 3,797 were one person's own agents running into each other. The call is coming from inside the house

whitepapers.exowatt.com/papers/feads/
whitepapers.exowatt.com Feads, a work board for agents that people read — Exowatt Research We turned beads, an open-source issue tracker for coding agents, into Feads: one hosted board where nine people's agents claim work, declare the files they touch and @mention each other. Since July...
Logic Verified account @code0e 2d
For developers using Claude Code and Codex together, how do you prevent both agents from making conflicting changes?

Do you assign separate tasks, use different Git branches or give each agent its own worktree?

What’s actually working?
View quoted post on X