Local coding

Component map (what you need)

Local coding is five layers. Missing any required layer = “nothing works.” Optional RAG only if you need repo retrieval beyond the model context.

  1. 1

    1. IDE / Agent client

    Extensões VS Code / Cursor (Continue, Cline), plugins JetBrains (Continue e semelhantes) e CLI como Aider. Todos contra um endpoint local compatível com OpenAI.

    O anfitrião é o IDE ou o terminal; o plugin não é o modelo. Repos em Agent / Toolchain.

  2. 2 Optional

    2. RAG / repo index

    A maioria dos clientes traz índice (codebase Continue/Cline, repo map do Aider). Camada à parte: AnythingLLM, RAGFlow ou LlamaIndex; stores Chroma, Qdrant ou FAISS; embeddings no local.

    Salte se basta complete de contexto curto; quase obrigatório com modelo pequeno e monorepo grande. Não é o runtime de inferência.

  3. 3

    3. Local runtime (OpenAI-compatible server)

    Ollama, llama.cpp server, MLX, vLLM, or SGLang—exposes localhost chat/completions.

    This is the “stack” decision on this page. Community stars below measure popularity of this layer.

  4. 4

    4. Model weights on disk

    GGUF / MLX / safetensors from the Models allowlist—size locks your hardware band.

    API-only MoE coders never land here.

  5. 5

    5. Hardware (VRAM / unified memory)

    NVIDIA CUDA, Apple unified + Metal/MLX, or limited AMD/Intel paths—see Hardware.

    Weights fit ≠ context fit (KV tax).

Quick “what am I missing?”

  • Have an IDE but no localhost runtime → install Ollama / llama.cpp / MLX first.
  • Runtime up but empty models → download an allowlisted coder GGUF (Models page).
  • Model loads but agent is blind in a big repo → add RAG / repo index (optional layer).
  • OOM or tiny context → Hardware band is wrong, or KV budget is too high.

Decision tree

Desktop NVIDIA

Ollama to start → llama.cpp when you need exact quants and context → vLLM / SGLang only on a dedicated machine.

Apple Silicon

Prefer MLX for native unified memory. Use llama.cpp or Ollama when you need cross-platform GGUF workflows.

IDE wiring

Aponte uma extensão VS Code / Cursor (Continue, Cline), um plugin JetBrains (Continue ou similar) ou o Aider para localhost. Repos abertos em Agent / Toolchain — esta página não inventa um segundo ranking.

Agente · Cadeia

Community signal — runtime popularity (GitHub OSS)

Stars from Trends segments inference / serving / llm_lib. This is popularity of layer 3 (local runtime)—not SWE skill, not IDE quality, not model quality.

Use it to sanity-check “is this runtime still alive?”, not to pick a coding model.

Repository Trends segment Stars
ggml-org/llama.cpp inference 124,446
earendil-works/pi inference 92,672
BerriAI/litellm inference 56,603
sgl-project/sglang inference 31,995
microsoft/onnxruntime inference 21,399
huggingface/transformers llm_lib 164,211
fighting41love/funNLP llm_lib 82,521
unslothai/unsloth llm_lib 73,350
ComposioHQ/awesome-claude-skills llm_lib 72,700
labmlai/annotated_deep_learning_paper_implementations llm_lib 67,312
open-webui/open-webui serving 149,090
Mintplex-Labs/anything-llm serving 64,859
janhq/jan serving 44,038
lm-sys/FastChat serving 39,513
chatchat-space/Langchain-Chatchat serving 38,546

← Local coding hub

Assumptions and sources

Hardware bands are classes, not street quotes. VRAM estimates use curated GGUF footprints plus size-class KV factors. API job cost uses OpenRouter primary listing when present. choose-ai-infrastructure-guide covers API hosts—not desk GPUs.