"Select" tool not working as intended

As the project file grows and past conversations increase, when I want to make a change with the “Select” button in the prototyper area, it can break completely different places. Even if I ask it to never make a change anywhere else, even if I specifically identify the change it always makes and tell it not to make that change again, it can say ok and make that change again.

image

The purpose of the “Select” tool should be to make a specific and point change without changing anything else, without getting too hung up on past contexts. I think Gemini looks at past conversations and confuses itself a lot. It shouldn’t do that anyway, and I’m sure it’s being worked on to improve it, but the “Select” tool shouldn’t do that at all. The past context should be seriously reduced for this tool. There seems to be a need for improvement in this regard. @kirupa

This may not be specific to the “Select” tool. It’s related to context, a common problem for all models as projects go. There are a few links in this community forum on how others have reduced the size of the context window to get improved results.

1 Like

Yes, I have read them, but I think that for the “Select” tool the context should be automatically minimized by the system. Maybe the AI should decide that too. If you want to do something simple like minimize, maximize, move, margin/padding the selected object, the context can be automatically minimized to avoid unwanted results. If, for example, the selected object is a button and the button is intended to make changes elsewhere, the context may not be minimized. At least this approach makes the system a little better. We need to improve step by step and move towards a better point.

I hope that as the context grows, they can quickly reduce the problem of misunderstanding the context and confusing the AI. That would be the best of all, of course.

Have you tried to use /clear first?

Clear works to some extent, but past conversations are still recorded and Gemini evaluates them. It is possible to delete them, but it doesn’t always make sense.

Might be able to prompt it to list all pending tasks from prior prompts and context and then confirm if they have been resolved or not.

Have you tried this? Does it work? After doing this, have you experienced that it doesn’t interfere in unnecessary places again? I ask this because Gemini can sometimes make changes that were never even discussed before. Gemini can separate an input from a container. I think Gemini believes it will look better :man_shrugging:

/clear + reset context + .aiexclude = best case for getting Gemini back on track to do as you say.