Devxcoder Unpacked

What actually happens when you type a message into Claude Code? The agent loop, tools, multi-agent orchestration, and unreleased features, mapped straight from the source.

Ask DeepWiki Featured on Hacker News 8,218 Contributions
1,900+
Files
519K+
Lines of Code
50+
Tools
95+
Commands
8,218
Contributions
8,218 contributions in the last year
MonWedFri
Less More
Start exploring

The Agent Loop

From keypress to rendered response, step by step through the source.

1Input 2Message 3History 4System 5API 6Tokens 7Tools? 8Loop 9Render 10Hooks 11Await

Watch what happens when you send a message to Claude Code

1 User Input
src/components/TextInput.tsx
User types a message or pipes input through stdin
claude-code
$ Find all TODO comments in src/ and create a summary
Keyboard input comes from Ink's TextInput component. In non-interactive mode, it reads from piped stdin instead.
111

Keyboard: ← → arrow keys to step through · Space to play/pause

Architecture Explorer

Click any block to explore what's inside each directory.

Tools & Commands
Core Processing
UI Layer
Infrastructure
Support & Utilities
Personality & UX
utils/564 files components/389 files commands/189 files tools/184 files services/130 files hooks/104 files ink/96 files bridge/31 files constants/21 files skills/20 files cli/

Scroll horizontally to explore

↖ Click any block to explore a directory
files

Tool System

Every tool Claude Code can call, sorted by category. Click a tool to see details.

Click any tool to see details and source

Command Catalog

Every slash command extracted from the source, by category.

Click a command to see details and source code

Hidden Features

Stuff that's in the code but not shipped yet. Feature-flagged, env-gated, or just commented out.

Click a feature to explore