Showing the first 18000 characters. Load the complete file to read the remainder.
# Augment
- [Introduction](https://docs.augmentcode.com/introduction.md): Augment Code is the AI-native coding platform built for enterprise-grade software engineering. Transform how you build and ship software with powerful coding agents, deep codebase intelligence, and flexible automations.
- [Getting Started with Cosmos](https://docs.augmentcode.com/cosmos/getting-started.md): Understand the core building blocks of Augment Cosmos — Environments, Experts, Sessions, Capabilities, and Triggers.
- [Configuring Cosmos](https://docs.augmentcode.com/cosmos/configuring-cosmos.md): Connect your tools, set up an environment, and start your first session in Cosmos.
- [Software Factory](https://docs.augmentcode.com/cosmos/software-factory/overview.md): Connect planning, implementation, review, and feedback into a repeatable delivery workflow with Cosmos.
- [Requirements → Ticket](https://docs.augmentcode.com/cosmos/software-factory/requirements-to-ticket.md): Turn feature requirements into a reviewed design and actionable tickets.
- [Ticket → PR](https://docs.augmentcode.com/cosmos/software-factory/ticket-to-pr.md): Turn a delegated ticket into a draft PR with Ticket Manager and PR Author.
- [PR → Merge](https://docs.augmentcode.com/cosmos/software-factory/pr-to-merge.md): Review and repair changes before a human merges them.
- [Signal → Ticket](https://docs.augmentcode.com/cosmos/software-factory/signal-to-ticket.md): Turn feedback and incident findings into actionable follow-up.
- [Cosmos Environments](https://docs.augmentcode.com/cosmos/environments/overview.md): The compute environment where your agents access filesystem, repositories, execute code, and run tools. They can be an Augment-hosted cloud sandbox, virtual machine, or even your laptop.
- [Cloud Environments](https://docs.augmentcode.com/cosmos/environments/cloud.md): A cloud environment is a Augment hosted compute environment and filesystem for your agent to run.
- [Self-Hosted Environments](https://docs.augmentcode.com/cosmos/environments/daemons.md): You can run your agents on your own virtual or physical infrastructure with self-hosted daemons.
- [Configure Self-Hosted Daemons with daemon-config.json](https://docs.augmentcode.com/cosmos/environments/daemon-config.md): Configure Auggie's self-hosted daemon with discovered JSON files or generate configuration from explicit command-line flags.
- [Configure Daemon Workspaces and Isolation](https://docs.augmentcode.com/cosmos/environments/daemon-workspaces.md): Configure repositories, repository discovery, and isolated or shared workspaces for self-hosted Cosmos daemons.
- [Use Self-Hosted Daemon Pools](https://docs.augmentcode.com/cosmos/environments/daemon-pools.md): Group self-hosted daemon machines into a pool and configure connectors, workspace behavior, and routing.
- [Using Sessions](https://docs.augmentcode.com/cosmos/sessions-overview.md): Work with an Expert in a conversation — where you give the agent a task, watch it run and follow every turn.
- [Cosmos Experts](https://docs.augmentcode.com/cosmos/experts.md): Reusable agent configurations for engineering workflows like authoring code, reviewing code, investigating incidents, and more.
- [Template Experts](https://docs.augmentcode.com/cosmos/experts-templates.md): Choose a Template Expert for PR authoring and repair, code review, incident response, feedback triage, project building, or ticket management.
- [PR Author](https://docs.augmentcode.com/cosmos/experts-pr-author.md): Use the PR Author Expert to have an agent build a change from a task description — creating the branch, implementing changes, and handling follow-up.
- [PR Fixer](https://docs.augmentcode.com/cosmos/experts-pr-fixer.md): Use the PR Fixer Expert to repair review findings, CI failures, and merge conflicts on a pull request or merge request.
- [Risk Analyzer](https://docs.augmentcode.com/cosmos/experts-risk-analyzer.md): Use the Risk Analyzer Expert to triage new code reviews and route complex changes to focused human review.
- [Deep Reviewer](https://docs.augmentcode.com/cosmos/experts-deep-reviewer.md): Use the Deep Reviewer Expert for non-interactive, line-by-line correctness review with inline findings.
- [Pair Reviewer](https://docs.augmentcode.com/cosmos/experts-pair-reviewer.md): Use the Pair Reviewer Expert for interactive, intent-focused code reviews where a human makes the final judgment calls.
- [Verifier](https://docs.augmentcode.com/cosmos/experts-verifier.md): Use the Verifier Expert to exercise a change in a running environment and report evidence-backed findings.
- [Project Builder](https://docs.augmentcode.com/cosmos/experts-project-builder.md): Use the Project Builder Expert to turn a large feature into a reviewed design, ticket breakdown, and coordinated implementation.
- [Feedback Triager](https://docs.augmentcode.com/cosmos/experts-feedback-triager.md): Use the Feedback Triager Expert to classify Slack feedback, investigate technical reports, and create tickets or launch fixes when appropriate.
- [Incident Investigator](https://docs.augmentcode.com/cosmos/experts-incident-investigator.md): Use the Incident Investigator Expert to watch alert channels, post root-cause analyses in-thread, and accompany incidents through to resolution.
- [Ticket Manager: from ticket to PR](https://docs.augmentcode.com/cosmos/experts-ticket-manager.md): Connect your tools, set up Ticket Manager with Advisor, and delegate your first ticket from GitHub, Linear, or Jira.
- [Ticket Dispatcher](https://docs.augmentcode.com/cosmos/experts-ticket-dispatcher.md): Use the Ticket Dispatcher Expert to scan tickets on a schedule and launch implementation workers for work that is ready to implement.
- [Data Analyst](https://docs.augmentcode.com/cosmos/experts-data-analyst.md): Use the Data Analyst Expert to answer questions about your data with read-only queries against your source-of-truth datasets, naming the source and window for every answer.
- [Cosmos ROI Analyst](https://docs.augmentcode.com/cosmos/experts-cosmos-analyst.md): Use the Cosmos ROI Analyst Expert to learn how Cosmos has impacted your engineering team using GitHub PR / GitLab MR activity and cost data.
- [Code Review Memory Manager](https://docs.augmentcode.com/cosmos/experts-code-review-memory.md): Use Code Review Memory to turn feedback from completed code reviews into durable, repository-specific guidance for future reviews.
- [Memory](https://docs.augmentcode.com/cosmos/experts-memory.md): Learn how Experts retain useful context across sessions and apply it to future work.
- [Configure a Custom Expert](https://docs.augmentcode.com/cosmos/experts-configure-custom.md): Create a custom Cosmos Expert for a team-specific workflow when no existing Template Expert fits.
- [Delegating Work](https://docs.augmentcode.com/cosmos/workers-subagents.md): The three ways a Cosmos Expert can hand off work — workers, subagents, and Expert-to-Expert interactions through integrations.
- [How Experts respond to events](https://docs.augmentcode.com/cosmos/experts-triggers-subscriptions-integrations.md): Understand how Cosmos Experts respond to events and interact with the outside world.
- [Configure a Code Review Pipeline](https://docs.augmentcode.com/cosmos/experts-code-review.md): Configure a Cosmos PR-to-merge pipeline with specialized Experts for authoring, review, repair, verification, and approval.
- [Understanding Automation](https://docs.augmentcode.com/cosmos/automations.md): What an automation is in Cosmos, how it wires an event source to an Expert, and where to inspect the events that fire one.
- [Configuring Triggers](https://docs.augmentcode.com/cosmos/config-triggers.md): Add triggers to a Cosmos Expert — pick an event source, choose an event type, and filter payloads with JSONLogic expressions.
- [Webhooks](https://docs.augmentcode.com/cosmos/config-webhooks.md): Wire any external event source to a Cosmos Expert using a custom webhook — receive JSON payloads and filter them with JSONLogic expressions.
- [Using Schedules as Triggers](https://docs.augmentcode.com/cosmos/config-schedules.md): Fire Cosmos Experts on a recurring cron schedule — daily standups, hourly health checks, and more.
- [Manage automations](https://docs.augmentcode.com/cosmos/manage-automations.md): Review the schedules, webhooks, and events that trigger your Experts, and track each one's runs from a single page.
- [Setting Up Automations with Advisor](https://docs.augmentcode.com/cosmos/automation-advisor.md): Let Advisor recommend, deploy, and wire up automations conversationally — nothing fires until you say so.
- [Your First Automation](https://docs.augmentcode.com/cosmos/first-automation.md): Build two automations from scratch — a personal daily PR nudger on a schedule, and a team-wide review nudger driven by GitHub events with a payload filter.
- [Other Workflow Automations to Explore](https://docs.augmentcode.com/cosmos/automation-explore.md): Explore additional workflow automations including data engineering, CI/CD failure resolution, code review automation, and Linear ticket resolution.
- [Cosmos Advisor](https://docs.augmentcode.com/cosmos/advisor/overview.md): Your go-to agent for navigating Cosmos.
- [Sample Prompts](https://docs.augmentcode.com/cosmos/advisor/sample-prompts.md): Ready-to-use prompts for common Cosmos Advisor tasks — connecting integrations, building Environments, deploying and tuning Experts, and wiring Automations.
- [Limitations](https://docs.augmentcode.com/cosmos/advisor/limitations.md): What Cosmos Advisor can and can't do on its own — the two setup steps you still complete manually through the web UI.
- [MCP Registry](https://docs.augmentcode.com/cosmos/config-mcp.md): Extend Cosmos Experts with external tools and services through Model Context Protocol (MCP) servers.
- [Managing Secrets](https://docs.augmentcode.com/cosmos/config-secrets.md): Store API keys, tokens, and credentials in the Cosmos Secrets Manager and inject them into Expert VMs at boot.
- [Skills](https://docs.augmentcode.com/cosmos/config-skills.md): Extend the agent with domain-specific expertise using reusable knowledge packages that follow the agentskills.io specification.
- [Understanding Files](https://docs.augmentcode.com/cosmos/understanding-files.md): Files persist across Expert Sessions — how Experts produce them, how they sync, and how you browse files and folders in Cosmos.
- [Understanding Artifacts](https://docs.augmentcode.com/cosmos/artifacts.md): View, search, and manage the durable outputs a Cosmos session produces — pull requests, Git branches, Linear issues, and custom links.
- [Integrate Azure DevOps Cloud](https://docs.augmentcode.com/cosmos/connectors/azure-devops-cloud.md): Connect Azure DevOps Cloud to Cosmos to receive webhook events, access repositories, and automate pull request authoring and code review.
- [Using GitHub as a Tool or Trigger](https://docs.augmentcode.com/cosmos/connectors/config-github.md): Configure GitHub triggers and the GitHub API tool on your Cosmos Experts — listen for PRs, pushes, CI failures, and slash commands.
- [Integrate GitHub Enterprise Server (GHES)](https://docs.augmentcode.com/cosmos/connectors/github-enterprise-server.md): Connect GitHub Enterprise Server to Cosmos with webhooks, a daemon, and the GitHub CLI to automate pull request reviews on your infrastructure.
- [Integrate GitLab Cloud](https://docs.augmentcode.com/cosmos/connectors/gitlab-cloud.md): Integrate GitLab Cloud with Cosmos to receive webhooks, clone repositories, and deploy experts that author and review merge requests.
- [Integrate GitLab Self-Hosted](https://docs.augmentcode.com/cosmos/connectors/gitlab-self-hosted.md): Connect self-hosted GitLab to Cosmos using webhooks, a daemon, and the GitLab CLI to automate merge request workflows on your infrastructure.
- [Atlassian Jira Cloud](https://docs.augmentcode.com/cosmos/connectors/jira-cloud.md): Configure Atlassian Jira Cloud app and user integrations for Cosmos, including workflow triggers, subscriptions, and user authorization.
- [Integrate ClickUp](https://docs.augmentcode.com/cosmos/connectors/clickup.md): Connect ClickUp to Cosmos using webhooks and the ClickUp MCP server to receive task events and read workspace objects.
- [Integrate Datadog](https://docs.augmentcode.com/cosmos/connectors/datadog.md): Connect Datadog to Cosmos with webhooks and the Datadog MCP server so experts can respond to monitoring events and read logs.
- [Using Linear as a Tool or Trigger](https://docs.augmentcode.com/cosmos/connectors/config-linear.md): Configure Linear triggers and the Linear API tool on your Cosmos Experts — listen for issues, status changes, and comments.
- [Integrate Microsoft Teams](https://docs.augmentcode.com/cosmos/connectors/microsoft-teams.md): Connect Microsoft Teams so Cosmos Experts can read and respond to channel posts and chat messages.
- [Using Slack as a Tool or Trigger](https://docs.augmentcode.com/cosmos/connectors/config-slack.md): Configure the Augment Slack bot for Cosmos Experts — enable Slack as a tool, set up triggers, and interact with agents from Slack channels.
- [Integrate Twingate](https://docs.augmentcode.com/cosmos/connectors/twingate.md): Configure a Cosmos cloud environment to securely access resources on a remote Linux virtual machine through Twingate.
- [Atlassian Jira Cloud (legacy)](https://docs.augmentcode.com/cosmos/connectors/jira-cloud-webhooks-mcp.md): Set up the legacy Jira Cloud integration with Cosmos using webhooks for issue events and the Jira MCP server to read and update tickets.
- [Cosmos Spaces](https://docs.augmentcode.com/cosmos/spaces/overview.md): Spaces group the experts, environments, sessions, and settings for a team or workstream so everyone works from a shared, focused set of resources.
- [Managing Spaces](https://docs.augmentcode.com/cosmos/spaces/managing.md): Switch between Spaces, create new ones, assign experts and environments, and control who can manage them.
- [101 - Getting Started On Cosmos](https://docs.augmentcode.com/cosmos/guides/getting-started-on-cosmos.md): Connect your tech stack & deploy your v1.0 software factory with Cosmos Advisor
- [Software Factory: Core Loops Cosmos Can Help Build](https://docs.augmentcode.com/cosmos/guides/software-factory-core-loops.md): Software Factory: Core Loops Cosmos Can Help Build -
- [A portfolio of software factories: one per team](https://docs.augmentcode.com/cosmos/guides/n-software-factories-one-per-team.md): A portfolio view of per-team software factories, shared environments, and Cosmos Advisor.
- [Admin Checklist](https://docs.augmentcode.com/cosmos/guides/admin-checklist.md): Set up your Cosmos enterprise tenant with this administrator checklist covering initial access, domains, users, and single sign-on.
- [Self-hosted Kubernetes](https://docs.augmentcode.com/cosmos/guides/self-hosted-k8s.md): Connect a self-hosted Kubernetes cluster to Cosmos using Minikube, generated manifests, or Helm chart.
- [Docker Compose in cloud envs](https://docs.augmentcode.com/run-docker-compose-with-cloud-envs.md): Configure a Cosmos cloud env to run docker compose commands
- [Share instructions across multiple experts](https://docs.augmentcode.com/sharing-some-instructions-across-n-experts.md)
- [Cosmos Keyboard Command Reference](https://docs.augmentcode.com/cosmos/keyboard-command-reference.md): A reference of all available keyboard shortcuts for navigating and controlling the Cosmos app.
- [Introducing Auggie CLI](https://docs.augmentcode.com/cli/overview.md): Auggie in the terminal gives you powerful agentic capabilities to analyze code, make changes, and execute tools in an interactive terminal and in your automated workflows.
- [Install Auggie CLI](https://docs.augmentcode.com/cli/setup-auggie/install-auggie-cli.md): Install Auggie to get agentic coding capabilities in your terminal, on your server, or anywhere your code runs.
- [Login and authentication](https://docs.augmentcode.com/cli/setup-auggie/authentication.md): You will need an active account and valid authentication session to use Auggie CLI, which you can get by following the instructions below.
- [Workspace context](https://docs.augmentcode.com/cli/setup-auggie/workspace-context.md): Auggie will automatically index the current working directory or directory you specify to give Augment a full view of your system.
- [Index your workspace](https://docs.augmentcode.com/cli/setup-auggie/workspace-indexing.md): When your workspace is indexed, Augment can provide tailored code suggestions and answers based on your unique codebase, best practices, coding patterns, and preferences. You can always control what files are indexed.
- [Automatic Updates](https://docs.augmentcode.com/cli/autoupgrade.md): Learn how to manage and troubleshoot Auggie CLI's automatic update feature.
- [Configuration Wizard](https://docs.augmentcode.com/cli/config.md): Learn how to configure Auggie CLI settings using the interactive configuration wizard.
- [Subagents](https://docs.augmentcode.com/cli/subagents.md): Configure custom agents for specific tasks to automate your workflow and share them with your team.
- [Rules & Guidelines](https://docs.augmentcode.com/cli/rules.md): Configure custom rules and guidelines to provide context-aware assistance in Auggie CLI.
- [Agent Skills](https://docs.augmentcode.com/cli/skills.md): Extend Auggie's capabilities with specialized domain knowledge using the agentskills.io specification.
- [Tool Permissions](https://docs.augmentcode.com/cli/permissions.md): Control what tools the agent can execute with granular permission settings for security and compliance. Honored by the Auggie CLI and by Cosmos cloud agents; not enforced in the Augment code extension.
- [Plugins and Marketplaces](https://docs.augmentcode.com/cli/plugins.md): Manage and install plugins from marketplaces to extend Auggie's capabilities
- [Integrations and MCP](https://docs.augmentc
Measured from the saved file
Linked document
UTF-8 text size
41.7 KB42727 bytes
Token count
9379o200k_base encoding
Markdown links
214214 distinct URLs
Fenced code blocks
0221 lines in the file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Project H1
Augment
Context architecture
How the content is divided
1 H2 sections organize 214 parsed Markdown links. 211 links point to .md or .markdown paths; 1 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
OpenAPI SpecsLine 215
3
178
41
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Code, installation and API examples
Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
The Optional section
No H2 section named “Optional” was detected in this file.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP references and configuration text
MCP-related text was detected in the captured file. 21 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
What can be said about freshness
This capture establishes a baseline. Update frequency cannot be determined from one observation.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.