PenterDocumentationCloud AI and what it can do.
Cloud / Availability

Cloud AI and what it can do.

PENTER Cloud AI and remote command execution are separate features. Here is what you can use during the public beta, how your account applies, and what to do if a request is unavailable.

01 · Overview

Cloud AI isn't the same as remote scanning

FeatureWhat it means
Cloud AI chatYour account can access supported hosted AI models and agent reasoning when the service and plan allow it.
Desktop Browser & HTTP toolsScoped, local Desktop tools inspect an authorized target under PENTER execution controls.
Cloud command executionRemote security-tool commands are a separate capability. This runner is not enabled for the public beta.
A Cloud CLI unavailable error is not an account setup failure
A beta safety gate may intentionally prevent Cloud command execution. You can still use available Cloud AI chat and the scoped Desktop Browser/HTTP tools independently.
02 · Beta

Which execution features are currently supported?

Use PENTER Desktop's scoped Browser, HTTP and Request Lab for authorized target-facing work. Native shell, WSL/Kali command execution, MCP execution and networked managed Docker are disabled in packaged public-beta builds while destination-scoped controls are evaluated.

  • Set your active authorized engagement target before using Browser or HTTP tools.
  • Review approvals and inspect actual tool results rather than trusting an AI summary of an unexecuted step.
  • Keep managed Docker containers offline with network=none if you choose to use that optional feature.
  • Do not attempt to bypass a blocked feature or scope restriction.
03 · Account

Models, plans and usage

Your available hosted models and usage depend on your PENTER account and any active plan allowances. Visit the dashboard to check current model access and recent usage. Cloud AI messages may be sent to the configured provider; avoid including secrets or unauthorized customer data in prompts.

View usage · Manage devices · Understand agent models

04 · Troubleshooting

If your Cloud request fails

Cloud AI says the selected model is unavailable.
Try another model your account supports and check your usage. Keep the exact error code or request ID for support without sharing tokens.
Remote command execution returns unavailable.
The Cloud command runner is intentionally disabled for the current public beta. Use scoped Desktop Browser/HTTP tools for authorized investigations.
The service says my device is unauthorized.
Reconnect the Desktop device using a new authorization code and check Dashboard → Devices.
Can I use Cloud commands against private networks?
The current Cloud runner is not available in the public beta. Do not try to route local/private systems through another destination to bypass restrictions.

More step-by-step help is available in the Troubleshooting guide.

Next step

Ready to get started?

Follow the setup guide, install the current approved Desktop release, and connect your account.