Operator Playbook¶
What to do once Overwatch is running. Pick the page that matches your situation:
Haven't installed yet?
Stop here and do the 5-minute Quick Start first.
Pick your situation¶
| You have... | Go to |
|---|---|
| One target VM (HTB box, single host) | HTB / Single Host |
| A network range to sweep (HTB ProLab, internal scope) | HTB / Network |
| An Active Directory lab (GOAD, Proxmox AD) | GOAD AD Lab |
| A foothold and want to capture creds (Responder, ntlmrelayx, fake LDAP) | Operator Infrastructure |
| An engagement that just wrapped | Retrospectives |
Want to see the full arc?¶
Read the End-to-End Walkthrough — a narrated example taking an engagement from empty graph to Domain Admin on a GOAD-like lab. It's the best way to understand what "good" looks like.
Reference¶
These pages aren't tutorials — they're answers to specific questions:
- parse_output vs report_finding — which tool to use to get data into the graph
- Session Instructions — the core loop (
AGENTS.mdcontent) for the AI to follow - CLI Adapter — operate Overwatch via shell when MCP is unavailable
How an Engagement Actually Flows¶
The same pattern applies regardless of target type:
flowchart LR
A[Start<br/>get_state] --> B[Preflight<br/>run_lab_preflight]
B --> C[Bootstrap<br/>scan + ingest]
C --> D{Main loop}
D --> E[next_task]
E --> F[validate_action]
F --> G[execute]
G --> H[parse_output<br/>or report_finding]
H --> I[log_action_event]
I --> D
D -.objective hit.-> J[generate_report]
J --> K[run_retrospective]
classDef start fill:#22c55e,stroke:#15803d,color:#fff
classDef loop fill:#3b82f6,stroke:#1e40af,color:#fff
classDef end_ fill:#d97706,stroke:#92400e,color:#fff
class A,B start
class D,E,F,G,H,I loop
class J,K end_
You give direction; the AI does the bookkeeping. See Session Instructions for the exact tool sequence the AI follows.