MetaChip

Nice idea, @file, but it collides with other usage. Marking links as context in some way is highly desirable IMHO. If we can do this it would mean the requirement...

> > Nice idea, [@file](https://github.com/file), but it collides with other usage. > > With what usage does it collide? Presets, that I mentioned, or something else also? Yes, presets, but...

> To be clear, I think the issues we're discussing in https://github.com/karthink/gptel/issues/481 and https://github.com/karthink/gptel/issues/475 are mostly about the UI and orthogonal to this feature. Agreed. > In the time it'll...

Thanks for the reference to this issue @karthink, hcere's my thoughts on the questions you posed to @orge-dev I have two suggestions. **Multiple Context Buffers** I agree the concept here...

> This proposal for multiple context buffers is going to be confusing to most users. I would prefer gptel-add and co to be a one-shot interaction -- every additional decision...

> I also think you are underestimating the amount of confusion an opaque many-to-one associative map from buffers to context sets will cause when using gptel. Fair enough. I think...

@ultronozm Very interesting. The UI you have created to add all sorts of context types looks great. I'll give it a go. What follows are my initial thoughts in light...

I forgot to add. I think context should include more than just references to regions, files and media. It should also include what GPTEL already manages; the selected model, the...

@karthink The core issue seems to be that overlays, while excellent for visual feedback, create constraints when managing multiple contexts because they exist in the buffer space, not context space....

Looking back through this thread, I think @dwrz and @nlevnaut's suggestions point to the simplest workable solution, with an additional refinement for persistence: 1) Keep the current single-context mechanism exactly...