> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt > Use this file to discover all available pages before exploring further. # CloudThinker > Meet the frontier investigation agents that find root causes and propose fixes across incidents, code, cost, and security. CloudThinker AI agent orchestrating cloud operations — incidents resolved, PRs reviewed, costs optimized, security remediated, debug output CloudThinker is a self-healing ops platform: frontier investigation [agents](/guide/agents/overview) investigate every issue across AWS, Azure, GCP, and Kubernetes and propose the fix, while your engineers set intent and approve. ## Start here Three first tasks, each 5–10 minutes with a result you can verify. Just created your account? The [quickstart](/quickstart) takes you from sign-in to your first investigation — no cloud credentials needed if you start with the demo.
Frontier investigation
Investigate your first incident

Frontier investigation agents work out the root cause of any incident and propose the fix for you to approve. Log one by hand to try it in minutes — no alert source needed — then route alerts through Pulse so every incident gets investigated.

Run your first investigation → Find idle resources, oversized instances, and unused commitments — with projected monthly savings Connect a Git repository and get AI review comments on the next pull request ## Choose your goal Pick the outcome you want next. Each goal maps to a guided path. **Resolve** — Pulse strips noise from monitoring; agents investigate the rest, propose the fix, and run approved runbooks **Optimize** — continuous spend audit across AWS, Azure, and GCP with rightsizing recommendations and approval-gated remediation **Review** — every PR reviewed with context from running infrastructure, past incidents, and your team's conventions **Cyber** — give the security agent one app target, optional authentication, and source context to test and verify **Autonomous agents + skills** — teach agents your runbooks, conventions, and policies once, as reusable skills, so the loop runs without restating them **Tutorial** — run your role's first prompts against your live environment, then follow the chain into your first module setup ## How CloudThinker works Every module runs the same agentic loop: **Detect → Analyze → Resolve → Validate**. Agentic loop: Detect, Analyze, Resolve, and Validate in a cycle, with engineers at the center setting intent and approving Agentic loop: Detect, Analyze, Resolve, and Validate in a cycle, with engineers at the center setting intent and approving Agents **detect** signals from your connections — metrics, cost data, pull requests, alerts. They **analyze** each signal against topology, history, and [team knowledge](/guide/knowledge) to form a plan. The plan **resolves** under your autonomy mode — [Manual or Auto](/guide/auto-mode) — with [approvals](/guide/approval) gating sensitive actions. Finally the agent **validates** the outcome and writes the result back into memory, so the next iteration starts smarter. Your engineers stay on the loop, not in every step: they set intent, choose the autonomy mode, and approve the fixes that need judgment. The [AgenticOps field guide](/learn/aio/introduction) covers the reference architecture and governance discipline behind the loop. ## The four modules The same investigation agents, memory, and approvals run across all four modules. Compare what each needs in [Modules](/guide/modules). [Pulse](/guide/pulse/overview) suppresses monitoring noise. When something escalates, frontier investigation agents form hypotheses, gather evidence, propose the fix, and run approved [runbooks](/guide/incident/runbooks). AI review on every PR with context from running infrastructure, [past incidents](/guide/incident/incident-memory), and [team conventions](/guide/code-review/convention-rules). Inline comments, reproduction steps, suggested patches. Continuous spend audit across [AWS](/guide/connections/aws), [Azure](/guide/connections/azure), and [GCP](/guide/connections/gcp). Idle resources, oversized instances, unused commitments — surfaced with projected savings and approval-gated remediation. A dedicated security agent continuously tests one live application target, preserves its attack surface and findings between runs, and verifies each issue with reproducible proof. ## Why CloudThinker Most engineering time on an incident goes to investigation: reassembling context from Datadog, CloudWatch, GitHub, and more before anyone can decide on a fix. CloudThinker's frontier investigation agents do that work on every issue, around the clock, and hand your engineers a root cause and a proposed fix to approve. Every action runs under your policy, behind an auditable approval trail, and every run writes back to shared memory so the next investigation starts smarter. That is a self-healing cloud. The same agents bring that investigation to Review, Optimize, and Cyber. See how in [The Harness](/guide/harness), or start with the [quickstart](/quickstart). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.