Desktop workspace
PENTER Desktop is a security workbench rather than a chat window. The agent, target state, browser, execution queue, files and findings are meant to remain connected to the same investigation.
Treat the workspace as the engagement boundary
The workbench is designed around persistent context. Instead of copying data between a terminal, proxy, browser, notes app and AI chat, PENTER keeps the selected target and execution history close to the current agent thread.
Workbench surfaces
Agent
Target explorer
Findings
Tool catalog
Terminal / Queue
Files
Inspector
Extensions
What belongs in engagement state
| State | Why it matters | Recommendation |
|---|---|---|
| Target | Gives browser, agent and Cloud execution a common scope anchor. | Set it before active testing. |
| Browser state | Authentication/navigation state changes what the application exposes. | Keep state tied to the same engagement. |
| Findings | Candidates need provenance and verification context. | Do not promote scanner noise automatically. |
| Tool results | Results feed subsequent reasoning. | Keep raw output available while summarizing only what is needed. |
| Files / PoCs | Artifacts often outlive a single agent turn. | Store them inside the engagement workspace. |
| Extensions | MCP/custom tools can grant powerful capabilities. | Enable only what the engagement actually needs. |
Execution should stay inspectable
PENTER separates model reasoning from execution. A tool request should produce a visible action or result row, and approval-sensitive operations are checked by the desktop execution layer rather than being silently treated as already complete.
- Review the actual command or MCP tool before granting approval.
- Use the queue/terminal output as evidence of what executed rather than relying on conversational claims.
- Keep active target context visible when reviewing commands that can affect remote systems.
- Use Cloud execution only when its stricter target and command policy matches the intended action.
Files, findings and evidence
The workspace should make it possible to move from observation to verification without losing the path that produced the issue. Notes, screenshots, request/response evidence and PoCs are more useful when they remain tied to the finding they support.
Ready to get started?
Follow the setup guide, install the current approved Desktop release, and connect your account.