> For the complete documentation index, see [llms.txt](https://osintverse.gitbook.io/otinstaller/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://osintverse.gitbook.io/otinstaller/changelog.md).

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## \[Unreleased]

## \[0.0.3] - 2026-10-12

### Added

* Contact email and OSINTverse social links in the README and `otinstaller about`
* README tool catalogue, generated from the registry, plus a why section, FAQ, docs link and launch video

### Changed

* user-scanner 1.5.2.2, linkook 1.1.3, aliens-eye 2.7.0 and mailaccess 0.18.5, each re-verified on Ubuntu 24.04 with Python 3.12
* blackbird now installs from its new home, antoniaci/blackbird; Telepathy points to prose-intelligence-ltd/Telepathy-Community

### Fixed

* mailaccess runs `mailaccess --no-banner investigate <email>`; the old `--email` flag no longer exists, and 0.18.5 fixes the missing greenlet dependency

## \[0.0.2] - 2026-10-11

### Added

* Startup banner for init, about, and a bare invocation
* `requires_python` on registry entries, with install failing early when the interpreter is too old
* `long_running` flag so whatsapp-osint and instagram-monitor are left out of `--all` and auto

### Changed

* README rewritten for the PyPI page, with absolute links and project URLs
* pyyaml pinned to 6.0.3 and ruff pinned to 0.16.10

### Fixed

* Registry input types and entrypoints for ghunt, theharvester, bbot, linkook, spiderfoot, ignorant, aliens-eye, telepathy, and neutrosint
* Git-installed tools pinned to full commit SHAs
* Removed the fabricated ghunt example output
* Interrupted runs print the real output path
* Result folders use the typed input value when no other target name is available

## \[0.0.1] - 2026-09-29

### Added

* Initial release
* Basic tool management: install, remove, run, update, list, search, info
* Parallel tool execution with configurable concurrency
* Result storage with metadata and SHA256
* API key management via \~/.otinstaller/.env
* Responsible use notice on first run
* Auto-detect target type with the auto command
* Example output viewer
* Resume interrupted jobs
* Doctor diagnostics
* Typed input prefixes: u: (username), e: (email), p: (phone), d: (domain), url: (URL), q: (query), geo: (coordinates), tg: (Telegram channel)
* `--all` mode for the run command
* `--include-credentialed` flag for `--all`
* check-updates command
* `--tools` option for update and check-updates
* `--json` output and `--yes` / `-y` on commands
* Stable exit codes: 0 success, 1 error, 2 invalid input, 130 interrupted
* `ot` command alias
* Tools added for that release: Blackbird, Telegram Phone Number Checker, Auto Archiver, edgar-tool, instagram-location-search, Telepathy

### Fixed

* Tool name collision between a bare tool name and a subcommand
* Input type validation for `--all`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://osintverse.gitbook.io/otinstaller/changelog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.