Getting Started with GUIDE

Prev Next

Overview

GUIDE allows AI packages like Anthropic’s Claude to use the keyboard and mouse on a Windows system to operate programs directly. Most AI agents can only use programs or Web sites with an API interface: they can’t use human-oriented user interfaces. GUIDE can and does. This not only broadens the range of tasks that can be performed, it approaches the tasks in the way that is more familiar to human operators.

How it Works

While GUIDE runs an “Agent” (a set of instructions you provided it), it first parses your instructions and shows you its interpretation of what you’re asking for, usually with greater detail than you provided. During operation, GUIDE logs screen shots of each step and reports what it’s thinking and what it’s trying to do, allowing you to verify its operation.

GUIDE It also verifies the output of each step itself, making corrections automatically if a step didn’t deliver the desired result. It thus adjusts to circumstances as it runs.

Terminology

In the context of GUIDE:

  • GUIDE (capitalized) is the AI enhancement package.

  • Development system. A Windows device running GUIDE.

  • An Agent (capitalized) is an Agent created and run under GUIDE. (AI agents in general are not capitalized.)

  • Agent system. A Windows device running GUIDE Agents. This can be a different system from the development system.

  • Remote device or remote system.

Implementation

GUIDE is implemented as an application that runs on Microsoft Windows. It makes API calls to cloud-based AI engines such as Anthropic’s Claude. (It currently does not support locally hosted AIs.)

GUIDE’s Agents can run locally on the GUIDE development system (the same system on which GUIDE is installed), or on a remote Agent system, where GUIDE controls the Agent via RDP (remote desktop protocol) session. When running, the Agent takes over the keyboard and mouse, and the maximum supported screen resolution is 1280x800 pixels. Running Agents on a remote Agent system is recommended except for brief periods of testing.

  • You create GUIDE Agents on the development system and run them either on the development system or a remote Agent system.

  • You can publish Agents so other members of your team can use them, and they can publish Agents that you can use.

  • The development system is a Windows device with Internet access (the underlying AI’s API must be accessible).

  • The remote Agent system, if present, is a Windows device that is accessible via Remote Desktop and has access to the Internet. The remote Agent system is optional.

Current and Recent Releases

Current Release

GUIDE 1.0.5.

GUIDE 1.0.5

Highlights

  • Released on April 30, 2026.

  • Increased execution speed.

  • Support for Microsoft Login (in addition to Google Login).

  • The default number of iterations has been increased from 20 to 50, allowing simple Agents to run without interruption.

  • Many bug fixes and UI improvements.

GUIDE 1.0.4

Highlights

  • The maximum number of iterations you can specify has been increased to 300.

  • Support for AWS Bedrock models in addition to Antropic. Users of a paid plan can choose their own models. Users of the free plan should contact Workspot if they need an alternate model.

  • Many UI improvements and bug fixes.

GUIDE 1.0.3

First production release.

Installation

Installation always involves choosing or creating a Windows system to serve as a development system, then optionally configuring a remote Agent system.

Prerequisites

Development System and Agent System

  • Windows.

  • Internet Connection (Required for AI model access and agent execution).

Simplest Installation

This uses your usual Windows system as both a development system and the Agent system.

Important: Keep in mind that an Agent controls the mouse and keyboard and you must reduce your monitor’s display to 1280x800 or less while it is running.

Follow the instructions in Installation Steps for the Development Machine.

If you have access to multiple Windows devices, we recommend using one of the following:

  1. Instead of using your main Windows device for GUIDE, install GUIDE on a remotely accessible system and use it as both development system and Agent system. The installation procedure is the same as a local installation: Installation Steps for the Development Machine

  2. Install GUIDE on either your main Windows device or a different one and use a separate Windows system as your remote Agent system.

    1. For the development system, follow Installation Steps for the Development Machine.

    2. For the remote Agent system, follow Remote Agent VM Setup.

Installation Steps for the Development Machine

Download GUIDE

You can download GUIDE from the GUIDE Management portal or directly via a link.

Download GUIDE from the GUIDE Management Portal

User profile menu showing download option and administrator role information.

  1. In a browser (Edge and Chrome are the browsers that have been tested), go to the GUIDE Management Portal at https://manage.runguide.ai.

  2. Sign into your work account using Google authentication.

  3. Click the My Account icon in the upper right corner.

  4. Click “Download” to download the installation files, which come in a ZIP archive with a name like “GuideUserSetup_1.0.4.zip.”

  5. Inside the ZIP archive is a GuideSetup.exe (and also this document and GuideRuntimeInstaller.exe, which is used for remote Agents).

  6. Launch GuideUserSetup (you can do this from inside the ZIP archive, without extracting it first), and install Guide in the usual way, as shown below.

  7. During this process, you can customize the following settings (only “Add to PATH” is enabled by default).

    1. Installation location (“C:\Users\username\AppData\Local\Programs\Guide\”).

    2. Name of the Start File shortcut (default is “Guide”).

    3. Create a desktop icon

    4. Add “Open with Guide” to the Windows Explorer file/directory context menus.

    5. Register Guide as an editor for default file types.

    6. Add to PATH.

