IR
irwinrodriguez.dev
ES EN DE
Back to docs

Installation

Download

Download the FoxAgent installer for Windows:

Download FoxAgent

Windows x64 · Requires administrator · Create your free account and download the latest version from your portal, no credit card.

FoxAgent is digitally signed

Since 1.62.7, FoxAgent.McpHost.exe, FoxAgent.Broker.exe, FoxAgent.Bridge.dll, the command-line tools and the installer carry a publisher signature in the name of Irwin Alfredo Rodriguez Gimenez, with a timestamp. To see it: right-click the file → Properties → Digital Signatures, or run Get-AuthenticodeSignature in PowerShell, which must say Valid.

  • SmartScreen: the certificate is new and Windows may still warn for a while. If “Windows protected your PC” appears, click More info: it must say Publisher: Irwin Alfredo Rodriguez Gimenez. If it does, Run anyway; if it says “Unknown publisher”, that file is not ours: do not run it.

Before you install

The FoxAgent installer is signed, but the certificate is new and Windows may still warn you the first time you run it. Here is what you will see, how to continue, and how to check for yourself that the file you downloaded is exactly the one we published.

The SmartScreen warning

If a blue window saying “Windows protected your PC” appears when you run it, click “More info” and look at the publisher: it must be Irwin Alfredo Rodriguez Gimenez. The warning does not mean there is anything wrong with the file: it means Windows has not yet seen enough downloads with this certificate to recognize it.

  1. Click More info.
  2. Click Run anyway.

Before that second click, check the hash: that is how you know what you are about to run is ours and not an altered copy.

If your antivirus stops it

Some antivirus products quarantine installers they rarely see. If that happens, add an exclusion for the installation folder, C:\Program Files\FoxAgent, and run it again.

If the antivirus belongs to your company and you cannot change its rules, give the SHA-256 below to whoever administers it: that is what they need to clear the file.

Check what you downloaded

These are the details of the current version and the day it was published. The hash is computed on the file exactly as the portal serves it:

FileVersionPublishedSizeSHA-256
FoxAgent-Setup-1.65.4.exe 1.65.4 18 Oct 2026 63.5 MB 7A63BFBC94CE971D0A8387786EA16DC7B772CF9E168B7E38185068078F788B51

To check it, open PowerShell in your downloads folder and run:

Computing the SHA-256 of the downloaded file
Get-FileHash -Algorithm SHA256 "$HOME\Downloads\FoxAgent-Setup-1.65.4.exe"

If the value matches the table, the file is ours and intact. If it does not match, do not run it: download it again and, if it still does not match, write to soporte@irwinrodriguez.dev.

Hashes are measured again for every published version. If you downloaded an earlier version, its hash will not necessarily match this table.

System requirements

  • Windows 10 or 11 (x64), or Windows Server 2016 or later
  • .NET Framework 4.8, which FoxAgent.Bridge needs because it is COM. It is the only thing you must already have installed
  • Visual FoxPro 9.0 SP2, or VFP Advanced 10 or later, on the machine you develop on

The Broker and the McpHost are self-contained: they carry their runtime inside and no separate .NET has to be installed. That is why the installer only checks for .NET Framework 4.8, and offers to download it if it is missing.

What the installer does

These four things, without asking more than it has to:

  1. Installs the components
    • FoxAgent.Broker.exe: the registry of connected instances
    • FoxAgent.McpHost.exe: the one that speaks MCP to your AI client
    • FoxAgent.Bridge.dll: the COM bridge that lives inside your VFP process
    • The SDK\: both base classes, the template and the examples
  2. Registers the Bridge as a COM component
    • So VFP can create it with CREATEOBJECT("FoxAgent.Bridge"). The RegAsm it uses is the .NET Framework 4.x one, not the modern .NET one.
  3. Installs the Broker as a Windows service
    • The FoxAgentBroker service is left on automatic start and is started there and then. You can see it in services.msc.
  4. Configures your AI client if it finds one
    • It configures Claude Desktop and OpenCode if they are installed. For the others it leaves the MCP block ready, with the real path already filled in, at C:\Program Files\FoxAgent\mcp-foxagent.json. An MCP client is not optional: without one there is no agent.

Check the installation

After installing, check that the service is running:

Checking that the Broker service is running
# In PowerShell or CMD:
sc query FoxAgentBroker

# It should say: STATE: 4 RUNNING

You can also open services.msc and look for "FoxAgent Broker" in the list.

Installation folder By default FoxAgent installs into C:\Program Files\FoxAgent, without the (x86): the Bridge is x86 because it lives inside VFP, but the installer itself runs in 64-bit mode. The SDK is in C:\Program Files\FoxAgent\SDK.

Startup order

Always in this order. If you open your AI client before your application has registered, it will see no instances.

  1. FoxAgent.Broker: Windows service, automatic start
  2. Your VFP application: registers with Connect()
  3. The MCP client: Claude Desktop, Claude Code or any other

Evaluation mode

With no license file, FoxAgent runs in evaluation mode: one VFP instance and one custom tool. The 55 built-in tools are unlimited. It does not expire and asks for no card.

Your machine ID

The Developer license is tied to the machine you develop on, so the purchase asks for its ID: 16 hexadecimal characters. Any of these three gives it to you.

Three ways to get the machine ID
# 1. From the command line
"C:\Program Files\FoxAgent\FoxAgent.Broker.exe" --machine-id

# 2. From the browser, with the service running
http://localhost:7400/license      -> "machineId" field

# 3. With restart-broker.cmd, which prints it when it finishes

Dashes and letter case do not matter: paste it into the checkout exactly as it comes out.

Installing your license

  1. Download the .lic file from your license detail page in the portal.
  2. Save it as foxagent.lic next to FoxAgent.Broker.exe (case does not matter). Anywhere else will not be found, and if it downloaded as foxagent (1).lic or foxagent.lic.txt, rename it.
  3. Run restart-broker.cmd as administrator. The Broker reads the license only at start-up: copying the file in is not enough on its own.

The script queries http://localhost:7400/license itself and reports the result. Look at the mode field:

ValueWhat happened
"Licensed"Your license is active
"Evaluation"It was not picked up: check the file name and that it sits in that folder
"MaintenanceExpired"The license is valid, but this build is newer than your maintenance covers. Meanwhile it runs with the evaluation limits: install the previous build, or renew and replace the .lic
"LicenseExpired"The 30-day trial ran out. FoxAgent still starts, with the evaluation limits, and that same output carries your machineId so you can buy
Changed machine? The license only starts on the machine it is bound to. If you have changed computers, write to me and I will reissue it.

Next steps