HIT-SCIR/Chinese-Mixtral-8x7B-adapter
Updated
•
1
Jack Pan
JackPan1024
AI & ML interests
None yet
Recent Activity
liked
a model
about 1 month ago
HIT-SCIR/Chinese-Mixtral-8x7B-adapter
liked
a dataset
about 1 month ago
Luobots/BlueMO
liked
a dataset
about 1 month ago
liushuaiqian/Chinese-High-School-Chemistry-Correction-Dataset
Organizations
None yet
liked
a
model
about 1 month ago
liked
2
datasets
about 1 month ago
liked
2
datasets
about 2 months ago
liked
a
Space
4 months ago
liked
3
datasets
4 months ago
upvoted
a
paper
5 months ago
liked
2
models
5 months ago
commented on
Welcome GPT OSS, the new open-source model family from OpenAI!
6 months ago
good
upvoted
an
article
6 months ago
Article
Welcome GPT OSS, the new open-source model family from OpenAI!
- +10
•
509
liked
5
models
6 months ago
xiaodongguaAIGC/xdg-llama-3-8B
Text Generation
•
8B
•
Updated
•
2
•
5
xiaodongguaAIGC/X-R1-3B
Text Generation
•
3B
•
Updated
•
2
•
2
apple/DiffuCoder-7B-Instruct
8B
•
Updated
•
985
•
60
OmniSVG/OmniSVG
Text Generation
•
Updated
•
237
•
188
moonshotai/Kimi-K2-Instruct
Text Generation
•
1T
•
Updated
•
133k
•
•
2.31k
reacted to
hesamation's
post with ❤️
6 months ago
Post
4150
longer context doesn't generate better responses. it can even hurt your llm/agent. 1M context window doesn't automatically make models smarter as it's not about the size; it's how you use it.
here are 4 types of context failure and why each one happens:
1. context poisoning: if hallucination finds its way into your context, the agent will rely on that false information to make its future moves. for example if the agent hallucinates about the "task description", all of its planning to solve the task would also be corrupt.
2. context distraction: when the context becomes too bloated, the model focuses too much on it rather than come up with novel ideas or to follow what it has learned during training. as Gemini 2.5 Pro technical report points out, as context grows significantly from 100K tokens, "the agent showed a tendency toward favoring repeating actions from its vast history rather than synthesizing novel plans".
3. context confusion: everyone lost it when MCPs became popular, it seemed like AGI was achieved. I suspected there is something wrong and there was: it's not just about providing tools, bloating the context with tool use derails the model from selecting the right one! even if you can fit all your tool metadata in the context, as their number grows, the model gets confused over which one to pick.
4. Context Clash: if you exchange conversation with a model step by step and provide information as you go along, chances are you get worse performance rather than providing all the useful information at once. one the model's context fills with wrong information, it's more difficult to guide it to embrace the right info. agents pull information from tools, documents, user queries, etc. and there is a chance that some of these information contradict each other, and it's not good new for agentic applications.
check this article by Drew Breunig for deeper read: https://www.dbreunig.com/2025/06/26/how-to-fix-your-context.html?ref=blog.langchain.com
here are 4 types of context failure and why each one happens:
1. context poisoning: if hallucination finds its way into your context, the agent will rely on that false information to make its future moves. for example if the agent hallucinates about the "task description", all of its planning to solve the task would also be corrupt.
2. context distraction: when the context becomes too bloated, the model focuses too much on it rather than come up with novel ideas or to follow what it has learned during training. as Gemini 2.5 Pro technical report points out, as context grows significantly from 100K tokens, "the agent showed a tendency toward favoring repeating actions from its vast history rather than synthesizing novel plans".
3. context confusion: everyone lost it when MCPs became popular, it seemed like AGI was achieved. I suspected there is something wrong and there was: it's not just about providing tools, bloating the context with tool use derails the model from selecting the right one! even if you can fit all your tool metadata in the context, as their number grows, the model gets confused over which one to pick.
4. Context Clash: if you exchange conversation with a model step by step and provide information as you go along, chances are you get worse performance rather than providing all the useful information at once. one the model's context fills with wrong information, it's more difficult to guide it to embrace the right info. agents pull information from tools, documents, user queries, etc. and there is a chance that some of these information contradict each other, and it's not good new for agentic applications.
check this article by Drew Breunig for deeper read: https://www.dbreunig.com/2025/06/26/how-to-fix-your-context.html?ref=blog.langchain.com
- 2 replies