* local development and speed are both important to me so I spend some effort ensuring our app can run fast locally both in a 'lightweight' mode with 'fakes' and in a slower/more accurate prod-like mode.
* We do enable agents to able to interact with the application locally via a browser and some app controls to enable testing certain scenarios but it's generally better to have them iterate by writing and running tests.
* I usually have about three agents going locally via codex/gemini CLIs in separate tabs using work-trees with an IDE to supervise and shepherd them along. Any more and I have trouble feeding them with work and supervising them. I also agree work-trees suck and sometimes I YOLO having agents collaborate on the same tree if I think it'll be less work.
* I use async web agents like codex but really only for paper-cut issues I'm reasonably confident the agent can one-shot or random experiments I'm curious about that I don't really intend to merge.
Right now it's mostly gemini/codex (sorry claude).
* We do enable agents to able to interact with the application locally via a browser and some app controls to enable testing certain scenarios but it's generally better to have them iterate by writing and running tests.
* I usually have about three agents going locally via codex/gemini CLIs in separate tabs using work-trees with an IDE to supervise and shepherd them along. Any more and I have trouble feeding them with work and supervising them. I also agree work-trees suck and sometimes I YOLO having agents collaborate on the same tree if I think it'll be less work.
* I use async web agents like codex but really only for paper-cut issues I'm reasonably confident the agent can one-shot or random experiments I'm curious about that I don't really intend to merge.
Right now it's mostly gemini/codex (sorry claude).