axldelafosse

4 ms·

1.
by axldelafosse 2mo ago
Wow that's really cool! Nice work
2.
by axldelafosse 6mo ago
The feedback loop is faster. But PR reviews are still useful as they are multiplayer (meaning that you and another human reviewer can talk about a specific agent's comment directly on the diff, which is very useful sometimes).
3.
by axldelafosse 6mo ago
They don't. And you would be surprised how a good model actually pushes back on some comments. The point was: when they do agree, it is a very strong signal.
4.
by axldelafosse 6mo ago
Yes, but what’s cool about loop is that it runs the interactive TUIs and establishes a direct connection between them. You can steer and answer questions in both sessions, not just from the main worker.
5.
by axldelafosse 6mo ago
Cool! Thank you.
6.
by axldelafosse 6mo ago
I’m glad someone is finally bringing this up, thank you! What are you suggesting instead? To share the prompt in order to capture the intent? Usually I expect the plan to reflect the prompt. I find it interesting when I create a PR after a
7.
by axldelafosse 6mo ago
Yeah maybe! Right now I find it useful to use different agent harnesses but as the models get better (and the agent harnesses simpler), it might be possible to get the same result with the same model. Would be cool to experiment with open-s
8.
by axldelafosse 6mo ago
Yes exactly. I’m talking about this in the article. I found out that when Claude and Codex both review the same PR and both find the same issue, our team fixes it 100% of the time.
9.
by axldelafosse 6mo ago
Interesting! Feels like a good way to write docs/memories. What I like about loop is that it runs the interactive TUIs so you can answer questions in both sessions (not just the main worker). It is not human multiplayer though (but tha
10.
by axldelafosse 6mo ago
Yes, the goal is the same. This plugin is similar to the Codex gstack skill. What makes loop different is that it lets Claude and Codex talk to each other directly (receiving messages from Claude via the Codex App Server and from Codex via
11.
by axldelafosse 6mo ago
It doesn’t mean that they are always out of scope, rather than the reviewer can be nitpicking (like humans do) and instead of addressing the comment in a follow-up PR, the change gets addressed in the same PR. So not necessarily out of scop
12.
by axldelafosse 6mo ago
I created the first version of loop after getting tired of doing this manually!
13.
by axldelafosse 6mo ago
Good reminder: don't forget the plan review!
14.
by axldelafosse 6mo ago
Oh, that's cool!
15.
by axldelafosse 6mo ago
I agree! Right now it is leveraging the Codex App Server, which is open-source and very well implemented, but using Claude Code Channels is probably a bit hacky. The good thing is that it establishes a direct connection so it's already
16.
Agent-to-agent pair programming(axeldelafosse.com)
135 points by axldelafosse 6mo ago|60 comments
17.
by axldelafosse 2y ago
Happy to help! I have a small home studio. But I'm also really impressed by my AirPods with personalized Spatial Audio and head tracking enabled -- so I'm using them when I'm on the move. The funny thing is that I own a pair
18.
Show HN: I spent days curating concert films in Spatial Audio (Dolby Atmos/5.1)(sweetspot.stream)
3 points by axldelafosse 2y ago|2 comments
19.
by axldelafosse 3y ago
Location: Paris, France Remote: Yes Willing to relocate: Yes, SF or NY Technologies: React (+ Next.js), React Native (+ Expo), Node.js (+ NestJS), TypeScript, GraphQL (+ Hasura), SQL (+ PostgreSQL) Résumé/CV: https://x.com&#
20.
by axldelafosse 5y ago
Location: Paris, France Remote: Yes Willing to relocate: Yes Technologies: React (+ Next.js), React Native (+ Expo), Node.js (+ Nest.js), TypeScript, GraphQL (+ Hasura), PostgreSQL, AWS, Vercel, and more Résumé: https://drive.go