ZYPHERON
One workspace, not disconnected security tools
ZYPHERON Desktop is built around practical operator flow: recon, terminal execution, reverse engineering, and AI assistance in one workspace. Automation stays human-in-the-loop, with the CLI still available for terminal-first work.
Three Layers of the Current Product Experience
This page reflects the current public framing: desktop workspace first, open source CLI second, and operator-controlled workflow context across the assessment.
CLI and TUI
Launch with zypheron or zypheron tui, then drive scan, recon, dorking, and chat flows from the terminal with the operator deciding what runs next.
AI Assistance
Use local Ollama or hosted providers through Zypheron config. The repo docs emphasize provider-aware setup and operator review, not vague autonomous claims.
Local State and Workflows
Sessions, loot, config, and artifacts are stored locally under ~/.zypheron, with workflow-oriented commands like workflow list and autopent staying inside an operator-controlled environment.
Where Automation Helps and Where the Operator Stays in Control
These are the workflow surfaces the website can claim directly because they are already documented in the current repo.
Recon and Scanning
The repo README foregrounds scan, recon, AI-guided dorking, and workflow execution. This is where pentest automation helps, with the operator still setting scope and reviewing output.
zypheron scan example.com --web
zypheron recon example.com
Doctor and Install-Dep Flows
The modern setup story is not "figure it out manually." It is bootstrap, run doctor, install dependencies, and verify tools before wider automation.
zypheron doctor
zypheron install-deps --all
zypheron tools status
MCP Integration
The repo frames MCP around generated config and lifecycle commands: config, start, stop, and status. It is an operator workflow, not an autonomous black box.
zypheron mcp config
zypheron mcp start
Open Source CLI Core
The repo is MIT licensed. Trust should come from real install paths, local-first behavior, and command-level transparency, not novelty AI language.
MIT License
setup-hybrid.sh
download.zypheron.net/install.sh
What the website should emphasize
Install cleanly through the repo-backed source bootstrap or release installer.
Run doctor and install-deps early so the environment is verifiable.
Treat AI as a provider-aware layer on top of terminal workflows, not as a replacement for operator judgment.
Use human-in-the-loop, semi-automated, local-first, and operator-controlled language where trust matters.
Keep the docs aligned to install, setup and use, AI guide, MCP, tool chains, and help.
$ zypheron workflow list
bug-bounty-recon
web-scan-core
local-ai-review
$ zypheron session list
Stored locally under ~/.zypheron/sessions
Operator state remains on your machine unless you choose otherwise.
Continue with the CLI docs set
The strongest website content comes from mirroring the repo docs cleanly, then layering examples and walkthroughs on top.