Data framework for LLM apps · RAG · agents · workflows · verified against llama-index-core 0.14.x (2026)

LlamaIndex cheat sheet

LlamaIndex is the data framework for LLM apps: connect your data, index it, and query it in five lines. Load documents → VectorStoreIndexas_query_engine() is the classic RAG path. Configure models globally with Settings, swap in any of 300+ integration packages for LLMs / embeddings / vector stores, and build agents with FunctionAgent / AgentWorkflow on the event-driven Workflows runtime. Targets llama-index-core 0.14.x, Python 3.9+.

RAG core models & data indexing & retrieval agents & workflows storage / chat / ecosystem gotcha most common

Verified 2026-08-31 against the official docs at developers.llamaindex.ai (llama-index-core 0.14.x; latest 0.14.24). LlamaIndex is namespace-packaged: llama-index-core plus per-integration packages (llama-index-llms-*, -embeddings-*, -vector-stores-*).

Outline

The five-line RAG pipeline first; then how each piece (models, loaders, indexes, retrievers, agents, storage) is swappable.

Getting started

  1. 1Install & imports — packages
  2. 2RAG in five lines — load→index→query

Models & data

  1. 3Settings, LLMs & embeddings
  2. 4Loading data & documents

Indexing & retrieval

  1. 5Indexes
  2. 6Query engines
  3. 7Retrievers & postprocessors

Agents & workflows

  1. 8Function & ReAct agents
  2. 9Workflows (event-driven)

Storage, chat & ecosystem

  1. 10Persistence & vector stores
  2. 11Ingestion & chunking
  3. 12Chat engines
  4. 13Ecosystem & integrations

Getting Started

Install core plus a model package, then run the canonical retrieval-augmented pipeline.

1Install & importspip / packages
2RAG in five linesthe whole idea

Models & Data

Set models once, globally; connect to any data source with a reader.

3Settings, LLMs & embeddingsglobal config
4Loading data & documentsconnect sources

Indexing & Retrieval

Choose an index, expose it as a query engine, then tune retrieval and post-processing.

5Indexeshow data is organized
6Query enginesask questions
7Retrievers & postprocessorstune recall

Agents & Workflows

Give the LLM tools; orchestrate multi-step logic on the event-driven Workflows runtime.

8Function & ReAct agentstool-using LLMs
9Workflows (event-driven)orchestration

Storage, Chat & Ecosystem

Persist indexes, plug in a real vector DB, hold a conversation, and reach the wider ecosystem.

10Persistence & vector storesdon't re-embed
11Ingestion & chunkingnodes pipeline
12Chat enginesmulti-turn
13Ecosystem & integrationsthe wider stack

Worth memorizing

5-line RAGReader → VectorStoreIndex → as_query_engine
llama_index.corecore classes; providers in own packages
Settingsglobal .llm / .embed_model (was ServiceContext)
SimpleDirectoryReaderload a folder into Documents
from_documentschunk + embed + index in one call
similarity_top_khow many chunks to retrieve
response_modecompact / refine / tree_summarize
as_retrieverscored nodes only, no LLM
persist / loadStorageContext + load_index_from_storage
FunctionAgenttools + llm; await agent.run(...)
Workflows@step + events; agents run on them
LlamaHub300+ llama-index-* integration packages