← Back to context

Comment by mrmansano

6 days ago

> I'm just starting to use Codex Web for asynchronous agents because I have a friend who swears by queueing up a dozen async prompts every morning and sifting through them in the afternoon

Bunch of async prompts for the same task? Or are you parallelizing solving different issues and just reviewing in the afternoon?

Sounds intriguing either way.

I _think_ I’m the friend being referenced. I’m parallelizing solving different issues. Basically I keep an internal swim lane of a variety of projects and just kick off the next task in the lane I think the agent can handle.

Then I do my “real” work, there’s the stuff I don’t trust the agent with, or is more exploratory or whatever.

As I think of more agent tasks doing that I write them down. When I take a break, say for lunch or winding down at the end of the day I check back in on previous tasks and fire off the new ones.

My flow is very similar to what I did with junior eng except I’m willing to fire off even more trivial tasks at the agent because I don’t care if it sits idle. Similarly if it gets way off base I’m happy to kill the pr more aggressively and start over, what do I care if it wasted its time or if it learns a valuable lesson from the experience?