End-to-End LLM Stack Trace: From Keystroke to Streamed Token
A software engineer has published a detailed technical document that traces exactly what happens at every layer of the stack when you send a prompt to an LLM like Claude or ChatGPT. Inspired by the classic "what-happens-when" repository for browser navigation, this document provides a production systems perspective on LLM chat interactions.
What the Document Covers
The document follows the full journey in production order:
- Client-side: Live token counting via WASM tokenizers, IME composition events, optimistic UI rendering
- Network: Why SSE wins over WebSockets for chat, UTF-8 boundary problem in streaming
- API Gateway: Edge TLS termination, multi-dimensional rate limiting (RPM vs ITPM vs OTPM)
- Safety classifiers: What runs before and after the model, why prompt injection is structurally unsolved
- Context assembly: What actually goes into the context window (it's not just your messages)
- Tokenization: Why models can't count letters, why leading spaces matter, how special tokens consume budget
- KV cache and prefix caching: GQA vs MHA memory math, PagedAttention, cache hit rate as a cost lever
- Prefill vs decode: Why they're bottlenecked differently (compute vs memory bandwidth)
- Sampling pipeline: The full logit pipeline in order — repetition penalty, temperature, top-k, top-p, softmax, sample
- Streaming: TTFT breakdown, SSE event parsing, incremental markdown rendering
- Tool use and agentic loops: Parallel tool calls, prompt injection resurfacing in tool results
- Billing and observability: TTFT vs TPOT, cache pricing math, what to instrument
Document Details
The document is aimed at engineers who already understand transformers and want to see how production systems actually work. It's released under CC0 license, and contributions are welcome. The author notes several uncovered subsystems at the bottom including speculative decoding, multimodal systems, and multi-agent coordination.
The repository was created to address the gap between high-level "transformers are magic" explanations and academic papers that don't connect concepts to production system behavior.
📖 Read the full source: r/LocalLLaMA
👀 See Also
Claude Code Workflow Visual Explains Memory Hierarchy and Skills System
A Reddit user shared a visual diagram showing Claude Code's workflow structure, including memory layering with CLAUDE.md files and reusable skills defined in .claude/skills/ directories. The workflow loop suggests using Plan mode, describing features, auto-accepting, and committing frequently.
How to Migrate OpenClaw and Hermes Between Machines Using SSH Self-Migration
A user transferred OpenClaw and Hermes from WSL2 Ubuntu on a laptop to an EVO-X2 WSL2 Ubuntu 2604 instance by having the tools SSH in and migrate themselves.
NemoClaw Windows Setup Issues and Fixes
NemoClaw installations on Windows fail with three specific errors: unsupported environment on Git Bash, port 18789 already in use, and Docker build failing on OpenClaw install. The root cause is that NemoClaw wasn't built with Windows in mind, requiring WSL2 Ubuntu for successful setup.
Contract Testing for AI-Driven Development with OpenClaw
Contract testing can replace integration/E2E tests when using AI agents like OpenClaw, focusing on interfaces and invariants between components. The AI generates code to satisfy deterministic contracts, creating a tight feedback loop for faster iteration.