@haukebri your comment is flagged as dead so replying here.
> Do you keep a fresh context per agent?
Yes I've run into the same problem of trying to stuff too much into one session. So Delegator uses a fresh session for each task. For larger workflows, I'll do the same where I'll have a design or feature doc and then the tickets may refer to that if necessary for additional context.
> The part that eats my time isn't the delegation, it's the review. I trust an agent now on mechanical work with a crisp "done" definition, and a lot less where the acceptance criteria are fuzzy, so those tickets tend to take me longer than doing them myself.
> Between the queue and your review, where do you actually get bottlenecked? That's my constraint right now.
Yes, I'm bottlenecked on the review. I think everyone has this problem now. I'm trying to solve that by bringing the task into a ticket system so you can easily look up what it was trying to do. From some research I did, context switching isn't so bad if you are presented with the context clearly and succinctly when coming back to the task. I'll admit I don't think I have a perfect solution for this yet but I'm trying to work towards that. I do think this is the biggest issue with AI-assisted development - reviewing the code and output. What have you tried that's been working?
@haukebri your comment is flagged as dead so replying here.
> Do you keep a fresh context per agent?
Yes I've run into the same problem of trying to stuff too much into one session. So Delegator uses a fresh session for each task. For larger workflows, I'll do the same where I'll have a design or feature doc and then the tickets may refer to that if necessary for additional context.
> The part that eats my time isn't the delegation, it's the review. I trust an agent now on mechanical work with a crisp "done" definition, and a lot less where the acceptance criteria are fuzzy, so those tickets tend to take me longer than doing them myself. > Between the queue and your review, where do you actually get bottlenecked? That's my constraint right now.
Yes, I'm bottlenecked on the review. I think everyone has this problem now. I'm trying to solve that by bringing the task into a ticket system so you can easily look up what it was trying to do. From some research I did, context switching isn't so bad if you are presented with the context clearly and succinctly when coming back to the task. I'll admit I don't think I have a perfect solution for this yet but I'm trying to work towards that. I do think this is the biggest issue with AI-assisted development - reviewing the code and output. What have you tried that's been working?
[flagged]