If you are instructed to use a download link instead of the GUIDE management portal:

  1. In a browser, use the link to download the GuideSetup.exe installation program.

  2. Launch GuideSetup.exe and install it in the usual way, as shown above.

Configure the Development Machine

Signing In

Sign-in page for Guide with options to continue using Google or Microsoft accounts.

  1. Launch Guide.

  2. Wait for “Continue with Google” and “Continue with Microsoft” to appear.

  3. Sign in using your work account using one of these providers.

  4. The left-hand pane will display GUIDE options.

Left-hand Navigation Pane

User account settings with options for agents, settings, and help features displayed.

The left-hand navigation pane is the starting point for GUIDE activities divided into the following sections:

  • Agents. Lists the Agents you’ve defined, with icons for changing their settings. Your published Agents (ones shared with your team) are listed separately.

  • Agent Runs. Results of your recent Agent Runs.

  • Settings:

    • Global Settings: Logfile directory, model configuration, display resolution, and max. number of iterations before timing out.

    • Runtime Settings. Creates remote Agent configurations (the built-in local configuration isn’t configurable). See Remote Configuration.

  • Help & Feedback:

    • Getting Started. This document.

    • What’s New. Latest announcements and updates (on Slack).

    • Community. The Workspot GUIDE community (on Slack).

    • About. Reports the GUIDE release number.

  • Account: Identifies the username, email, user role (Administrator, Builder, User), and the GUIDE plan that’s in force.

  • Sign Out. Signs you out and returns you to the sign-in page.

The pane is quite tall and will usually require scrolling to reveal the full “Account” section. Scrolling may be required within the individual sections as well.

Configure Global Settings

Go to “Settings > Global Settings”:

  • Agent Folder: Where your agents are stored. (Defaults to “C:\Users\username\AppData\Local\guide\”.)

  • Model: The AI model used by your Agents by default.

    • Claude Opus 4.6 is the default and recommended model as of GUIDE 1.0.5.

    • You can override this on a per-Agent basis as desired.

    • We recommend trying different models.

  • Display Resolution (Important)

    • Must match the actual resolution of your display or RDP connection (your Agent will not run otherwise).

      • The maximum resolution is 1280x800 pixels.

      • If running on your local system, change your display resolution before running your Agent.

      • If running with a remote configuration, the resolution will be set automatically.

      • Set your desktop background to a solid color with no wallpaper (wallpaper confuses Agents).

Creating Your First Agent

Creating an agent named 'Hello, World!' with workflow instructions in a software interface.

  • Click the “+” symbol in the “Agents” section on the left-hand pane.

Create a Workflow

  • Fill in the Build page in the Create Agent tab:

    • Give the Agent a name.

    • Create a “Workflow,” by describing what the Agent is supposed to do. This will be parsed and turned into a more precise step-by-step version that you can review and edit as needed.

    • Click “Generate Steps.”

    • GUIDE will generate detailed steps from your Workflow and display them in a new right-hand pane.

Instructions for opening Notepad and saving a file in Windows environment.

  • On the right-hand pane:

    • Review the expanded steps. Note that only your original Workflow is editable at this point.

    • Click “Go To Agent.”

    • This takes you to the “Agent” page.

Note: Instruct your Agent to save its answer to a file. It does not do this by default, nor does it report its result in its step-by-step narrative.

Edit and Run Your Agent

Instructions for opening Notepad and typing 'Hello, World!' in a document.

  • Once in the Agent page, you can edit the steps and run the whole Agent or just selected steps.

  • To run the Agent, click “Select All” and then “Run.”

  • To run selected steps, select the step in question and then click “Run.”

    • Selecting random steps may have random results.

  • If you are asked to type in the value of a variable, do so:

Interface displaying runtime variables with a security warning about sensitive information.

How the Agent Runs

Screenshot showing Notepad with 'Hello, World!' and runtime output details on the side.

  • Guide now runs the Agent to completion if it can.

  • Its actions are broken up into “Iterations,” the amount of work it can do as a unit.

  • With each iteration, it uses screenshots and its instructions to decide what to do next.

    • It presents its thoughts in the right-hand pane, along with links to each iteration’s final screen shot.

  • If there was a problem with the previous iteration, the Agent figures out what went wrong and tries again. It can often solve problems on its own after no more than a few attempts.

