Alejandro AO
Alejandro AO is a developer advocate at Hugging Face and an AI/software educator who publishes YouTube tutorials and articles about software development, machine learning, LLM applications, and Hugging Face tools.
Pi Durable Resumes Interrupted Agent Work From Persistent Checkpoints
Alejandro Ao describes Pi Durable as a harness for agent applications that need to recover task state after crashes or interruptions, not as a coding-agent CLI. It stores conversations and checkpoints so work can resume when the host process starts again, while leaving tool replay safety and process restarts to the surrounding application. In a tutorial, Ao walks through the harness setup and demonstrates recovery with a local model and SQLite.
Odysseus Separates the Agent Harness From the Model It Runs
PewDiePie’s Odysseus separates the agent application from the model it uses: the workspace coordinates tools and information, while Ajax, a fine-tuned Qwen 3.5 9B model, is intended to make tool-use decisions. In his breakdown, Alejandro AO argues that building a useful local agent depends not just on running software on your own machine, but on where the model runs and whether it can reliably use the harness’s tools. He explains how the agent loop works and why training on traces from the target setup may help a smaller model perform better.
AI Coding Agents Can Build Dashboards, but Analysts Must Define the Questions
Alejandro AO argues that AI coding agents can build a working business dashboard quickly, but that speed does not replace the analyst’s judgment. In a bank marketing example, he starts by defining what campaign managers need to learn, checks what the dataset can support, and specifies KPIs before asking an agent to build the interface. He then reviews and revises the charts, while cautioning that observed patterns do not establish what caused them—or what will improve the next campaign.
Pi Workspaces Turn Telegram Into a Gateway for Always-On AI Agents
Alejandro’s tutorial shows how to run specialized Pi assistants on an always-on machine and reach them through Telegram using his open-source `pi-gateway`. Each assistant runs from its own workspace, with its own instructions, tools and model; the gateway uses a local SQLite database to route messages to persistent Pi sessions. The demonstration covers a personal assistant and a research agent, while scheduled automations and support for other messaging platforms remain proposed extensions.
Pi Adds On-Device GGUF Models Through llama.cpp
Alejandro-ao shows how Pi can use GGUF models served locally through llama.cpp, keeping prompts, code and data on the user’s machine rather than sending them to third-party APIs. The setup depends on running a local llama.cpp server and choosing a quantized model that fits the available hardware; in his Apple M4 Max example, Hugging Face recommends Qwen 3.8-27B’s Q4_K_M variant. Pi’s `/llama` command then downloads and loads that model, making it available through the standard `/model` selector.
Agent Memory Requires Extraction, Separate Stores, and Hybrid Retrieval
Alejandro Ao argues that persistent memory for AI agents is not a longer chat history or a single vector database, but a write-and-retrieve pipeline that extracts durable claims, stores them alongside entity links and recent context, then ranks them for later use. In his walkthrough of Mem0, semantic search supplies the candidate set while BM25 and entity-based signals rerank it; that design makes the vector index the system’s gatekeeper. Ao’s practical case is that the architecture can run locally with small extraction models and open embedding models.
Stable Prompt Prefixes Cut Long AI Agent Input Costs
Alejandro AO argues that long-running AI agents become expensive because every turn reprocesses an expanding transcript, not just the latest user input. Prompt caching can sharply reduce that input bill by discounting previously processed prompt prefixes, he says, but only if an agent harness keeps system instructions and conversation history stable and append-only. Dynamic material placed early in a prompt, compaction, cache expiry and unenabled provider settings can all reset those savings.
Tau Ports Pi’s Coding-Agent Architecture to a Textual Terminal
Alejandro Ao presents Tau as a Python implementation of Pi’s coding-agent harness, built to preserve Pi’s parent-linked sessions, core tools, skills, and event design rather than introduce a different agent architecture. He argues that Tau’s main departure is its Textual terminal interface, which makes a run’s context, tool activity, resource provenance, branching history, and exports visible alongside the conversation.
Tau Exposes Coding-Agent Architecture Through Three Readable Python Layers
Alejandro Ao presents Tau, a small Python coding agent, as an educational reference rather than a competitor to established tools such as Pi or OpenCode. He argues that Tau’s value is legibility: its three-layer architecture separates provider-neutral model streaming, the reusable agent loop, and the coding-specific terminal environment so developers can see how tools, sessions, model calls, and UI behavior fit together. The project is meant to be read, modified, and extended as a way to understand how coding agents work.
Hermes Uses a Minimal Agent Loop to Preserve State Across Channels
Alejandro AO’s walkthrough of Hermes presents the agent as a deliberately small always-on system rather than a complex orchestration stack. He argues that Hermes’ usefulness comes from a simple loop that builds context from Markdown files, message history, tools, skills and memory, then preserves state through compression, SQLite transcripts, optional external memory providers, gateway integrations and scheduled cron jobs. The architecture’s central concern is continuity: keeping enough context across channels and time for the agent to behave like a persistent assistant.
FineWeb Shows LLM Dataset Quality Depends on Measured Web Filtering
Alejandro Ao’s overview of Hugging Face’s FineWeb argues that building a competitive LLM pretraining dataset from Common Crawl is a measurement-driven engineering process, not a matter of collecting more web text. He presents FineWeb as an open recipe in which Hugging Face chose raw HTML extraction over Common Crawl’s text extracts, found that global deduplication removed valuable data, and selected filters by training and evaluating small models. The same logic underpins FineWeb-Edu, where Llama-3-70B labels were distilled into a smaller classifier to filter the corpus for educational value at scale.