> ## Documentation Index
> Fetch the complete documentation index at: https://docs.komodor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Sign in, get a first run out of the built-in assistant, deploy one catalog agent and run it, and read the evidence every run records, in about ten minutes.

A new Komodor Agentic Operation Platform (KAOP) account has no agents and nothing connected. In about ten minutes you can get a first run out
of the built-in assistant, deploy an agent from the catalog, run it, and read the evidence it
produced. Everything else in KAOP extends that loop.

## Before you start

* The account URL your Komodor contact sent you. Sign-in is by **single sign-on**; there is no
  separate KAOP password, and your access is provisioned on first sign-in.
* Optionally, one system to connect (Kubernetes, Datadog, AWS, or GitHub) so the catalog agent
  you deploy has something real to look at.

## Your first run

<Steps>
  <Step title="Sign in">
    Open your account URL and sign in. You land on **Overview**: a chat box, counts of agents online
    and recent activity, and anything needing attention. The sidebar groups the console by job:
    **Build**, **Operate**, **Improve**, **Connect**, with **Settings** in the footer.
  </Step>

  <Step title="Ask the built-in assistant something">
    Type a question into the chat box on Overview. *What can you do?* is a fine start. The built-in
    chat assistant works before you have deployed or connected anything, and because it is an agent
    like any other, your question and its answer are recorded as a run.
  </Step>

  <Step title="Open the run">
    Open **History**. It lists every run and chat session, newest first. Click the question you just
    asked: you see what you asked, which tools the assistant used, how it reasoned, what it answered,
    and what it cost. This is what
    every run in KAOP records, whoever or whatever started it.
  </Step>
</Steps>

## Deploy a catalog agent and run it

The catalog holds Komodor-built agents you deploy as they are: read-only investigators for
Kubernetes, AWS, Azure, Google Cloud, Datadog and Grafana, code review and GitHub agents, remediation
agents, an AWS cost analyzer, and an orchestrator.

<Steps>
  <Step title="Pick an agent">
    Open **Build → Agents**, choose **Add agent**, then **Start from catalog** and **Browse catalog**.
    Each card says what the agent reads and whether it is **Ready to deploy** on your account or
    **Needs setup**, in which case the wizard collects what is missing, usually a credential for
    the system it investigates.

    If you connected a system in *Before you start*, deploy the investigator for that system. It has
    the shortest path from deploy to a useful run.
  </Step>

  <Step title="Deploy it">
    Press **Deploy to Komodor cloud**. Komodor runs the process for you; nothing to install. The agent
    shows as **deploying**, then **online** once it reports in, usually within a couple of minutes.
    It now appears in **Fleet** with its own identity, permissions, and run history.
  </Step>

  <Step title="Run it">
    On the agent's row in **Fleet**, choose **Run agent** and describe the task in plain text. For a
    Kubernetes investigator, something like *why is the checkout deployment in namespace prod
    restarting?*
  </Step>

  <Step title="Read the evidence">
    The run lands in **History**. Open it. Every tool the agent called, every argument and result, the
    reasoning between them, the final output, and the cost of the run are there. It is the same record you
    saw for the chat turn, now against your own infrastructure.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Onboarding" href="/get-started/onboarding">
    Connect your systems, your model, your alerts, and Slack: the six steps to production use.
  </Card>

  <Card title="Agent catalog" href="/manage-your-agents/build/catalog/overview">
    Every Komodor-built agent: what it reads, what it costs in time, where it stops.
  </Card>

  <Card title="Runs & evidence" href="/manage-your-agents/run/runs-evidence">
    What the evidence trail contains and how to read it.
  </Card>

  <Card title="APIs" href="/developer-tools/apis">
    Invoke an agent and read a run programmatically.
  </Card>
</CardGroup>


## Related topics

- [Overview](/get-started/overview.md)
- [Onboarding](/get-started/onboarding.md)