Docs / Console, ecosystem and developer tools / Console, Workspace, and Campaign Hygiene
GitHub

Console, ecosystem and developer tools

Console, Workspace, and Campaign Hygiene

The workspace as mission folder

Before any scan, create a named context. Everything that follows (hosts, vulns, mission history) stays attached to that workspace.

workspace create dvwa-low-2026
workspace use dvwa-low-2026
workspace list
scope add 127.0.0.1
host add 127.0.0.1 --note "DVWA local test target"
scope and host document the authorized perimeter. The agent and certain commands rely on this data to avoid off-target drift.

Manual module cycle

search --type scanner --protocol http security
use scanner/http/security_headers_detect
show options
set rhost 127.0.0.1
set rport 80
set ssl false
run
back
  • show options : required options and common values.
  • check : prerequisite validation without full action (if the module supports it).
  • back : leave the current module without closing the console.
  • reload : reload the module after code changes (development).
search wordpress --type scanner
search --cve CVE-2026-24849
search sql injection --type auxiliary --protocol http
search --type exploits --platform php --reliability high
sync now
inventory

After adding custom modules or marketplace sync: sync now.

Command reference by category

The help command with no argument displays the categories defined in the framework (help_command.py). For details on a command: help <name>. This section reproduces and comments on each category for day-to-day pentesting.

Core Commands (console core)

clearClear the display before a client demo.
exitQuit the console (background sessions: check jobs).
bannerDisplay the banner; useful for report screenshots.
agentAutonomous campaign or sub-commands doctor, explain, replay (agent campaign replay).
statusFramework state, current workspace, counters.
interpreterSwitch to integrated interactive Python shell (advanced debug).

Module Management

search [filters]Inventory modules by keyword, CVE, type, protocol.
show options|info|payloadsOptions, metadata, compatible payloads.
set <opt> <val>Configure the target (rhost, rport, targeturi).
runExecute the loaded module.
backReturn to global console context.
checkLightweight vulnerability test before full run.
reloadReload source module after editing.

Example typical session:

use auxiliary/scanner/portscan/tcp
show options
set rhosts 127.0.0.1
set ports 1-1000
set threads 50
run

Workspace & Data (mission data)

syncModule indexing (sync now) after repository update.
hostadd, list, services : asset mapping.
vulnTrack confirmed vulnerabilities linked to hosts.
historySession command traceability (audit evidence, the relevant documentation).
portalLocal web portal access for visualization (if enabled).
campaignAttack graph, executable plan, report / Navigator exports.
vuln list
campaign --preview
campaign --formats plan,report,navigator --max-steps 25

Sessions & Shells

sessions -i <id>Interact with a session.
sessions -k <id>Close cleanly after evidence collected.
shellShell management tied to the framework.
msfCompatibility bridge / Metasploit-style commands if configured.
routeNetwork routes for pivoting through active sessions.

Docker Environments

Network & Discovery

myipLocal IP useful for lhost / Docker reverse shells.
httpAssisted HTTP requests from the console.
proxyKittyProxy : start, status, interactive.
debug_proxyAdvanced proxy diagnostics (development).
scannerParallel mass scan (-u URL, --threads, --module).
torTor routing if configured (anonymization --- mandate required).
scanner -u http://127.0.0.1 --threads 10
scanner -u http://127.0.0.1 --module phpinfo_detect -v
proxy start --host 127.0.0.1 --port 8080
myip

Development & Tools

generateGenerate module / payload skeleton.
newCreate new resource (dev workflow).
detection_packDetection packs (grouped modules).
api_importImport external API definitions.
patternPattern / signature management.
syscallSyscall data (low-level modules).
compatible_payloadsList payloads for current exploit.
doctorFramework health.
inventoryIndexed module inventory.
attackMITRE ATT\CK : catalog, show, export.
labDocker test environment orchestration.
attack catalog
attack show scanner/http/security_headers_detect
attack export --format navigator --output /tmp/layer.json
doctor
lab list

Jobs & Background

jobs -k <id>Stop a job; useful in case of incident.

Collaboration

collab_connectJoin a shared session.
collab_chatTeam messaging during red team.
collab_disconnectLeave collab session.
collab_share_moduleShare custom module with the team.
collab_sync_moduleSync remote module.
collab_edit_moduleCollaborative editing.
collab_sync_editSync edits in progress.
ircIntegrated IRC channel (legacy / team).

Advanced Features

browser_serverServer for browser_exploits modules.
demoBuilt-in demonstrations.
guardianMonitoring / guardrails (depending on configuration).
scopeExplicit authorized perimeter (add, list).
marketCommunity module marketplace.
pluginConsole extensions.
resetReset selected states (use with caution).
soundAudible event feedback (optional).

Standalone tool: kittyrelay

Not invocable in the console; separate binary/script for P2P relay:

kittyrelay --host 0.0.0.0 --port 9000
# Console side:
use listeners/multi/p2p_relay
set role operator
set relay_host <hub-ip>
set relay_token <token>
run
help kittyrelay in the console displays the details.

Pivot commands for a KittySploit pentest

lab start/run/scoreOrchestration of Docker test environments.
proxy startKittyProxy: web traffic interception.
agent <target>Autonomous campaign scan → analysis → exploit → report.
sessions -lList and interact with obtained shells.
vulnTrack confirmed vulnerabilities in the workspace.
campaign --previewAttack graph and executable plan from the workspace.
attack catalogMITRE ATT\CK mapping of modules.
historyTrace session commands.
jobsModules running in the background.

Mission start routine

  1. workspace create <mission>
  2. scope add <authorized targets>
  3. doctor if fresh machine or after update
  4. lab start or manual target validation
  5. host add + context notes
  6. scanner -u for quick mapping
  7. Manual analysis of critical findings
  8. agent or targeted modules for validation
  9. vuln + concise documentation per finding
  10. campaign --preview for graph validation

This routine is the thread running through the rest of the documentation.