Cosmos
Getting Started with Cosmos
Understand the core building blocks of Augment Cosmos — Environments, Experts, Sessions, Capabilities, and Triggers.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Understand the core building blocks of Augment Cosmos — Environments, Experts, Sessions, Capabilities, and Triggers.
| Concept | What it is |
|---|---|
| Expert | A reusable template that defines an agent’s behavior. It includes a name, instructions, environment, system prompt, model, and which capabilities it has access to, triggers and events it can react to, and visibility — either shared or private. |
| Environment | A reusable virtual machine where your Experts run. Bundles a name, base image, repositories, environment variables, and visibility. |
| Capability | A bundle of tools or MCP servers that give an Expert a specific ability (CLI Tools, GitHub, Linear, Slack, Web Access, etc.). |
| Trigger | A structured notification that turns a real-world event into an Expert action. Sources include GitHub (a new PR), Linear (a status change), Slack (a new message), PagerDuty (a P0 incident), a cron schedule, or a custom webhook. |
| ↳ Skills | A reusable knowledge package (following agentskills.io) that provides specialized instructions or domain expertise to an Expert. Stored inside Files. |
| ↳ Visibility | Controls whether an Environment or Expert is private to you or shared across your organization. |
| Session | The conversation with an Expert — every message, turn, and tool call. Sessions can be private or shared, and are accessible from the web, mobile, and Slack. |
| Automation | A persistent, event-driven rule that tells Cosmos to launch an agent — or wake up a running one — whenever something happens in a connected services (GitHub, Linear, Slack, etc.). |
| Files | Objects stored in a virtual file system that Experts can read and write. Shared files are visible to all members of an Organization, while private files are only visible to the User who created them. |