OTInstaller
Sign in

Start

Build your setup. One command installs it.

Pick starter packs and tools, the AI agents that should use them, and how ot saves results. This page builds an ot start command; run it, check the summary, and ot installs the tools and saves your settings. Nothing you pick here is sent anywhere.

1 Install ot

Skip this if you have it. Tools run in containers, so Docker Desktop or Podman has to be running. If your ot doesn't know ot start yet, run ot self-update.

curl -fsSL https://get.otinstaller.com/ot | sh
What this script does
  1. Downloads the latest ot release for your machine from GitHub Releases.
  2. Checks its SHA-256 against checksums.txt, and the Ed25519 signature on that file against the key built into the script.
  3. Puts ot in /usr/local/bin or ~/.local/bin. Nothing else is written. Read the script.
irm https://get.otinstaller.com/ot.ps1 | iex
What this script does
  1. Downloads the latest ot release for your machine from GitHub Releases.
  2. Checks its SHA-256 against checksums.txt, and the Ed25519 signature on that file against the key built into the script.
  3. Puts ot in %LOCALAPPDATA%\Programs\ot, and adds it to your PATH. Nothing else is written. Read the script.

2 Starter packs

The playbooks bundled with ot: a few tools for one kind of target, none needing an API key. A pack picks its tools in the list below; run them all at once with ot playbook.

3 AI agents

ot start adds ot's MCP server to these clients, as ot mcp install does, so they can search, install and run tools. Runs that touch a target ask you first. How agents use ot

4 Settings

Output of ot run
Where results are saved
API keys
Registry and telemetry

5 Tools 0 picked

Everything in the registry, A to Z. Untick a pack's tool to leave it out.

6 Run it

ot start

Without --yes, ot start opens with these choices so you can check them; it changes nothing until you confirm. Add --dry-run to see what it would do.

Esc

Try

↑ ↓ to move↵ to open