Personal agents
OpenClaw
The @telemai/openclaw-plugin package adds web search and page reading to OpenClaw.
While it is enabled, it blocks OpenClaw’s built-in web_search and web_fetch and
sends the agent to the Telem tools.
Before you begin
Section titled “Before you begin”OpenClaw 2026.7.1 or newer. The installer checks the version. For the installer, Node.js 20 or later; it checks for it and offers to install it.
Create a Telem API key
- Open your project
- API keys
- Issue API key
tlm_••••••••••••••••Keys start with tlm_.
Never paste a key into a chat with OpenClaw. Every path below sets it for you.
Install
Section titled “Install”Connect OpenClaw to Telem
-
Run the installer in your terminal. If it shows a menu, pick OpenClaw. Paste your key when the installer asks. The field is masked, and the key never appears on screen. The installer also allows
telem_searchandtelem_fetchin OpenClaw’s tool policy.Terminal window curl -fsSL https://docs.telem.ai/install.sh | shTerminal window npx @telemai/create@latestIn PowerShell, with Node.js 20 or later. Or run the macOS and Linux command in WSL or Git Bash.
-
Restart the Gateway. OpenClaw loads the plugin and reads the key when the Gateway starts.
Terminal window openclaw gateway restart -
Check the install. The output lists
telem_searchandtelem_fetch.Terminal window openclaw plugins inspect telem --runtime --json
Install with no prompts, for example in CI
curl -fsSL https://docs.telem.ai/install.sh | sh -s -- --yes --client openclaw --key-env TELEM_API_KEYnpx @telemai/create@latest --yes --client openclaw --key-env TELEM_API_KEYIn PowerShell, with Node.js 20 or later. Or run the macOS and Linux command in WSL or Git Bash.
-
Set your key, then install the plugin. The commands add your key to the Gateway’s
~/.openclaw/.envonce, fromTELEM_API_KEY.Terminal window export TELEM_API_KEY=tlm_your_keyTerminal window openclaw plugins install npm:@telemai/openclaw-plugin# Adds your key to the Gateway's .env once, and only if TELEM_API_KEY is set[ -n "$TELEM_API_KEY" ] && ! grep -qs '^TELEM_API_KEY=' ~/.openclaw/.env && echo "TELEM_API_KEY=${TELEM_API_KEY}" >> ~/.openclaw/.envopenclaw gateway restart -
Restart the Gateway. OpenClaw loads the plugin and reads the key when the Gateway starts.
Terminal window openclaw gateway restart -
Check the install. The output lists
telem_searchandtelem_fetch.Terminal window openclaw plugins inspect telem --runtime --json
-
Give the Gateway your key, then restart it. OpenClaw’s agent runs inside the Gateway, which reads its environment from
~/.openclaw/.env. These commands add your key there once, fromTELEM_API_KEY, so the key never goes into the chat.Terminal window export TELEM_API_KEY=tlm_your_key[ -n "$TELEM_API_KEY" ] && ! grep -qs '^TELEM_API_KEY=' ~/.openclaw/.env && echo "TELEM_API_KEY=${TELEM_API_KEY}" >> ~/.openclaw/.envopenclaw gateway restart -
Paste this prompt into OpenClaw. The agent runs the installer, which reads the key from
TELEM_API_KEY.Set up Telem web search for this coding agent.1. Read https://docs.telem.ai/llms.txt to learn what Telem is.2. Check that the TELEM_API_KEY environment variable is set. Do not print itsvalue. If it is not set, stop and ask me to set it and restart you.3. Run the Telem installer for this agent, with no prompts:curl -fsSL https://docs.telem.ai/install.sh | sh -s -- --yes --client openclaw --key-env TELEM_API_KEYOn Windows, in PowerShell, run this instead:npx @telemai/create@latest --yes --client openclaw --key-env TELEM_API_KEY4. Show me the installer's summary. Then tell me to restart the OpenClaw Gateway,so that the Telem tools load. -
Restart the Gateway. OpenClaw loads the plugin when the Gateway starts.
Terminal window openclaw gateway restart -
Check the install. The output lists
telem_searchandtelem_fetch.Terminal window openclaw plugins inspect telem --runtime --json
If it does not work, see If something goes wrong.
Search and read
2 toolstelem_searchSearches the web on several providers in one call.telem_fetchReads the full text of up to 5 pages.
Specific to OpenClaw
Section titled “Specific to OpenClaw”- Options go in the plugin config, not in
.telem/telem.json. The plugin readsplugins.entries.telem.config, then theTELEM_*variables.TELEM_AUTO_ROUTINGwins over both. It does not read.telem/telem.json. - Your key can go in the plugin config too, as
apiKey. There it wins overTELEM_API_KEYand~/.telem/credentials.json. - Only the built-in
web_searchandweb_fetchare blocked, by those exact names, while the plugin is enabled. Other search tools stay. Disable or remove the plugin, and the built-in tools come back, with nothing to undo.
Update and remove
Section titled “Update and remove”To update, run the installer again, or:
openclaw plugins update telemTo remove the plugin:
openclaw plugins uninstall telemRestart the Gateway after you update or remove.
What the installer changed outside the plugin
| Where | What it holds | To undo |
|---|---|---|
~/.telem/credentials.json |
Your key | Delete it if no other Telem integration uses it. |
~/.telem/telem.json |
Your Telem options | Delete it if no other Telem integration uses it. |
tools.alsoAllow in OpenClaw’s config |
telem_search and telem_fetch |
Remove only those two entries, and keep the others. |
Learn more
Section titled “Learn more”Set the tier, the providers and auto-routing in OpenClaw's plugin config.
Every option, the values it takes, and which setting wins.
What each search option does, from tiers to date windows.
Choose the fetch provider and tier, or read pages live.