Let an AI agent such as Claude Code reach, watch and control your systems, including machines behind a firewall with no public address. Setup has five steps, all on the AI Agents screen, which fills in your account details for you.
Before you start
Admin access, to create an API key.
A machine where your AI agent runs, with outbound internet access.
A decision about which systems the agent may reach and what it may do there. Both are set on the API key. See Create and use capability policies.
Step 1 - Create an automation API key
Go to Admin > API Keys and click Actions > Create key.
Set Type to Automation.
Under System access, add a rule for the systems the agent may reach, and choose a capability policy. Approval for risky is a safe start.
Click Create and copy the API key.
NOTE: The API key is shown once. If you lose it, create a new key.
For every field, see API keys and their permissions.
Step 2 - Install the hv CLI
Install the CLI on the machine where your agent runs, not on the systems it will control.
On AI Agents, under Step 2, choose Linux, macOS or Windows.
Copy the command and run it on the agent's machine.
For Step 3, below.
Step 3 - Sign the CLI in
Copy the
hv auth logincommand under Step 3. Your account UUID is already in it.Run it on the agent's machine and paste the API key from Step 1 when asked.
Run
hv auth statusto check it worked.
Step 4 - Give your agent the HyperView skill
The skill tells your agent the hv CLI exists and how to use it. Without it, the agent won't use HyperView.
Choose your agent: Claude Code, Cursor, Windsurf, Cline, Aider, Codex CLI, Gemini CLI, or Other.
Copy the install command and run it in your project.
This line shows where the skill is written.
To install it yourself instead, download the skill file.
For more options, see Install the HyperView skill for your agent.
Step 5 - Test it
Ask your agent something simple first:
"What systems do you have access to with the HyperView skill?"
This checks the whole chain (key, CLI, sign-in and skill) without changing anything. Then try something real:
"Take a screenshot of system windesktop12."
"Use HyperView to debug why the RDMS service is failing to start on the system with IP 10.0.2.1."
Check it worked
The agent lists your systems when asked.
Admin > Activity Log shows the agent's actions with an Actor Type of
api_key.
If something doesn't work, see Automation isn't working.

