Zypheron

ZYPHERON

First Run and Doctor

The shortest stable path after install is: verify the binary, run doctor, install missing dependencies if needed, check tools, and run a narrow first workflow before wider automation.

Step 1: Verify the install

zypheron --version

zypheron doctor

Step 2: Install Python-side dependencies if needed

zypheron install-deps --all

Step 3: Check your tool inventory

zypheron tools check

zypheron tools list

zypheron tools list --missing

Step 4: Install critical tools if you want Zypheron to manage them

zypheron tools install-all --critical-only --yes

Step 5: Run a first workflow

zypheron

zypheron scan example.com --web

zypheron recon example.com

Why doctor matters

The repo positions zypheron doctor as the fastest way to validate runtimes, config, and environment health before you start debugging manually or widening the workflow.

Why start narrow

A narrow first run gives you better signal than a large chained workflow if your environment is still incomplete or you want tighter operator review.

Once your first-run checks are clean, the repo’s next useful commands are zypheron dork "admin panels" --ai-guided, zypheron chat "How would you approach this host?", zypheron workflow list, and zypheron autopent example.com.

ZYPHERON

ZYPHERON Desktop is a cybersecurity IDE for offensive and defensive workflows. The open source CLI remains available for terminal-first users.

AUTHORIZED USE ONLY

Infrastructure

Network

© 2025 ZYPHERON SYSTEMS//DESKTOP + CLI