Architect Agent is a Windows service. This means that the service will start and run in the background. The Agent is not a desktop application and thus will not show up when you access your Windows GUI.
As the Agent is run as a service, it runs in Windows special SYSTEM space. This space is reserved for services and all other core functions running in a separate and isolated space.
When the Agent is now running and attempting to start game server processes, the processes will also be started in the SYSTEM space.
When you log in to Windows, you are logging in to a specific user account, for example Administrator. This user is not the SYSTEM user, so it does not see the console windows for game servers.
Enforce Interactive Processes
To run the game servers processes within a normal user account, the Agent can employ a Windows technique called "token duplication" to grab a token from a logged in user and then use it to start the game server processes.
This will result in the process showing up when logging into the Windows GUI and the process being run as the selected user.
It is important to note that this only works, if the user account was logged in to at least once, prior to the Agent starting. When you reboot your Windows system, and have your servers on auto start, the first time, the console will not show up when logging in. Log in once, or set up Auto-Logon, and the console will then show up.
Configuring interactive processes
[windows]
start_server_non_interactive = false
session_username = "<USERNAME>" # case sensitive
Place the snippet inside your existing config.toml. If these parameters are already defined, but commented out (# in front) then uncomment them and fill in the username. The username must be case sensitive.
If your username is Administrator, you need to write Administrator.