Getting started
Install PENTER on Windows, connect your account and complete your first authorized investigation. Docker and WSL are not required for basic setup; optional integrations have clear beta limits.
A clean first setup, without unnecessary tools
New to PENTER?
Using Docker, Kali or MCP?
Before you start
- Use a target or environment you are explicitly authorized to assess.
- Have access to the PENTER account that should own the desktop device and Cloud usage.
- You can start without Docker, Kali or MCP. The packaged public beta supports the scoped Browser/HTTP path; unconfined local command execution is restricted.
- For Browser Agent in a packaged build, allow the first-run Chromium download when prompted.
- If you plan to use optional offline Docker tools, have Docker Desktop with a working local Linux engine; this is not needed for your first Browser/HTTP investigation.
Install PENTER Desktop
Download the current Windows installer from penter.dev/download when the public channel is available. The packaged app is an Electron desktop application; the web dashboard is not a substitute for Desktop when you need scoped local Browser/HTTP tooling. Native shell and MCP processes remain unavailable in packaged public-beta builds.
- 1Download the current installerUse the official Download page after beta downloads are enabled. Check the linked version and SHA-256; do not use unofficial mirrors.
- 2Install and open PENTERRun the Windows x64 installer. The beta build is unsigned, so Windows may show a trust warning; verify the release source and checksum. Do not disable antivirus protection.
- 3Complete the five-step setup wizardThe current wizard walks through Welcome → AI → Target → Workspace → Ready, including provider/model selection, engagement name/type, target/domain and an optional local workspace folder.
- 4Start the guided tourAfter setup, PENTER can introduce the workbench surfaces before you begin the real engagement.
Create one workspace per engagement boundary
A workspace should represent one coherent authorized investigation. Keeping unrelated targets in separate workspaces makes target context, evidence, MCP configuration, browser state and agent reasoning easier to audit.
- Set the intended target or target family before asking for active checks.
- Keep the engagement authorization boundary narrower than the technical network boundary whenever possible.
- Use a new workspace when moving to a different customer, contract, environment or unrelated target set.
- Store engagement notes and PoCs alongside the workspace rather than mixing them into global state.
Run the first agent workflow
Start with a bounded objective. The agent works best when it knows the target context, what outcome you want, and whether it should inspect, plan, execute, verify or document.
Map the public application surface for this authorized target. Start with passive/basic checks, show each active command before execution, and separate observations from verified findings.The expected flow is reasoning → tool proposal → execution/approval → result → updated reasoning. PENTER should not invent output for a command that has not run.
Choose Local or Cloud execution deliberately
Local execution
For authorized targets, use the scoped Browser, HTTP and Request Lab tools. In the packaged public beta, native shell, WSL/Kali commands and MCP execution are blocked; managed Docker is offline-only.
Cloud execution
Cloud AI chat is separate from the Cloud command runner. Command execution is currently disabled server-side for the public beta, even if a command would otherwise meet the target policy.
Optional: connect Docker Desktop
Docker is not required for login, AI chat or Browser/HTTP investigations. Use it only when you need an approved, locally available image for offline tool execution. Networked containers are intentionally disabled in the packaged public beta.
- 1Install and start Docker DesktopUse Docker Desktop with the WSL 2 Linux-container backend. Wait until the app says its engine is running.
- 2Confirm the Linux Engine is reachableOn Windows, desktop-linux is the typical active context. A missing named pipe usually means the engine has not started yet, even if the CLI is installed.
- 3Pull a trusted image explicitlyFor a basic connectivity check, alpine:3.21 is a lightweight example. PENTER does not permit surprise image pulls while executing tools.
- 4Check PENTER Settings → DockerRefresh the engine status, select an approved local image and keep network=none. A stopped Docker Desktop Windows service alone does not imply the WSL2 engine is unhealthy.
docker context ls
docker context use desktop-linux
docker info --format "{{.OSType}}"
wsl --status
wsl -l -vdocker pull alpine:3.21
docker image lsDocker pipe missing, WSL setup confusion or image not found? Find the matching fix.
Updates in the restricted public beta
Packaged Windows builds can check the configured update feed, but the beta deliberately does not auto-download or auto-install updates. The update feed can also be unavailable while the public release channel is gated.
- Use the official Download page to obtain a newly approved release when available.
- Compare the installer version and published SHA-256 checksum to the release metadata.
- Do not turn off Windows protections or install from unofficial mirrors just to resolve an update warning.
- Prerelease updates and silent install-on-quit are not enabled in the current beta.
Need help with a specific error?
The troubleshooting guide has searchable fixes for device codes, provider errors, failed Chromium downloads, Docker's Windows named pipe and public-beta restrictions. The guides are for PENTER Desktop users rather than developers building the application from source.
Open setup troubleshooter →Ready to get started?
Follow the setup guide, install the current approved Desktop release, and connect your account.