> ## Documentation Index > Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt > Use this file to discover all available pages before exploring further. # Cosmos Advisor > Your go-to agent for navigating Cosmos. ## What is Cosmos Advisor? **Cosmos Advisor** is a built-in Expert that sets up Cosmos for you. Instead of clicking through forms, describe what you want in plain language and the Advisor handles the setup — connecting [integrations](#connecting-integrations), building the [Environment](/cosmos/environments/overview) your agents run in, creating and tuning [Experts](/cosmos/experts), and wiring the [Automations](/cosmos/automations) that put them to work. It asks only what it needs, confirms the plan, and remembers your decisions across sessions. It works in four phases and resumes wherever you have open work: connect **dependencies** (integrations), stand up an **Environment**, create an **Expert**, then **analyze** how your agents are doing and tune them. The most successful Cosmos users configure everything through Cosmos Advisor rather than the web UI. Describing what you want in a session is faster than clicking through forms, and the Advisor picks the right defaults, wires up dependencies, and remembers your decisions across sessions. ## Connecting integrations Before your agents can do useful work, they need the right connections: code to read, places to post, and events to react to. Tell the Advisor what you want your agents to do and it identifies which integrations are required, checks what's already connected, and walks you through connecting the rest — GitHub, Slack, Linear, PagerDuty, GitLab, Jira/Confluence, and more. The Advisor tells you which integrations a given Expert depends on and flags any that aren't connected yet, but the browser sign-in flow is completed by you (or an admin) — the Advisor can't finish OAuth on its own. See [Limitations](/cosmos/advisor/limitations). Reference: [GitHub](/cosmos/config-github), [Linear](/cosmos/config-linear), and [Slack](/cosmos/config-slack) configuration. ## Creating and modifying Environments An [Environment](/cosmos/environments/overview) is the virtual machine your Experts run in — its base image, synced repositories, environment variables, and toolchain. Describe the project and the Advisor picks the image, syncs the repos, and installs what's needed, rather than you building it by hand in the environment form. ```text Example theme={null} Select: Cosmos Advisor Prompt: Help me create an Environment for a Ruby on Rails project. I want to use Ruby 3.4 and Sqlite3. ``` The Advisor can also update an existing Environment — adding a dependency, syncing another repository, or setting an environment variable. Updates only apply to future sessions. For all the ways to build and update one by hand, see [Cloud environments](/cosmos/environments/cloud). ## Creating and modifying Experts An [Expert](/cosmos/experts) is a reusable agent template. The Advisor can deploy Experts from a built-in catalog — PR Author, Deep Code Reviewer, Pair Reviewer, PR Risk Analyzer, Personal Assistant, Backlog Dispatcher, Project Builder, and more — confirming your picks, deploying them in the right dependency order, and handing you a one-click link to try each one. For end-to-end code review coverage, it recommends deploying the review Experts together, since each covers a different stage from PR open to merge. When nothing in the catalog fits, the Advisor designs a **bespoke Expert** with you through a short conversation: it restates the goal, asks only what's genuinely ambiguous (how it fires, whose identity it acts as, who can launch it, where it posts, and whether to wire in memory — recommended by default), confirms the design in plain language, then creates it. You never see or edit a configuration file — the only thing you interact with is the finished Expert in your launcher. Reference: [Template Experts](/cosmos/experts-templates) and [Configure a custom Expert](/cosmos/experts-configure-custom). ## Creating and modifying Automations An [Automation](/cosmos/automations) launches an Expert whenever something happens — a PR opens, a Linear ticket changes state, a cron fires, or a custom webhook arrives. The Advisor wires the right trigger to the right Expert and lets you decide when it goes live. Many catalog Experts ship with triggers, but the Advisor deploys them **turned off** by default so nothing fires before you're ready — the Experts are usable from Home immediately; enabling triggers is a separate step. When you're ready, the Advisor turns triggers on in one step and lets you choose the scope: just the Experts you tried, or the full set you picked. For a bespoke Expert, it can also stage the rollout — create it with the trigger disarmed, let you try it once, then arm it when you confirm. Reference: [Understanding Automation](/cosmos/automations), [Schedules](/cosmos/config-schedules), and [Webhooks](/cosmos/config-webhooks). ## Analyzing and tuning your fleet Once your Experts have been running for a while, the Advisor's fourth phase is analysis: it pulls session data and looks for patterns worth acting on — repeated failures (edit the prompt), usage skew (retire dormant Experts, split overworked ones), sessions stuck mid-run or waiting on humans (tighten the prompt, route to Slack, swap models), and missing capabilities (return to integration or Environment setup). It surfaces the relevant cut, explains what it sees, and can apply the change in the same conversation. Cosmos doesn't ship built-in analytics dashboards for this; the Advisor works from session data directly. For tenant-wide usage and cost reporting, ask about the Cosmos Analyst Expert. ## Next steps * **[Sample Prompts](/cosmos/advisor/sample-prompts)** — ready-to-use prompts for common Advisor tasks. * **[Limitations](/cosmos/advisor/limitations)** — what the Advisor can and can't do on its own. ## See Also * [Getting Started with Cosmos](/cosmos/getting-started) — the core concepts the Advisor works with. * [Experts](/cosmos/experts) — the catalog and custom Experts the Advisor can deploy. * [Understanding Automation](/cosmos/automations) — how triggers, events, and Experts fit together.