The fix ended up being to open up SSMS, right-click on SQL Server Agent, go to Properties. Then on the Connections tab, write in the name of the virtual SQL Server.
It may be that the Cluster Manager is the proper way to start the Agent. But due to the weird way the customer set up my access, I didn’t have access to Cluster Manager.
Agent named pipes provider could not open a connection to sql server
sqlserveragent could not be started local