Glossary
Who This Is For
This page is for every author and reader of xAgent documentation.
What It Is
The glossary is the source of standardized terminology for xAgent documentation. Add new terms here when they are introduced.
Core Terms
| Term | Standard Meaning |
|---|---|
| Agent | The entity responsible for understanding goals, planning, scheduling Tools, and providing feedback |
| Task | A goal unit executed by an Agent |
| Tool | The smallest external capability an Agent can invoke |
| Skill | A reusable set of task methods, constraints, and Tool usage guidance |
| AgentPlugin | A plugin service connecting external systems, user Channels, and capability declarations; called Connector before 0.0.16.beta |
| ProcessSandbox | The platform isolation boundary for untrusted processes, responsible for file mounts, environment, process trees, and resource limits |
| Runtime Assets | Execution dependencies independently installed and verified by xAgent, then provided read-only to ProcessSandbox |
| Execution Lease | The minimal file view, overlapping-write coordination, and file-change commit capability that WorkspaceFileService provides for one process execution |
| Memory | The memory system for long-term context |
| SubAgent | An independent execution unit for long-running tasks |
| Session | An interaction context between a user and an Agent |
| Workspace | The space for files, context, and intermediate artifacts used by an Agent during a Task |
| Trigger | A mechanism that turns a future time or external event into a Session Task |
| WorkGroup | Versioned configuration for agents and communication edges; not the owner of session runtime state |
| Work Record | Session-scoped topic records, revisions, and deltas used to inspect continuity and evidence |
| Model Profile ID | Stable reference to a model configuration; distinct from its display name or the Provider’s model ID |
| A2A Client | User-scoped connections to remote Agents, remote task tracking, and inbox result delivery |
| Delivery Receipt | Evidence that a particular messaging stage was accepted; does not by itself prove the whole task completed |
When to Use It
User guides, technical references, and maintenance documentation should all follow this glossary. A user guide can explain a term in plain language, but its core meaning must remain consistent.
Writing Rules
When writing documentation:
- Do not invent synonyms without a reason.
- Do not describe planned capabilities as implemented.
- Update this page and related documentation when adding a term.
- Explain how to use a feature in user-facing pages; reserve internal boundaries for technical references.