Getting Started with WSHawk v4

Pick the right surface, run the desktop or CLI, and start with the local validation labs.

Getting Started with WSHawk v4

The shortest practical rule is simple:

  • use the CLI for a fast first pass
  • use the desktop for the real v4 workflow
  • use the validation labs before testing a real target

CLI Quick Start

pip install wshawk
playwright install chromium
wshawk ws://target.example/ws

The CLI is still useful, but it is no longer the whole story.

Desktop from Source

git clone https://github.com/regaan/wshawk
cd wshawk
pip install -e .
cd desktop
npm install
npm run smoke
npm start

Run the Validation Labs

./venv/bin/python validation/run_validation.py --list
./venv/bin/python validation/run_validation.py

At the time of the v4.0.0 release, the shipped labs cover:

  • full-stack realtime SaaS
  • Socket.IO SaaS
  • GraphQL subscriptions

First Useful Workflow

  1. open or create a desktop project
  2. connect a target or lab
  3. pair the browser companion if browser auth matters
  4. capture traffic
  5. replay a real action
  6. compare behavior across identities
  7. run a race if the action changes state
  8. review evidence and export