otinstaller · Frameworks

Install AIRecon on Linux in one command

AIRecon pairs a locally hosted language model with a Kali container and a terminal UI, and lets the model plan and run recon steps against a target you name. Everything runs on your machine.

AIRecon in three lines

pipx install otinstaller
ot install airecon
ot run airecon -- d:example.com

Runs pikpikcu/airecon (MIT, ★ 1.1k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.

What AIRecon is for

Experimenting with agent-driven recon on lab targets.

Typed inputs for AIRecon

otinstaller translates these prefixes into AIRecon's own flags. Anything else after -- is passed through unchanged, so every original flag still works.

d:: domain · ot run airecon -- d:example.com

It also takes ip input through its own flags; there is no typed prefix for those yet.

Run every installed tool that takes the same input at once: ot run --all d:example.com

Where the results go

Every run lands under ./results/airecon/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff airecon <target>, and pull indicators out with ot extract.

Before you run it

Needs Ollama and Docker installed and a model downloaded. Keep it on lab targets; the agent chooses active tools.

Update, remove, inspect

ot info airecon      # inputs, flags, keys
ot example airecon   # sample output
ot update airecon    # move to the next tested version
ot remove airecon    # delete its virtualenv

Full reference for this tool: docs for airecon.

Pairs with

OpenOSINT

OpenOSINT is an agent-style tool: you describe what you want in a REPL and it chooses and runs lookups on usernames, emails, and domains.

secator

secator wraps dozens of recon and scanning tools behind one command with a shared output format, and runs them as tasks, workflows, or full scans.

SpiderFoot

SpiderFoot runs two hundred-odd modules against a domain, IP, email, or username and links what they return into one graph.

FAQ

AIRecon with otinstaller, answered

How do I install AIRecon on Kali or Ubuntu?

Install otinstaller once with pipx install otinstaller, run ot init, then ot install airecon. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.

Which inputs does AIRecon take through otinstaller?

d: (domain). otinstaller maps each prefix to AIRecon's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.

Where does otinstaller save AIRecon results?

Under ./results/airecon/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff airecon <target> to compare the last two.

Does AIRecon need an API key or a login?

No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.

Can I run AIRecon together with other tools?

Yes. ot run --all d:example.com runs every installed tool that accepts domain input, in parallel, including AIRecon. Save the combination as a playbook to repeat it.