Rohit Malhotra

^ Agreed I'd prefer a fork button, which has the option to select either 1. summarize previous content 2. start fresh conversation with my current repo + branch - optionally...

This should be available in both the gitlab resolver and regular UI

FYI #7570 is adding similar support for Github, so the scaffolding changes may be quite similar

Hi @tdeckers, thanks a bunch for this! If you don't mind, could you provide a quick examples of resolver outputs with/without the changes on this PR?

I don't think I have the bandwidth to take this forward at the moment; if no one else can work on this I'll close the PR

I've updated this PR with solution suggested by @enyst; this allows for openhands-resolver to subscribe to events with a unique key See updated [resolver pr](https://github.com/All-Hands-AI/openhands-resolver/pull/237) for final implementation

> Then when we do, will we get duplicates in the `resolver`? Would that be a problem? Yup we would have duplicates; I'll close this PR in that case.

I'm not sure if I've interpreted this correctly, but from what I understand we want the following 1. Every agent controller handles their own callback 2. No duplicate events (parent...

I think it could also be helpful to store an ID attribute for every subscription? This way we manage subscribing and unsubscribing without worrying about the order in which the...

# Updates ## Change 1: Emitting to every subscriber instead of most recent subscriber Every subscriber now subscribes to events with a unique ID. An event type can have multiple...