Engee documentation

Connecting using Engee usage.Integrations

Engee.Integrations connects the work environment Engee with supported local files, interfaces, protocols and hardware. Technical messages use the name Engee Device Manager (EDM). For communication, you need the server part in the session Engee and a client on a computer that has local resources available.

Connecting Engee MIND to the AI client does not launch EDM automatically. For regular modeling without local resources, the Engee program.Integration is not required.

Communication scheme

ИИ-агент → Engee MIND → сессия Engee / сервер EDM
                                      ↕
                           клиент EDM на компьютере
                                      ↕
                        локальные ресурсы и оборудование

Preparation

Specify the operating system, the target computer, the installation directory, and the connection task. The client EDM must work on a computer that has access to the necessary resources. The agent needs the means to work with this computer or the user’s participation in local steps. Remote chat by itself does not access the processes of your computer.

First connection

  1. Open the agent client on the appropriate computer and connect Engee MIND.

  2. Send a request for full training Engee.Integration.

  3. The agent will upload engee_integration_start, will check Engee and prepare the server side.

  4. The agent will get links to the client and the current connection from the response itself Engee. If you perform local actions manually, use only the link and the parameters obtained in this run.

  5. The client is loaded into the selected directory, unpacked and launched with the address of the current connection. For Windows, the standard skill catalog — C:\engee, unless another is specified.

  6. The agent checks that the client process remains running and performs a test socket creation in full mode.

  7. The final message should contain the mode, the client path, the status of the process, the result of the connection and the way to stop.

Example:

Используй engee_integration_start. Подключи Engee.Интеграции на этом Windows-компьютере в полном режиме, каталог `C:\engee`. Подтверди связь с текущей сессией проверкой тестового сокета. После подключения сообщи состояние и способ остановки клиента. К устройствам пока не обращайся.

If the agent does not have local tools, ask to issue the received from Engee download and run the steps and run them on the target computer. Do not use the connection link from the old session: it should refer to the current session.

Reconnecting

For an already installed client, you can explicitly request fast mode:

Подключи Engee.Интеграции в быстром режиме, используй установленный клиент по указанному мной пути. Затем проверь состояние через engee_integration_status.

Fast mode does not check for updates, does not download the client, and does not check the socket. If the fast mode conditions are not met, the skill provides for a transition to full training. The agent must report the mode actually used and the missed checks.

Checking the status without running

Используй engee_integration_status. Только проверь состояние: не запускай сессию, не устанавливай пакет и не перезапускай клиент.

The skill returns the following fields:

Field Value

pod_server_running

Server side EDM works in the current session

connection_established

The client is connected to the server side of the current session

ready

Both conditions of readiness are fulfilled

reasons

Reasons for unavailability or error of verification

If the status could not be read, unknown does not mean «stopped». A running client process without a confirmed connection also does not prove readiness.

After connecting

Set a separate task to work with the desired resource: for example, check a specific machine RITM. Status ready=true y EDM confirms the connection to the computer, but does not guarantee the availability of each device behind it.