Grant Computer Access Without Surrendering Control

Hermes becomes substantially more capable when it can operate a computer, but computer control also creates the largest concentration of risk. The correct objective is not maximum access. It is enough access to perform the intended work, introduced gradually and verified before high-impact actions are allowed.

Hermes can install a computer-use package and request operating-system permissions through the desktop environment. With those permissions, it can open applications, navigate interfaces, configure integrations, and perform tasks that would otherwise require manual clicking.

Computer use gives Hermes the equivalent of a dedicated workstation. The installation process requests permissions and enables the driver needed to control the machine. The setup may require quitting and restarting the application after permissions are granted.

Troubleshooting is interactive. If Hermes reports that access is incomplete even though the system settings appear correct, the user can capture the permission screen and provide the screenshot to Hermes or the buddy agent. The agent can compare the visible settings with what it expects and guide the restart or verification process.

Access and authority are different. Computer use may give Hermes the technical ability to send email, publish content, modify files, or interact with financial applications. That does not mean those actions should immediately be allowed to run without review.

An agent with broad access can make mistakes at machine speed. One cautionary example involved an agent that received inbox access and deleted years of email. The lesson is not that agents should never receive access. It is that access should be staged, outputs should be verified, and irreversible actions should remain protected until the behavior has been tested.

The same rule applies to money movement and public publishing. An agent can draft an email, prepare a trade, or create a post before it is trusted to send, execute, or publish. This preserves most of the productivity while reducing the cost of a wrong action.

Introduce computer access in levels.

Level 1: Read and inspect. Let Hermes open applications, view calendars, inspect files, or retrieve information. Confirm it selects the correct account and interprets the interface correctly.

Level 2: Prepare reversible work. Let it create drafts, organize project issues, generate files, or assemble a website in a test location. Review the output before it affects customers or external systems.

Level 3: Execute controlled changes. Allow selected actions such as moving a meeting, posting approved content, or updating a project board after the workflow has been tested repeatedly.

Level 4: Run scheduled or goal-driven actions. Only automate a process after its permissions, outputs, timing, failure handling, and reporting are understood.

During setup, enable the computer-use driver, grant the requested operating-system permissions, restart the application, and verify with a harmless test. Ask Hermes to open a known application or inspect a visible item. Do not begin with email deletion, money movement, or public publishing.

Maintain a clear separation between tasks Hermes may complete autonomously and tasks that require review. The highest-risk categories identified in the setup are sending email, moving money, and publishing externally.

Without computer use, Hermes cannot perform many desktop tasks. With unrestricted computer use, an error can affect files, accounts, communications, or finances. More capability therefore increases the need for staged access and observable workflows.

Computer use is optional. It is appropriate when the benefit of hands-on execution is greater than the added risk and when the user is prepared to inspect permissions and intervene when the interface changes.

Give Hermes the ability to act in stages, verify it on reversible tasks, and keep destructive, financial, and public actions behind human review until the workflow has earned trust.