Every HyperView term in alphabetical order, with a link to the article that covers it.
For the same terms grouped by subject rather than alphabetically, see Concepts and vocabulary.
Term | Definition |
Access rule | The pairing on an API key of a set of systems with the capability policy that applies there. Checked top to bottom; first match decides. 9.2 |
Alias | The name you give a system in the console, as opposed to its hostname. 3.2 |
API key | The credential a script or agent signs in with. Its access rules decide which systems it can reach. 9.2 |
Approval | A human decision permitting a key to use a gated capability on a system. Scoped to the key and the system, not to the session. 9.4 |
Automation Enabled | The account-wide kill switch for all automation. 9.3 |
Automation session | A session opened by a script or agent rather than a person. Billed identically. 8.1 |
Capability | What a session may do on a target system, such as a screenshot, shell command or file write. Eighteen exist, six risky. 6.6 |
Capability policy | A named set of per-capability decisions (Allowed, Guardian, Human approval, Denied) attached to an access rule. 6.7 |
Connection mode | How a session behaves: Connect, View only, Admin (shared), Admin (stealth) or Group share. 3.4 |
Conflicted | System status indicating an identity conflict, usually a fingerprint mismatch. 2.8 |
Console | The HyperView web app. Orchestrates systems; never contacts them directly. 1.1 |
Default share | Access record created automatically at registration so a new system is immediately reachable. 2.4 |
DesktopAgent | The lightweight, temporary HyperView Server used for remote support. Deletes itself when the session ends. 5.1 |
Fingerprint | How a system identifies itself as the same system across restarts. Mismatches cause re-registration. 2.8 |
Folder | The account's primary segmentation. One per system. Drives filtering and usage attribution. 3.2 |
Guardian | An AI reviewer for capabilities set to Guardian. Approves, denies, or escalates to a person, judging against the account mission. 9.3 |
Guided tour | A step-by-step walkthrough of a screen, started from Show tour. 1.4 |
Heartbeat | The regular check-in from a HyperView Server. Drives the status dot. 3.1 |
hv | The HyperView command-line tool, wrapping the automation API. 6.4 |
Installation key | Decides how systems installed with it are set up: folder, owner, version and server settings. 2.4 |
Overage | Session hours consumed beyond the plan bundle, billed at an hourly rate. Cappable. 8.4 |
Owner | The user accountable for a system, installation key or API key. 9.1 |
Permission | What an API key may do in the console, as opposed to on a system. 9.2 |
Private venue | A venue your own account hosts, rather than a shared one. 9.6 |
Recording | A captured task on a system (actions, screenshots and narration) for reuse as documentation. 7.1 |
Rollover | Unused plan hours carried into a later period. 8.4 |
Session | A human or automated caller connected to a system. The unit of billing. 8.1 |
Session state | What the desktop on the system is doing: logged_in, locked, logged_out, screensaver, switching_user or unknown. 3.3 |
Session viewer | The browser tab a session runs in, with the toolbar for the clipboard, file transfer and session settings. |
Share link | A URL that gives someone a session in a set mode, without a console login. 3.4 |
Skill | A file telling an AI agent that the hv CLI exists and how to use it. 6.3 |
System | A machine registered with your console. 1.2 |
System access | Which systems an API key may reach, set by its access rules. Systems no rule matches are denied and invisible to the key. 9.2 |
System type |
|
Tag | Free-form label on a system, |
Venue | A distributed relay that brokers the connection between console and system. 9.6 |
Virtual video driver | Optional driver that sizes the remote desktop to the browser window and compresses the screen it sends. 2.6 |