AI Agent Terminology | Rookie TutorialWith the rapid development of Large Language Models (LLMs) and Agent technologies, programming paradigms are undergoing a profound transformation. New concepts and terms are emerging constantlyβVibe Coding, Agentic Coding, Harness Engineer, Loop Engineer... Let's take a look at what these new terms mean and what they represent.
\\n\\n
AI Agent is composed of Artificial Intelligence and Agent.
\\n\\n
![Image 1]()
\\n\\n
I. Coding Paradigm
\\n\\n
\\n\\n\\n| Term | \\nChinese | \\nCore Meaning | \\nExample (Restaurant Business) | \\n
\\n\\n\\n\\n| Vibe Coding | \\nVibe Programming | \\nUsing natural language/voice to describe requirements and let AI generate code | \\nCooking fried rice at home based on intuition, adding whatever you feel like | \\n
\\n\\n| Context Engineering | \\nContext Engineering | \\nImproving model performance by organizing context, knowledge, memory, and tools | \\nPreparing ingredients in advance, creating menus, and setting up the kitchen environment | \\n
\\n\\n| Agentic Coding | \\nIntelligent AgentProgramming | \\nAgent autonomously completes programming tasks (design β implementation β testing β acceptance) | \\nRunning a formal restaurant, from menu planning, preparation to final serving | \\n
\\n\\n| AI Native Development | \\nAI Native Development | \\nAI participation in design, development, and testing by default | \\nDirectly operating a smart restaurant | \\n
\\n\\n
\\n\\n
II. Engineer Role
\\n\\n
\\n\\n\\n| Term | \\nChinese | \\nCore Meaning | \\nExample (Restaurant Business) | \\n
\\n\\n\\n\\n| Harness Engineer | \\nHarness Engineer | \\nCan call various Harness components, doing work and self-verification | \\nProfessional chef, proficient in various cooking techniques and tools, tasting and checking own dishes | \\n
\\n\\n| Loop Engineer | \\nLoop Engineer | \\nBuilding automated orchestration systems for autonomous evolution | \\nRestaurant operations management system, coordinating scheduling, procurement, serving rhythm, and costs | \\n
\\n\\n| Context Engineer | \\nContext EngineeringEngineer | \\nResponsible for designing context, knowledge sources, and memory systems | \\nHead kitchen coordinator | \\n
\\n\\n| AI Product Engineer | \\nAI Product Engineer | \\nResponsible for AI capability and business closed-loop design | \\nRestaurant owner and operator | \\n
\\n\\n| Agent Operator | \\nIntelligent AgentOperations Engineer | \\nContinuously monitoring and optimizing Agent execution performance | \\nStore manager continuously optimizing business data | \\n
\\n\\n
\\n\\n
III. Model & Fundamentals
\\n\\n
\\n\\n\\n| Term | \\nChinese | \\nCore Meaning | \\nNotes | \\n
\\n\\n\\n\\n| LLM (Large Language Model) | \\nLarge Language Model | \\nLanguage prediction model trained on massive text data | \\nGPT, Claude, Gemini are all LLMs | \\n
\\n\\n| GPT | \\nGenerative Pre-trained Transformer | \\nOpenAI's model architecture paradigm | \\nGenerative Pre-trained Transformer | \\n
\\n\\n| Token | \\nToken | \\nThe smallest unit of text processed by the model (about ΒΎ of an word) | \\nThe unit for billing and context length measurement | \\n
\\n\\n| Context Window | \\nContext Window | \\nThe maximum number of tokens the model can "see" at once | \\nLarger window means more memory | \\n
\\n\\n| Inference | \\nReasoning | \\nThe process of the model generating output | \\nDistinct from training | \\n
\\n\\n| Hallucination | \\nHallucination | \\nThe model confidently fabricating information that doesn't exist | \\nGenerating content inconsistent with facts, context, or goals | \\n
\\n\\n| Temperature | \\nTemperature | \\nControls sampling probability distribution; higher values are more divergent, lower values more stable | \\nSuggested to set lower when writing code | \\n
\\n\\n| Top-p / Top-k | \\nSampling Parameters | \\nControls the sampling range of candidate words | \\nAffects output diversity | \\n
\\n\\n| Embedding | \\nVector Embedding | \\nConverting text/images into numerical vectors for similarity calculation | \\nFoundation of RAG | \\n
\\n\\n| Fine-tuning | \\nFine-tuning | \\nContinuing training on a general model with specific data | \\nMaking the model more knowledgeable in a specific domain | \\n
\\n\\n| RLHF | \\nReinforcement Learning from Human Feedback | \\nAligning model behavior with human preferences | \\nMaking AI "obedient" | \\n
\\n\\n| MoE (Mixture of Experts) | \\nMixture of Experts | \\nActivating only part of parameters each time to improve efficiency | \\nRunning stronger models with less computing power | \\n
\\n\\n| Multimodal | \\nMultimodal | \\nSimultaneously processing text, images, audio, and video | \\nGPT-4o, Gemini are multimodal | \\n
\\n\\n| Transformer | \\nTransformer Architecture | \\nThe underlying neural network structure of modern LLMs | \\nAttention mechanism is the core | \\n
\\n\\n| KV Cache | \\nKey-Value Cache | \\nCaching context computation results to improve inference speed | \\nAvoiding repeatedly looking up recipes | \\n
\\n\\n| Latency | \\nLatency | \\nModel response time | \\nAffects user experience | \\n
\\n\\n| Throughput | \\nThroughput | \\nNumber of tasks that can be processed per unit time | \\nAffects concurrency capability | \\n
\\n\\n
\\n\\n
IV. Prompt Engineering
\\n\\n
\\n\\n\\n| Term | \\nChinese | \\nCore Meaning | \\n
\\n\\n\\n\\n| Prompt | \\nPrompt | \\nInput instructions given to the model | \\n
\\n\\n| System Prompt | \\nSystem Prompt | \\nUnderlying instructions defining Agent role, boundaries, and behavior | \\n
\\n\\n| Prompt Engineering | \\nPrompt Engineering | \\nTechniques for designing and optimizing prompts to obtain better output | \\n
\\n\\n| Zero-shot | \\nZero-Shot | \\nAsking the model to complete a task without giving examples | \\n
\\n\\n| Few-shot | \\nFew-Shot | \\nGiving a few examples to guide the model to output in a specific format/style | \\n
\\n\\n| Chain of Thought (CoT) | \\nChain of Thought | \\nGuiding the model to produce intermediate reasoning processes to improve complex reasoning ability | \\n
\\n\\n| ReAct | \\nReasoning+Action | \\nReasoning + Acting performed alternately, thinking while doing; core paradigm of Agent | \\n
\\n\\n| Role Prompting | \\nRole-playing | \\nHaving the model play a specific role (e.g., "You are a senior architect") | \\n
\\n\\n| Structured Output | \\nStructured Output | \\nForcing the model to output in JSON/XML and other formats | \\n
\\n\\n| Prompt Chaining | \\nPrompt Chain | \\nMultiple prompts connected in series to complete complex tasks | \\n
\\n\\n| Self-Consistency | \\nSelf-Consistency | \\nGenerating multiple reasoning results and then voting to select | \\n
\\n\\n| Tree of Thoughts (ToT) | \\nTree of Thoughts | \\nExploring multiple reasoning paths simultaneously | \\n
\\n\\n
\\n\\n
V. Agent Architecture
\\n\\n
\\n\\n\\n| Term | \\nChinese | \\nCore Meaning | \\nExample (Restaurant Business) | \\n
\\n\\n\\n\\n| Agent | \\nIntelligent Agent | \\nAI program capable of autonomous perception, decision-making, and task execution | \\nHead chef | \\n
\\n\\n| Multi-Agent | \\nMultiIntelligent Agent | \\nMultiple Agents working together with division of labor | \\nChef team collaborating to prepare meals | \\n
\\n\\n| Subagent | \\nExampleIntelligent Agent | \\nSpecialized sub-Agent derived from the main Agent | \\nSpecialized chefs (e.g., prep, cold dishes, desserts) | \\n
\\n\\n| Tool Use / Function Calling | \\nTool Call / Function Invocation | \\nAgent calling external tools/APIs to perform actions | \\nUsing kitchen knives, stoves, ovens, and other cooking tools | \\n
\\n\\n| Planning | \\nPlanning | \\nAgent breaking down goals and formulating execution steps | \\nCreating preparation and serving plans | \\n
\\n\\n| Reflection | \\nReflection | \\nAgent reviewing its own behavior and improving | \\nTasting dishes and adjusting flavors based on feedback | \\n
\\n\\n| Memory | \\nMemory | \\nLong-term information saved and reused across sessions (short-term/long-term) | \\nRecipe books and accumulated business data | \\n
\\n\\n| Agent Loop | \\nIntelligent AgentLoop | \\nThink β Act β Observe β Re-think iterative mechanism | \\nPreparation β Cooking β Tasting β Serving cycle | \\n
\\n\\n| Environment | \\nEnvironment | \\nThe real world where Agent perceives and executes actions | \\nKitchen environment | \\n
\\n\\n| Observation | \\nObservation | \\nObtaining feedback information after execution | \\nTasting feedback | \\n
\\n\\n| Execution | \\nExecute | \\nTransforming plans into real actions | \\nStarting to cook | \\n
\\n\\n| Long-term Memory | \\nLong-term Memory | \\nLong-term preservation of experience and knowledge | \\nBusiness database | \\n
\\n\\n
\\n\\n
VI. Harness Components (AI Agent Capability Modules)
\\n\\n
\\n\\n\\n| Term | \\nChinese | \\nCore Meaning | \\nExample (Restaurant Business) | \\n
\\n\\n\\n\\n| Harness | \\nHarness / Orchestration Framework | \\nExecution framework carrying Agent operation, context management, and tool orchestration | \\nThe entire kitchen system (kitchen itself) | \\n
\\n\\n| Skills | \\nSkills | \\nSpecialized capability modules that Agent can call | \\nVarious cooking techniques (frying, stir-frying, boiling, deep-frying) | \\n
\\n\\n| Context | \\nContext | \\nThe range of information accessible for the current task | \\nCurrent orders, ingredient inventory, and customer requirements | \\n
\\n\\n| MCP (Model Context Protocol) | \\nModel Context Protocol | \\nStandardized protocol for Agent to connect to external tools/data sources | \\nStandardized interfaces connecting to ingredient suppliers and food delivery platforms | \\n
\\n\\n| Permission | \\nPermission Control | \\nSecurity mechanism controlling what Agent can/cannot do | \\nKitchen operation permissions and procurement approvals | \\n
\\n\\n| RAG (Retrieval-Augmented Generation) | \\nRetrieval-Augmented Generation | \\nRetrieving from knowledge base first, then having the model generate, reducing hallucinations | \\nChecking recipe books for standard procedures before cooking | \\n
\\n\\n| Tool Registry | \\nTool Registry | \\nUnified management of tools Agent can call | \\nKitchen tool rack | \\n
\\n\\n| Session | \\nSession | \\nA single task lifecycle | \\nA single business operation | \\n
\\n\\n| Knowledge Base | \\nKnowledge Base | \\nExternal knowledge collection for Agent queries | \\nRestaurant recipe library | \\n
\\n\\n
\\n\\n
VII. Loop Tools (Automation Orchestration and Autonomous Evolution)
\\n\\n
\\n\\n\\n| Term | \\nChinese | \\nCore Meaning | \\nExample (Restaurant Business) | \\n
\\n\\n\\n\\n| /loop | \\nLoop Instruction | \\nMaking Agent execute in continuous loops | \\nContinuously operating serving pipeline | \\n
\\n\\n| /goal | \\nGoal Directive | \\nSetting goals to drive Agent autonomous achievement | \\nDaily business targets | \\n
\\n\\n| Cron | \\nScheduled Task | \\nAutomatically triggered according to time schedule | \\nBusiness hours and preparation scheduling | \\n
\\n>\\n\\n| Worktree | \\nWork Tree | \\nGit multi-branch parallel workspace | \\nMultiple stoves firing simultaneously without interference | \\n
\\n\\n| Workflow | \\nWorkflow | \\nPredefined multi-step automated process | \\nStandard serving SOP | \\n
\\n\\n| Scheduler | \\nScheduler | \\nCoordinating execution order of multiple tasks | \\nKitchen scheduling system | \\n
\\n\\n| Checkpoint | \\nCheckpoint | \\nSaving execution state for recovery | \\nResuming work after pausing business | \\n
\\n\\n| Human-in-the-loop | \\nHuman-in-the-Loop | \\nAllowing human intervention at critical steps | \\nHead chef's final confirmation before serving | \\n
\\n\\n
\\n\\n
VIII. Tool Ecosystem
\\n\\n
\\n\\n\\n| Tool | \\nType | \\nDescription | \\n
\\n\\n\\n\\n| Claude Code (cc) | \\nAI Agent / CLI | \\nAnthropic's official terminal Agent, typical representative of Harness | \\n
\\n\\n| Codex CLI | \\nAI Agent / CLI | \\nOpenAI's official command-line coding Agent | \\n
\\n\\n| Cursor | \\nAI IDE | \\nCode editor with built-in AI, main tool for Vibe Coding | \\n
\\n\\n| Windsurf | \\nAI IDE | \\nAI IDE from Codeium | \\n
\\n\\n| GitHub Copilot | \\nAI Programming Assistant | \\nThe earliest popularized AI programming plugin, more auxiliary completion | \\n
\\n\\n| Cline / Roo Code | \\nOpen Source Agent Plugin | \\nAutonomous coding Agent in VS Code | \\n
\\n\\n| Aider | \\nOpen Source CLI Agent | \\nAI pair programming tool in command line | \\n
\\n\\n| Devin | \\nAI Software Engineer | \\nCognition's "first AI programmer", more fully autonomous | \\n
\\n\\n| Continue | \\nOpen Source AI Plugin | \\nCustomizable model code assistant | \\n
\\n\\n| Qoder | \\nAI IDE | \\nDomestic intelligent development environment for AI programming scenarios, emphasizing Agent, project understanding, and code generation | \\n
\\n\\n| Trae | \\nAI IDE | \\nByteDance's new generation AI programming tool, supporting conversational development and engineering-level collaboration | \\n
\\n\\n| ZCode | \\nAI Programming Assistant | \\nZ.ai's intelligent programming product, supporting code generation, understanding, refactoring, and engineering collaboration | \\n
\\n\\n| OpenHands | \\nOpen Source Agent | \\nAutonomous software development, oriented toward complete engineering execution | \\n
\\n\\n| Bolt | \\nAI Builder | \\nRapidly generating applications, more product-focused | \\n
\\n\\n| Lovable | \\nAI Builder | \\nNatural language generation of Web, emphasizing product delivery | \\n
\\n\\n
\\n\\n
IX. Evaluation & Safety
\\n\\n
\\n\\n\\n| Term | \\nChinese | \\nCore Meaning | \\n
\\n\\n\\n\\n| Eval | \\nEvaluation | \\nMeasuring model/Agent capabilities using test sets | \\n
\\n\\n| Alignment | \\nAlignment | \\nMaking AI behavior conform to human intentions and values | \\n
\\n\\n| Guardrail | \\nGuardrails | \\nSafety mechanism limiting AI output scope | \\n
\\n\\n| Red Teaming | \\nRed Teaming | \\nActively attacking/inducing AI to discover vulnerabilities | \\n
\\n\\n| Prompt Injection | \\nPromptInjection | \\nMalicious input hijacking AI behavior (e.g., "ignore the above instructions") | \\n
\\n\\n| Context Poisoning | \\nContext Pollution | \\nAdding malicious information to context to mislead Agent | \\n
\\n\\n| Sandbox | \\nSandbox | \\nIsolated execution environment preventing AI misoperation from damaging systems | \\n
\\n\\n
\\n\\n
X. AI Engineering Evolution Path
\\n\\n
AI engineering capabilities are gradually moving upward: from controlling model output, to controlling context, to controlling systems, and ultimately evolving into continuously autonomous systems.
\\n\\n
\\n\\n\\n| Stage | \\nFocus | \\nKey Capability | \\n
\\n\\n\\n\\n| Prompt Engineering | \\nHow to ask | \\nPrompt design | \\n
\\n\\n| Context Engineering | \\nWhat information to provide | \\nContext organization | \\n
\\n\\n| Harness Engineering | \\nHow to organize capabilities | \\nTool orchestration | \\n
\\n\\n| Loop Engineering | \\nHow to continuously create results | \\nAutomatic execution and feedback | \\n
\\n\\n