Addy Osmani introduces Loop Engineering, a shift from writing prompts for coding agents to building autonomous loops composed of automations, worktrees, skills, plugins, sub‑agents, and state, while highlighting benefits, trade‑offs, and the new leverage point for engineers.
This tutorial walks through Claude Code’s built‑in slash commands, explaining each command’s purpose, when to use it, and providing concrete examples and demo prompts so developers can manage sessions, control context, run background tasks, and streamline AI‑assisted coding efficiently.
DeepSeek‑TUI is an open‑source terminal coding agent that combines DeepSeek model capabilities with a conversational tool‑calling interface, offering multi‑step file edits, shell and git operations, cost‑aware auto mode, and risk‑engineered workflows for engineers who need traceable, multi‑turn AI assistance.
The article explains how Gemini CLI’s Auto mode intelligently switches between the Pro and Flash models, why manually locking the Pro model does not cause extra quota consumption, presents benchmark comparisons, clarifies the meaning of the quota indicator, and offers practical model‑selection guidance.
The article explains why the reliability of long‑task agents now hinges on harness design rather than model strength, and details four harness innovations—programmatic tool calls, sub‑agents as isolation boundaries, context compression, and skill‑search priority—that Glean uses to build a distributed context management system.
Long Claude Code sessions quickly become noisy as every grep, find, and ls call stays in the main context, but using sub‑agents—including the built‑in Explore and Plan agents and the CLAUDE_CODE_FORK_SUBAGENT flag—isolates work, returns only concise summaries, and lets you monitor activity with a context‑timeline hook.
The article examines why raw LLM models fail as autonomous coding agents and introduces Harness Engineering—a disciplined scaffold of prompts, tools, context policies, hooks, and sub‑agents—that mitigates context corruption, long‑task collapse, and security risks while cutting token costs by up to 50%.
This guide explains why massive token windows can cause context rot in Claude Code, demonstrates how to monitor usage, and walks through the /rewind, /clear, and /compact commands plus sub‑agent techniques to keep the model’s context clean and efficient.
Claude Code, Anthropic's CLI AI programming assistant, offers six extensible mechanisms—Skills, MCP, Sub‑agents, Agent Teams, Hooks, and Plugins—each explained with purpose, setup steps, concrete examples, and practical guidance on when and how to combine them for robust AI‑driven workflows.
This guide explains why most users only tap into 20% of Claude Code’s capabilities, then details five core practices—including a project‑level CLAUDE.md file, a four‑step Explore‑Plan‑Code‑Commit workflow, the Think tool, sub‑agent architecture, and MCP integration—that together reduce error rates by 40%, cut rework by 60%, and accelerate development by up to 30%.
This article analyzes Claude Code's Sub‑agents and Agent Teams, comparing their architectures, use‑cases, and constraints, and provides practical guidelines, code examples, and design patterns to help developers decide which multi‑agent model best fits their tasks.
The article explains that the Xiaolongxie AI agent excels at workflow‑type tasks—those with clear steps, ongoing monitoring, defined inputs and outputs, and repeatable labor savings—and lists five concrete scenarios (web‑page inspection, data structuring, chat‑based assistants, scheduled monitoring, and multi‑step task decomposition) while also outlining its three core capabilities (browser automation, heartbeat scheduling, and sub‑agents) and advising a gradual adoption roadmap.
This comprehensive guide walks you through OpenClaw's five advanced modules—identity system, persistent memory, Skills, sub‑agents, and cron jobs—showing how to configure each with concrete file examples, JSON settings, and CLI commands so your AI assistant gains personality, long‑term recall, extensible capabilities, parallel processing, and automated workflows.
The article presents ten actionable Claude Code techniques—including context‑window management, self‑validation prompts, planning mode, CLAUDE.md rules, parallel sessions, raw‑data bug fixes, sub‑agents, custom skills, prompt tricks, and context clearing—to help developers use the AI coding assistant efficiently and reliably.
This guide translates and refines the Claude Code founder’s ten practical usage tips, covering parallel worktree sessions, plan‑mode workflows, CLAUDE.md maintenance, custom skills, automated bug fixing, prompt strategies, terminal setup, sub‑agents, data analysis, and learning techniques to help developers get the most out of the AI coding assistant.
This guide explains why a single generic prompt for Claude Code often fails, introduces the concept of sub‑agents that assign focused roles to the AI, and provides ten practical sub‑agent templates covering refactoring, bug fixing, testing, API review, security, documentation, performance, product thinking, code review, and architecture decisions.
The article surveys emerging 2025 agent architecture patterns—including giving agents a computer, multi‑layer action spaces, progressive disclosure, context offloading, caching, sub‑agent isolation, evolving context, and multi‑agent coordination—backed by citations from Meta, Anthropic, and open‑source projects.
After a changelog‑induced bug forced an emergency rollback of Claude Code 2.1.0, Anthropic quickly released version 2.1.1, introducing automatic skill hot‑reload, forked sub‑agent contexts, expanded Vim support, lifecycle hooks, remote‑dev commands, and a suite of bug fixes.
