🔥 Comprehensive survey on Context Engineering: from prompt engineering to production-grade AI systems. hundreds of papers, frameworks, and implementation guides for LLMs and AI agents.
3,311
84 commits
updated May 28, 2026
📄 Our comprehensive survey paper on Context Engineering is now published! Check out our latest academic insights and theoretical foundations.
A comprehensive survey and collection of resources on Context Engineering - the evolution from static prompting to dynamic, context-aware AI systems, and increasingly to agent runtimes, memory systems, protocols, coding agents, and observability stacks.
For questions, suggestions, or collaboration opportunities, please feel free to reach out:
Lingrui Mei
📧 Email: meilingrui25b@ict.ac.cn or meilingrui22@mails.ucas.ac.cn
I WROTE THE WRONG EMAIL ADDRESS IN THE FIRST VERSION OF MY PAPER!! You can also open an issue in this repository for general discussions and suggestions.
In the era of Large Language Models (LLMs), the limitations of static prompting have become increasingly apparent. Context Engineering represents the natural evolution to address LLM uncertainty and achieve production-grade AI deployment. Unlike traditional prompt engineering, context engineering encompasses the complete information payload provided to LLMs at inference time, including all structured informational components necessary for plausible task completion.
This repository serves as a comprehensive survey of context engineering techniques, methodologies, and applications.
As of March 2026, context engineering remains a useful and necessary concept, but it is no longer the whole story. The center of gravity has shifted from "how to pack the best prompt" to how agent systems manage runtime state, memory, tools, protocols, approvals, and long-horizon execution. In practice, context engineering now sits inside a broader stack that also includes agent harnesses, interoperability protocols, project memory for coding agents, and trace-first observability.
This repository still preserves its original survey structure on long context, RAG, memory, agent communication, tool use, evaluation, and applications. At the same time, this README is being reorganized to better reflect the agent era through additional coverage of:
Readers primarily interested in the 2026 shift should jump to the expanded sections on:
General AI Survey Papers
Context and Reasoning
Memory Systems and Context Persistence
Survey
Benchmarks
Production Memory Systems
Additional RAG and Retrieval Surveys
Context is not just the single prompt users send to an LLM. Context is the complete information payload provided to a LLM at inference time, encompassing all structured informational components that the model needs to plausibly accomplish a given task.
To formally define Context Engineering, we must first mathematically characterize the LLM generation process. Let us model an LLM as a probabilistic function:
$$P(\text{output} | \text{context}) = \prod_{t=1}^T P(\text{token}_t | \text{previous tokens}, \text{context})$$
Where:
In traditional prompt engineering, the context is treated as a simple string: $$\text{context} = \text{prompt}$$
However, in Context Engineering, we decompose the context into multiple structured components:
$$\text{context} = \text{Assemble}(\text{instructions}, \text{knowledge}, \text{tools}, \text{memory}, \text{state}, \text{query})$$
Where $\text{Assemble}$ is a context assembly function that orchestrates:
Context Engineering is formally defined as the optimization problem:
$$\text{Assemble}^* = \arg\max_{\text{Assemble}} \mathbb{E} [\text{Reward}(\text{LLM}(\text{context}), \text{target})]$$
Subject to constraints:
Where:
The context assembly can be decomposed as:
$$\text{context} = \text{Concat}(\text{Format}(\text{instructions}), \text{Format}(\text{knowledge}), \text{Format}(\text{tools}), \text{Format}(\text{memory}), \text{Format}(\text{query}))$$
Where $\text{Format}$ represents component-specific structuring, and $\text{Concat}$ assembles them respecting token limits and optimal positioning.
Context Engineering is therefore the discipline of designing and optimizing these assembly and formatting functions to maximize task performance.
From this formalization, we derive four fundamental principles:
System-Level Optimization: Context generation is a multi-objective optimization problem over assembly functions, not simple string manipulation.
Dynamic Adaptation: The context assembly function adapts to each $\text{query}$ and $\text{state}$ at inference time: $\text{Assemble}(\cdot | \text{query}, \text{state})$.
Information-Theoretic Optimality: The retrieval function maximizes relevant information: $\text{Retrieve} = \arg\max \text{Relevance}(\text{knowledge}, \text{query})$.
Structural Sensitivity: The formatting functions encode structure that aligns with LLM processing capabilities.
Context Engineering can be formalized within a Bayesian framework where the optimal context is inferred:
$$P(\text{context} | \text{query}, \text{history}, \text{world}) \propto P(\text{query} | \text{context}) \cdot P(\text{context} | \text{history}, \text{world})$$
Where:
The optimal context assembly becomes:
$$\text{context}^* = \arg\max_{\text{context}} P(\text{answer} | \text{query}, \text{context}) \cdot P(\text{context} | \text{query}, \text{history}, \text{world})$$
This Bayesian formulation enables:
| Dimension | Prompt Engineering | Context Engineering |
|---|---|---|
| Mathematical Model | $\text{context} = \text{prompt}$ (static) | $\text{context} = \text{Assemble}(...)$ (dynamic) |
| Optimization Target | $\arg\max_{\text{prompt}} P(\text{answer} \mid \text{query}, \text{prompt})$ | $\arg\max_{\text{Assemble}} \mathbb{E}[\text{Reward}(...)]$ |
| Complexity | $O(1)$ context assembly | $O(n)$ multi-component optimization |
| Information Theory | Fixed information content | Adaptive information maximization |
| State Management | Stateless function | Stateful with $\text{memory}(\text{history}, \text{query})$ |
| Scalability | Linear in prompt length | Sublinear through compression/filtering |
| Error Analysis | Manual prompt inspection | Systematic evaluation of assembly components |
The evolution from prompt engineering to context engineering represents a fundamental maturation in AI system design. As influential figures like Andrej Karpathy, Tobi Lutke, and Simon Willison have argued, the term "prompt engineering" has been diluted to mean simply "typing things into a chatbot," failing to capture the complexity required for industrial-strength LLM applications.
Single models alone cannot solve complex problems that require:
Static Knowledge Limitations:
Traditional prompting treats context as a static string, but enterprise applications require:
If prompt engineering is writing a single line of dialogue for an actor, context engineering is the entire process of building the set, designing lighting, providing detailed backstory, and directing the scene. The dialogue only achieves its intended impact because of the rich, carefully constructed environment surrounding it.
Most failures in modern agentic systems are no longer attributable to core model reasoning capabilities but are instead "context failures". The true engineering challenge lies not in what question to ask, but in ensuring the model has all necessary background, data, tools, and memory to answer meaningfully and reliably.
While prompt engineering suffices for simple, self-contained tasks, it breaks down when scaled to:
Enterprise applications demand:
Context Engineering enables:
Context Engineering provides the architectural foundation for managing state, integrating diverse data sources, and maintaining coherence across these demanding scenarios.
LLMs are essentially "brains in a vat" - powerful reasoning engines lacking connection to specific environments. Context Engineering provides:
Context Engineering addresses the fundamental challenge of information retrieval where the "user" is not human but an AI agent. This requires:
Context Engineering elevates AI development from a collection of "prompting tricks" to a rigorous discipline of systems architecture. It applies decades of knowledge in operating system design, memory management, and distributed systems to the unique challenges of LLM-based applications.
This discipline is foundational for unlocking the full potential of LLMs in production systems, enabling the transition from one-off text generation to autonomous agents and sophisticated AI copilots that can reliably operate in complex, dynamic environments.
Position Interpolation and Extension Techniques
Memory-Efficient Attention Mechanisms
Ultra-Long Sequence Processing (100K+ Tokens)
Comprehensive Extension Surveys and Methods
Audio-Visual Context Integration and Processing
Multi-Modal Prompt Engineering and Context Design
CVPR 2024 Vision-Language Advances
Video and Temporal Understanding
In the agent era, context engineering increasingly means runtime context management rather than only prompt construction. Production systems now rely on compaction, caching, artifact-backed state, and scoped instruction loading to keep long-horizon agents efficient and controllable.
Runtime Context Management Patterns
Context Optimization Engines
Production Design Questions
Knowledge Graph-Enhanced Language Models
Graph Neural Networks Combined with Language Models
Structured Data Integration
Foundational KG-LLM Integration Methods
Self-Supervised Context Generation and Augmentation
Reasoning Models That Generate Their Own Context
Iterative Context Refinement and Self-Improvement
Meta-Learning and Autonomous Context Evolution
Foundational Chain-of-Thought Research
In 2026, many of the most important advances in context engineering no longer live only inside the prompt. They live inside the agent harness: the runtime loop that manages plans, subagents, checkpoints, files, approvals, tool execution, and recovery from failure. This is where context engineering becomes agent engineering.
Harness and Runtime Design References
Core Runtime Concerns
survey
Naive RAG
Advanced RAG
Modular RAG
Graph-Based RAG
Agentic RAG
Real-Time and Streaming RAG
Modern memory systems are no longer a single retrieval store. Production agents increasingly separate:
Memory Design References
Coding agents have made project memory concrete. In practice, memory now often lives in artifacts such as repository instruction files, scoped rules, reusable skills, and long-lived project notes rather than only in vector stores.
Project Memory References
Persistent Memory Architecture
Memory Interchange Standards
Memory-Augmented Neural Networks
Episodic Memory and Context Persistence
Continual Learning and Memory Consolidation
Conversational Memory
Personalization and Memory
Safety and Alignment with Memory
Tool Integration and Memory
Learning and Reflection
Survey
Open protocols have become a major part of agent engineering. In practice, modern agent systems increasingly separate:
Official Protocol and Interoperability References
Agent Interoperability Protocols
Structured Communication Frameworks
LLM-Enhanced Agent Communication
The frontier of tool use has shifted from static function schemas to hosted tool runtimes, remote servers, and computer use interfaces. In the agent era, tools are increasingly connected through platform-managed execution, approval flows, and UI-aware control loops rather than single-shot JSON calls.
Official Tooling and Computer Use References
Foundational Tool Learning
Advanced Function Calling Systems
Multi-Agent Function Calling
Foundational Long-Context Benchmarks
Multimodal and Specialized Evaluation
RAG and Generation Evaluation
Synthetic vs. Realistic Evaluation
Long-running agent systems need more than offline benchmark scores. They require trace-level visibility into plans, tool calls, memory reads and writes, approvals, retries, and failure modes. Observability is increasingly the verification layer for context engineering in production.
Observability and Telemetry References
Hypothesis Generation and Data-Driven Discovery
Automated Scientific Discovery
AI for Science Integration and Future Directions
Deep Research Applications
Context Engineering as a Core Discipline
Enterprise AI Case Studies
Enterprise Applications and Infrastructure
Developer Tools with Context Engineering
Coding agents are one of the clearest production settings in which context engineering becomes agent engineering. Here, context is no longer just a prompt: it becomes repository instructions, project memory, task plans, file diffs, test results, and tool traces.
The production ecosystem is increasingly organized around full agent stacks rather than isolated models or prompts. These stacks combine tools, memory, runtime orchestration, sessions, observability, and interoperability in a single platform surface.
We welcome contributions to this survey! Please follow these guidelines:
<li><i><b>Paper Title</b></i>, Author et al., <a href="URL" target="_blank"><img src="https://img.shields.io/badge/SOURCE-YEAR.MM-COLOR" alt="SOURCE Badge"></a></li>
red for arXiv papersblue for conference/journal paperswhite for GitHub repositoriesyellow for HuggingFace resourcesThis project is licensed under the MIT License - see the LICENSE file for details.
If you find this survey helpful in your research, please consider citing:
@misc{mei2025surveycontextengineeringlarge,
title={A Survey of Context Engineering for Large Language Models},
author={Lingrui Mei and Jiayu Yao and Yuyao Ge and Yiwei Wang and Baolong Bi and Yujun Cai and Jiazhi Liu and Mingyu Li and Zhong-Zhi Li and Duzhen Zhang and Chenlin Zhou and Jiayi Mao and Tianze Xia and Jiafeng Guo and Shenghua Liu},
year={2025},
eprint={2507.13334},
archivePrefix={arXiv},
primaryClass={cs.CL},
url={https://arxiv.org/abs/2507.13334},
}
This project is ongoing and continuously evolving. While we strive for accuracy and completeness, there may be errors, omissions, or outdated information. We welcome corrections, suggestions, and contributions from the community. Please stay tuned for regular updates and improvements.
For questions, suggestions, or collaboration opportunities, please feel free to reach out:
Lingrui Mei
📧 Email: meilingrui22@mails.ucas.ac.cn
You can also open an issue in this repository for general discussions and suggestions.
This survey builds upon the foundational work of the AI research community. We thank all researchers contributing to the advancement of context engineering and large language models.
Star ⭐ this repository if you find it helpful!
A Survey of Context Engineering for Large Language Models
This comprehensive survey provides the latest academic insights and theoretical foundations for context engineering in large language models.
🔥 Comprehensive survey on Context Engineering: from prompt engineering to production-grade AI systems. hundreds of papers, frameworks, and implementation guides for LLMs and AI agents.
3,311
84 commits
updated May 28, 2026
📄 Our comprehensive survey paper on Context Engineering is now published! Check out our latest academic insights and theoretical foundations.
A comprehensive survey and collection of resources on Context Engineering - the evolution from static prompting to dynamic, context-aware AI systems, and increasingly to agent runtimes, memory systems, protocols, coding agents, and observability stacks.
For questions, suggestions, or collaboration opportunities, please feel free to reach out:
Lingrui Mei
📧 Email: meilingrui25b@ict.ac.cn or meilingrui22@mails.ucas.ac.cn
I WROTE THE WRONG EMAIL ADDRESS IN THE FIRST VERSION OF MY PAPER!! You can also open an issue in this repository for general discussions and suggestions.
In the era of Large Language Models (LLMs), the limitations of static prompting have become increasingly apparent. Context Engineering represents the natural evolution to address LLM uncertainty and achieve production-grade AI deployment. Unlike traditional prompt engineering, context engineering encompasses the complete information payload provided to LLMs at inference time, including all structured informational components necessary for plausible task completion.
This repository serves as a comprehensive survey of context engineering techniques, methodologies, and applications.
As of March 2026, context engineering remains a useful and necessary concept, but it is no longer the whole story. The center of gravity has shifted from "how to pack the best prompt" to how agent systems manage runtime state, memory, tools, protocols, approvals, and long-horizon execution. In practice, context engineering now sits inside a broader stack that also includes agent harnesses, interoperability protocols, project memory for coding agents, and trace-first observability.
This repository still preserves its original survey structure on long context, RAG, memory, agent communication, tool use, evaluation, and applications. At the same time, this README is being reorganized to better reflect the agent era through additional coverage of:
Readers primarily interested in the 2026 shift should jump to the expanded sections on:
General AI Survey Papers
Context and Reasoning
Memory Systems and Context Persistence
Survey
Benchmarks
Production Memory Systems
Additional RAG and Retrieval Surveys
Context is not just the single prompt users send to an LLM. Context is the complete information payload provided to a LLM at inference time, encompassing all structured informational components that the model needs to plausibly accomplish a given task.
To formally define Context Engineering, we must first mathematically characterize the LLM generation process. Let us model an LLM as a probabilistic function:
$$P(\text{output} | \text{context}) = \prod_{t=1}^T P(\text{token}_t | \text{previous tokens}, \text{context})$$
Where:
In traditional prompt engineering, the context is treated as a simple string: $$\text{context} = \text{prompt}$$
However, in Context Engineering, we decompose the context into multiple structured components:
$$\text{context} = \text{Assemble}(\text{instructions}, \text{knowledge}, \text{tools}, \text{memory}, \text{state}, \text{query})$$
Where $\text{Assemble}$ is a context assembly function that orchestrates:
Context Engineering is formally defined as the optimization problem:
$$\text{Assemble}^* = \arg\max_{\text{Assemble}} \mathbb{E} [\text{Reward}(\text{LLM}(\text{context}), \text{target})]$$
Subject to constraints:
Where:
The context assembly can be decomposed as:
$$\text{context} = \text{Concat}(\text{Format}(\text{instructions}), \text{Format}(\text{knowledge}), \text{Format}(\text{tools}), \text{Format}(\text{memory}), \text{Format}(\text{query}))$$
Where $\text{Format}$ represents component-specific structuring, and $\text{Concat}$ assembles them respecting token limits and optimal positioning.
Context Engineering is therefore the discipline of designing and optimizing these assembly and formatting functions to maximize task performance.
From this formalization, we derive four fundamental principles:
System-Level Optimization: Context generation is a multi-objective optimization problem over assembly functions, not simple string manipulation.
Dynamic Adaptation: The context assembly function adapts to each $\text{query}$ and $\text{state}$ at inference time: $\text{Assemble}(\cdot | \text{query}, \text{state})$.
Information-Theoretic Optimality: The retrieval function maximizes relevant information: $\text{Retrieve} = \arg\max \text{Relevance}(\text{knowledge}, \text{query})$.
Structural Sensitivity: The formatting functions encode structure that aligns with LLM processing capabilities.
Context Engineering can be formalized within a Bayesian framework where the optimal context is inferred:
$$P(\text{context} | \text{query}, \text{history}, \text{world}) \propto P(\text{query} | \text{context}) \cdot P(\text{context} | \text{history}, \text{world})$$
Where:
The optimal context assembly becomes:
$$\text{context}^* = \arg\max_{\text{context}} P(\text{answer} | \text{query}, \text{context}) \cdot P(\text{context} | \text{query}, \text{history}, \text{world})$$
This Bayesian formulation enables:
| Dimension | Prompt Engineering | Context Engineering |
|---|---|---|
| Mathematical Model | $\text{context} = \text{prompt}$ (static) | $\text{context} = \text{Assemble}(...)$ (dynamic) |
| Optimization Target | $\arg\max_{\text{prompt}} P(\text{answer} \mid \text{query}, \text{prompt})$ | $\arg\max_{\text{Assemble}} \mathbb{E}[\text{Reward}(...)]$ |
| Complexity | $O(1)$ context assembly | $O(n)$ multi-component optimization |
| Information Theory | Fixed information content | Adaptive information maximization |
| State Management | Stateless function | Stateful with $\text{memory}(\text{history}, \text{query})$ |
| Scalability | Linear in prompt length | Sublinear through compression/filtering |
| Error Analysis | Manual prompt inspection | Systematic evaluation of assembly components |
The evolution from prompt engineering to context engineering represents a fundamental maturation in AI system design. As influential figures like Andrej Karpathy, Tobi Lutke, and Simon Willison have argued, the term "prompt engineering" has been diluted to mean simply "typing things into a chatbot," failing to capture the complexity required for industrial-strength LLM applications.
Single models alone cannot solve complex problems that require:
Static Knowledge Limitations:
Traditional prompting treats context as a static string, but enterprise applications require:
If prompt engineering is writing a single line of dialogue for an actor, context engineering is the entire process of building the set, designing lighting, providing detailed backstory, and directing the scene. The dialogue only achieves its intended impact because of the rich, carefully constructed environment surrounding it.
Most failures in modern agentic systems are no longer attributable to core model reasoning capabilities but are instead "context failures". The true engineering challenge lies not in what question to ask, but in ensuring the model has all necessary background, data, tools, and memory to answer meaningfully and reliably.
While prompt engineering suffices for simple, self-contained tasks, it breaks down when scaled to:
Enterprise applications demand:
Context Engineering enables:
Context Engineering provides the architectural foundation for managing state, integrating diverse data sources, and maintaining coherence across these demanding scenarios.
LLMs are essentially "brains in a vat" - powerful reasoning engines lacking connection to specific environments. Context Engineering provides:
Context Engineering addresses the fundamental challenge of information retrieval where the "user" is not human but an AI agent. This requires:
Context Engineering elevates AI development from a collection of "prompting tricks" to a rigorous discipline of systems architecture. It applies decades of knowledge in operating system design, memory management, and distributed systems to the unique challenges of LLM-based applications.
This discipline is foundational for unlocking the full potential of LLMs in production systems, enabling the transition from one-off text generation to autonomous agents and sophisticated AI copilots that can reliably operate in complex, dynamic environments.
Position Interpolation and Extension Techniques
Memory-Efficient Attention Mechanisms
Ultra-Long Sequence Processing (100K+ Tokens)
Comprehensive Extension Surveys and Methods
Audio-Visual Context Integration and Processing
Multi-Modal Prompt Engineering and Context Design
CVPR 2024 Vision-Language Advances
Video and Temporal Understanding
In the agent era, context engineering increasingly means runtime context management rather than only prompt construction. Production systems now rely on compaction, caching, artifact-backed state, and scoped instruction loading to keep long-horizon agents efficient and controllable.
Runtime Context Management Patterns
Context Optimization Engines
Production Design Questions
Knowledge Graph-Enhanced Language Models
Graph Neural Networks Combined with Language Models
Structured Data Integration
Foundational KG-LLM Integration Methods
Self-Supervised Context Generation and Augmentation
Reasoning Models That Generate Their Own Context
Iterative Context Refinement and Self-Improvement
Meta-Learning and Autonomous Context Evolution
Foundational Chain-of-Thought Research
In 2026, many of the most important advances in context engineering no longer live only inside the prompt. They live inside the agent harness: the runtime loop that manages plans, subagents, checkpoints, files, approvals, tool execution, and recovery from failure. This is where context engineering becomes agent engineering.
Harness and Runtime Design References
Core Runtime Concerns
survey
Naive RAG
Advanced RAG
Modular RAG
Graph-Based RAG
Agentic RAG
Real-Time and Streaming RAG
Modern memory systems are no longer a single retrieval store. Production agents increasingly separate:
Memory Design References
Coding agents have made project memory concrete. In practice, memory now often lives in artifacts such as repository instruction files, scoped rules, reusable skills, and long-lived project notes rather than only in vector stores.
Project Memory References
Persistent Memory Architecture
Memory Interchange Standards
Memory-Augmented Neural Networks
Episodic Memory and Context Persistence
Continual Learning and Memory Consolidation
Conversational Memory
Personalization and Memory
Safety and Alignment with Memory
Tool Integration and Memory
Learning and Reflection
Survey
Open protocols have become a major part of agent engineering. In practice, modern agent systems increasingly separate:
Official Protocol and Interoperability References
Agent Interoperability Protocols
Structured Communication Frameworks
LLM-Enhanced Agent Communication
The frontier of tool use has shifted from static function schemas to hosted tool runtimes, remote servers, and computer use interfaces. In the agent era, tools are increasingly connected through platform-managed execution, approval flows, and UI-aware control loops rather than single-shot JSON calls.
Official Tooling and Computer Use References
Foundational Tool Learning
Advanced Function Calling Systems
Multi-Agent Function Calling
Foundational Long-Context Benchmarks
Multimodal and Specialized Evaluation
RAG and Generation Evaluation
Synthetic vs. Realistic Evaluation
Long-running agent systems need more than offline benchmark scores. They require trace-level visibility into plans, tool calls, memory reads and writes, approvals, retries, and failure modes. Observability is increasingly the verification layer for context engineering in production.
Observability and Telemetry References
Hypothesis Generation and Data-Driven Discovery
Automated Scientific Discovery
AI for Science Integration and Future Directions
Deep Research Applications
Context Engineering as a Core Discipline
Enterprise AI Case Studies
Enterprise Applications and Infrastructure
Developer Tools with Context Engineering
Coding agents are one of the clearest production settings in which context engineering becomes agent engineering. Here, context is no longer just a prompt: it becomes repository instructions, project memory, task plans, file diffs, test results, and tool traces.
The production ecosystem is increasingly organized around full agent stacks rather than isolated models or prompts. These stacks combine tools, memory, runtime orchestration, sessions, observability, and interoperability in a single platform surface.
We welcome contributions to this survey! Please follow these guidelines:
<li><i><b>Paper Title</b></i>, Author et al., <a href="URL" target="_blank"><img src="https://img.shields.io/badge/SOURCE-YEAR.MM-COLOR" alt="SOURCE Badge"></a></li>
red for arXiv papersblue for conference/journal paperswhite for GitHub repositoriesyellow for HuggingFace resourcesThis project is licensed under the MIT License - see the LICENSE file for details.
If you find this survey helpful in your research, please consider citing:
@misc{mei2025surveycontextengineeringlarge,
title={A Survey of Context Engineering for Large Language Models},
author={Lingrui Mei and Jiayu Yao and Yuyao Ge and Yiwei Wang and Baolong Bi and Yujun Cai and Jiazhi Liu and Mingyu Li and Zhong-Zhi Li and Duzhen Zhang and Chenlin Zhou and Jiayi Mao and Tianze Xia and Jiafeng Guo and Shenghua Liu},
year={2025},
eprint={2507.13334},
archivePrefix={arXiv},
primaryClass={cs.CL},
url={https://arxiv.org/abs/2507.13334},
}
This project is ongoing and continuously evolving. While we strive for accuracy and completeness, there may be errors, omissions, or outdated information. We welcome corrections, suggestions, and contributions from the community. Please stay tuned for regular updates and improvements.
For questions, suggestions, or collaboration opportunities, please feel free to reach out:
Lingrui Mei
📧 Email: meilingrui22@mails.ucas.ac.cn
You can also open an issue in this repository for general discussions and suggestions.
This survey builds upon the foundational work of the AI research community. We thank all researchers contributing to the advancement of context engineering and large language models.
Star ⭐ this repository if you find it helpful!
A Survey of Context Engineering for Large Language Models
This comprehensive survey provides the latest academic insights and theoretical foundations for context engineering in large language models.