which of the ide doesnt resent full chat again and again instead of only new messages

For an IDE/chat setup that avoids resending the full chat every time, VS Code with Copilot Chat is the closest mainstream option among common IDEs, because it keeps more conversational context in the workspace than simpler chat panels do. If you want the underlying API behavior, though, most systems are still stateless and must send prior context somehow, even if the app hides that from you.

What this means

• IDE chat UI: Some tools appear to “remember” the conversation and only continue from recent context, but they usually still manage history behind the scenes.

• API-based apps: They generally have to resend conversation context or store it externally, because the model itself does not retain memory between requests.

• Practical winner: If your goal is “don’t make me retype everything,” a chat assistant inside an IDE with history awareness is the best fit.

Best fit by use case

Use case| Better choice| Why
---|---|---
Coding in an editor with ongoing context| VS Code + Copilot Chat| More integrated chat history behavior 6.
Building your own assistant| Any IDE + your own conversation store| You control what gets sent each turn 410.
Wanting the model to automatically keep long context| Chat products with memory features| They manage context more smoothly for the user 8.

Bottom line

If you mean a normal coding IDE, VS Code with Copilot Chat is the most likely answer to your question. If you mean an app you’re building, no IDE alone solves it—the app must store context and send only what’s needed each turn.