Quick Fix Suggestions

Analysis report showing repeated filename field errors and suggested fixes for improvement.

  • Once The Agent is done, it gives a “Run Analysis” and an option to “Get Quick Fix Suggestions.”

    • If the run was successful, the Quick Fix Suggestions are to make future runs execute more efficiently.

    • If the run was not successful, the Quick Fix Suggestions are to make future runs successful.

  • To accept the fix, click “Apply to Step.”

Instructions for using Ctrl+A to replace text efficiently in a document.

Editing the Agent

Use the pencil icon to the left of the Agent’s name in the left-hand pane to edit the Agent or its variables.

Using Variables

The “Variables” button near the top of the Agent editing screen will show the variables defined for this Agent and allow you add more or edit or delete existing ones.

Two variables, “current_datetime” and “os_platform,” cannot be edited or deleted. These are the current date and time and the operating system architecture, version, and build.

Publishing the Agent

Form for publishing an agent with details like name, workflow, and settings.

When editing or running the Agent, there is a “Publish” button near the top of the screen. Clicking it will publish the Agent for the rest of your team. It pops up a page first, in case you want to change some of the Agent’s fields.

Runtime Configuration

Settings page displaying Runtime Settings for agent configuration options and environments.

The runtime settings tell GUIDE whether to run locally or remotely, which AI model to use, the maximum number of iterations (steps) to user, and more.

To see and modify the runtime configuration:

  1. Open the GUIDE sidebar

  2. Under “Settings,” click “Runtime Settings.” This opens the “Runtime Settings” tab.

The installation has a “Default local Config” that can’t be edited. You can add more runtime configurations with the “+” button at the top of the page.

Default Local Config

  • Named Default Local Config.

  • Cannot be edited or deleted.

  • Used for local execution only.

  • All new agents inherit it automatically.

Adding New Runtime Configurations

To add a new runtime configuration, Click “+” in the “Runtime Settings” tab.

Local Configuration

Configuration settings window showing fields for name, description, and execution type.

A local configuration is shown above. It will run on the same system that GUIDE is running on.

It includes the following fields:

  • Configuration Name. Your choice of a name for this runtime configuration.

  • Description. An optional description field.

  • Execution Type. “Local Computer.”

Remote Configuration

Configuration settings for remote computer access including IP address and credentials.

When you select “Remote Computer” instead of “Local Computer,” you get a remote runtime configuration. When you select a remote runtime configuration for an Agent, it will run on the specified remote machine.

  • Runs agents on a remote Windows device using the Remote Desktop Protocol.

  • Make sure the remote device is accessible from the local GUIDE machine via RDP (that is, make sure you can sign in via Remote Desktop Connection).

  • Your RDP Credentials will be securely stored in Windows Credential Manager.

  • Do NOT delete credentials manually.

The configuration has these parameters:

  • Configuration Name. Your choice of a name for this runtime configuration.

  • Description. An optional description field.

  • Execution Type. “Local Computer.”

  • IP Address. This can either be the remote device’s IP address or its hostname.

  • Port. Currently fixed at 3389.

  • Username, Password. The credentials used to sign into the desired account.

  • Restart remote computer before execution. Disabled by default, not generally recommended.

Running Agents Remotely

Install the Remote GUIDE Runtime

License agreement screen for Guide Runtime Setup with acceptance checkbox and options.

Follow these instructions to prepare the remote Windows PC or VM for the GUIDE Runtime:

  1. RDP into the remote Windows device VM, using an admin account.

  2. Download or copy the GuideUserSetup Zip archive to the remote device.

  3. Extract the files from the Zip archive. We will be using GuideRuntimeInstaller.msi.

  4. Run the installer.

    1. Double-click the GUIDE Runtime Installer.

    2. Accept the terms and click on Install.

  5. (Optional) Navigate to Control Panel\Programs\Programs and Features and check the version details, such as the release number.

Details of the Guide Runtime application including publisher and installation information.

Switching Runtime at Execution Time

Once you have multiple runtime configurations, you can choose which one to run at execution time.

  1. In “Step” view, click the dropdown next to “Run.”

  2. Select which runtime to use for the current execution.

  3. This does not alter the Agent’s default runtime.

GUIDE Runtime Troubleshooting

GUIDE Runtime Logs

You can find the GUIDE Runtime logs at installation location in the “C:\ProgramData\GUIDE” folder.

File directory showing Guide folder with GuideRuntimeService.log document details.

Uninstall GUIDE Runtime

Uninstall normally from Control Panel.

Update the GUIDE Runtime

Uninstall the old GUIDE Runtime first, then install the new version.