\nPlease note that TrueConf does not promote the use of OpenClaw, does not recommend its deployment in corporate infrastructure, and bears no responsibility for the work of OpenClaw, related AI agents, external services, or third\u2011party components.<\/p>\n
The plugin is used and connected to OpenClaw by a user or system administrator at their own discretion and with full awareness of possible risks. Before deploying this software in a corporate network, you must learn about information security risks, including data leakage, unauthorised access, prompt injection, execution of unwanted commands, compromise of API keys, and unintended behaviour of AI agents:<\/p>\n
- \n
- Four OpenClaw flaws let attackers steal data, escalate privileges, and plant backdoors through the agent\u2019s own sandbox<\/a><\/li>\n<\/ul>\n
The plugin should be used only after you perform a full risk assessment, test the software in an isolated environment, restrict access rights, set up monitoring, and take measures to protect the corporate infrastructure.\n<\/p>\n<\/div>\n
To make sure that the agent is always accessible to users from any device, including mobile messengers, you can install it on a dedicated server \/ VM that always stays powered on. The key requirement is that this server is accessible from your network. We will install OpenClaw on a dedicated VM and configure communication with the agent through a chat in True\u0421onf client applications.<\/p>\n
Getting ready<\/h2>\n
We will use Debian 13 as an example for the OpenClaw + TrueConf setup. We recommend that you update your packages with this command before starting:<\/p>\n
sudo apt update && sudo apt upgrade -y<\/pre>\n
Install the curl tool if you do not have it:<\/p>\n
sudo apt install curl -y<\/pre>\n
We recommend using the latest version of Node.js<\/a>. Run this command to check whether this tool is installed and its version:<\/p>\n
node -v<\/pre>\n
If necessary, install the latest version<\/a> (at the time when this guide was written, the version 26 was the latest one) by executing the following commands one after another:<\/p>\n
curl -o- https:\/\/raw.githubusercontent.com\/nvm-sh\/nvm\/v0.40.4\/install.sh | bash<\/pre>\n
\\. \"$HOME\/.nvm\/nvm.sh\"<\/pre>\n
nvm install 26<\/pre>\n
Next, verify the installation with this command:<\/p>\n
node -v<\/pre>\n
Installation of OpenClaw<\/h2>\n
Before installation, you need to choose the AI model and get an API key. To get an API key, choose a provider. We will use OpenCode<\/a> as an example. On the main page, select Zen \u2192 Get started with Zen<\/b> and log in to your account. Below you will see your API key and a large list of available models:<\/p>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image15-578x470.png\" "\\"\\"")
<\/a><\/p>\nTo install OpenClaw, just run this command:<\/p>\n
curl -fsSL https:\/\/openclaw.ai\/install.sh | bash<\/pre>\n
The setup wizard will open. Let us go through all the steps in detail.<\/p>\n
The setup wizard will check whether your OS meets system requirements, and install missing components such as Node.js and Git. During the first step, Select Yes to confirm that you understand the level of system access granted to the agent. Then choose QuickStart (recommended)<\/b>:<\/p>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image10-690x458.png\" "\\"\\"")
<\/a><\/p>\nNow let us consider the main steps. First, select your AI model provider:<\/p>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image7-690x458.png\" "\\"\\"")
<\/a><\/p>\nNext, paste your API key to access the model. As a rule, this key can be found in a user\u2019s personal area on the LLM vendor website.<\/p>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image8-690x458.png\" "\\"\\"")
<\/a><\/p>\nDuring the Select channel (QuickStart)<\/b> step, choose Skip for now<\/b>, since we will later configure our TrueConf plugin as the channel:<\/p>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image14-690x458.png\" "\\"\\"")
<\/a><\/p>\nTo make sure that the AI agent can search for information on the Internet, select a search provider:<\/p>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image12-690x458.png\" "\\"\\"")
<\/a><\/p>\nDuring the next step, you will be able to configure the AI agent\u2019s skills, in other words, you can determine what the agent is able to do. For a faster deployment, skip this step by selecting No<\/b>:<\/p>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image1-690x458.png\" "\\"\\"")
<\/a><\/p>\nFinally, choose Hatch in terminal (recommended)<\/b>:<\/p>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image4-690x458.png\" "\\"\\"")
<\/a><\/p>\nInstallation of the TrueConf plugin for OpenClaw<\/h2>\n
To install the plugin, run this command:<\/p>\n
openclaw plugins install @trueconf-community\/trueconf-openclaw-channel<\/pre>\n
The plugin will be configured through a wizard similar to the one used for OpenClaw. Launch the wizard with:<\/p>\n
npx -y -p @trueconf-community\/trueconf-openclaw-channel trueconf-setup<\/pre>\n
Let us go through each configuration step:<\/p>\n
- \n
- Choose the English language (it will be used for displaying the instructions in the wizard).<\/li>\n
- Enter the server domain name or IP address.<\/li>\n
- Type the login of the account under which the agent will work.<\/li>\n
- Enter the password for the agent\u2019s account.<\/li>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image6-690x467.png\" "\\"\\"")
<\/a><\/p>\n- We recommend choosing the option Specify the path to the root certificate (CA)<\/b> when configuring TLS, if you are using a self\u2011signed certificate (you can get this certificate from your server administrator). Next, enter the certificate path. If you are using a commercial certificate, disable TLS certificate verification.<\/li>\n
- Finally, select Yes<\/b> to complete the configuration.<\/li>\n<\/ul>\n
- We recommend choosing the option Specify the path to the root certificate (CA)<\/b> when configuring TLS, if you are using a self\u2011signed certificate (you can get this certificate from your server administrator). Next, enter the certificate path. If you are using a commercial certificate, disable TLS certificate verification.<\/li>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image2-690x467.png\" "\\"\\"")
<\/a><\/p>\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2026\/06\/image3-431x470.png\" "\\"\\"")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"