HackersGhost AI CLI is a memory-aware terminal assistant I built for my own ethical hacking lab.
It exists because I wanted speed without losing awareness, and assistance without breaking OPSEC.

This tool runs locally on Linux and lives entirely in the terminal.
It does not automate attacks.
It does not make decisions for you.
And it does not pretend that AI equals safety.

What it does is simple and dangerous at the same time: it remembers what you explicitly allow it to remember.

Free v1 Release 📦

This page hosts the first public release of HackersGhost AI CLI.
Version 1 is intentionally limited and intentionally free.
It is meant to be explored, understood, and questioned.

You bring your own environment.
You bring your own API key.
You bring your own discipline.


Download HackersGhost AI CLI v1 (ZIP)

Changelog

v1.0

  • Initial public release
  • Linux terminal-based AI assistant
  • Explicit user-controlled persistent memory
  • Manual memory actions: append, search, summarize, clear
  • Optional ethical Red Team mode
  • No automated execution
  • No hidden storage
  • No embedded credentials

This version is intentionally limited.
Behavior is explicit.
Responsibility remains with the user.

What’s Inside 🧩

  • A Python-based AI CLI designed for Linux
  • User-controlled memory with explicit append, search, summarize, and clear actions
  • Optional ethical Red Team mode with strict boundaries
  • No hardcoded secrets, no hidden storage

Quick Start 🧪

HackersGhost AI CLI is meant to run inside a Python virtual environment.
Skipping that step usually ends in confusion.

Create and activate a virtual environment

python3 -m venv .venv
source .venv/bin/activate

Install dependencies

python3 -m pip install -U pip
python3 -m pip install -r requirements.txt

Set your API key

export OPENAI_API_KEY="your-key-here"

Run the CLI

python3 hackersghost_ai_cli.py

OPSEC Reality Check ⚠️

This tool does not make you anonymous.
It does not protect you from bad habits.
If you paste secrets, credentials, or real identifiers into any AI system, that is your responsibility.

Local memory can still leak through logs, backups, screenshots, and human error.
If a secret was exposed, rotate it.
Immediately.

Lab Context 🧫

In my own setup, HackersGhost AI CLI runs inside a controlled lab.
A Parrot OS attack machine.
Windows 10 victims.
Isolated virtual machines.
No overlap with daily systems.

That separation is not optional.
It is the reason this tool remains useful instead of reckless.

HackersGhost AI CLI v2 — What’s Coming 🧠

While using v1 daily, some limitations proved to be features.
Others revealed where the tool could become safer and calmer without becoming more aggressive.
Those ideas are shaping v2.

Planned for v2 🔧

  • Separate memory scopes so notes never bleed into each other
  • A read-only memory mode for sensitive sessions
  • Cleaner exports for reports and write-ups
  • Optional OPSEC guardrails that warn instead of blocking
  • A small configuration file instead of hardcoded behavior

Nothing in v2 will automate attacks.
Nothing will remove responsibility.
And nothing will turn this into a shortcut machine.

Pricing Philosophy 💭

Version 1 stays free.
Version 2 will be pay-what-you-want.

No licenses.
No subscriptions.
No accounts.

If it saved you time, helped you think more clearly, or prevented a mistake, you decide what that was worth.

HackersGhost AI CLI will remain a tool, not a product pitch.