Coding agents
Claude Code
The Telem plugin adds web search, page reading and monitors to Claude Code. Its skill tells Claude to use them when a task needs the web.
Before you begin
Section titled “Before you begin”Node.js 20 or later. The installer checks for it and offers to install it. The plugin uses it to send your Telem options with each search.
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 Claude. Every path below sets it for you.
Install
Section titled “Install”Connect Claude Code to Telem
-
Run the installer in your terminal. If it shows a menu, pick Claude Code. Paste your key when the installer asks. The field is masked, and the key never appears on screen. The installer also asks whether to switch Claude Code’s default web search and fetch to Telem.
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 Claude Code. Plugins load when Claude Code starts.
-
Check the connection.
telemis in the list.Terminal window claude mcp list
Install with no prompts, for example in CI
curl -fsSL https://docs.telem.ai/install.sh | sh -s -- --yes --client claude-code --key-env TELEM_API_KEYnpx @telemai/create@latest --yes --client claude-code --key-env TELEM_API_KEYIn PowerShell, with Node.js 20 or later. Or run the macOS and Linux command in WSL or Git Bash.
For a private deployment, add its two urls: --base-url https://router.example.com --mcp-url https://mcp.example.com/mcp, for example. The installer points its copy of the plugin, in ~/.telem/plugins/claude-plugin-telem, at that MCP url instead of https://mcp.telem.ai/mcp, and saves both urls for later runs. A telem marketplace that you added from GitHub keeps https://mcp.telem.ai/mcp, and the installer warns.
-
Set your key, then add the marketplace, install the plugin and save the key. The last command reads the key from
TELEM_API_KEYand saves it in Claude Code’s settings. You seeConfiguration saved.Terminal window export TELEM_API_KEY=tlm_your_keyclaude plugin marketplace add TelemAI/claude-pluginclaude plugin install telem@telemprintf '{"TELEM_API_KEY":"%s"}' "$TELEM_API_KEY" | claude plugin configure telem@telem --values-stdin -
Restart Claude Code. Plugins load when Claude Code starts.
-
Check the connection.
telemis in the list.Terminal window claude mcp list
To connect Claude Code without the plugin, see MCP server.
-
Start Claude Code with your key set, and paste this prompt. Claude runs the installer, which reads the key from
TELEM_API_KEY, so the key never goes into the chat.Terminal window export TELEM_API_KEY=tlm_your_keyclaudeTerminal window $env:TELEM_API_KEY = "tlm_your_key"claudeSet 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 claude-code --key-env TELEM_API_KEYOn Windows, in PowerShell, run this instead:npx @telemai/create@latest --yes --client claude-code --key-env TELEM_API_KEY4. Show me the installer's summary. Then tell me to restart Claude Code,so that the Telem tools load. -
Restart Claude Code. Plugins load when Claude Code starts.
-
Check the connection.
telemis in the list.Terminal window claude mcp list
If it does not work, see If something goes wrong.
Search and read
4 toolstelem_searchSearches the web on several providers in one call.telem_fetchReads the full text of up to 5 pages.telem_providersLists the search providers.telem_session_historyLists the earlier searches in a session.
Monitors
8 toolsmonitor_createCreates a monitor. Its agent keeps the results that match.monitor_listLists your monitors that have an agent.monitor_getGets a monitor and its agent.monitor_agentGets the agent: its status, its plan and what it found.monitor_changesReads what the agent found, change by change.monitor_pausePauses a monitor.monitor_resumeResumes a paused monitor.monitor_deleteEnds a monitor.
Specific to Claude Code
Section titled “Specific to Claude Code”-
The plugin keeps each session’s searches together. Its hook links every search to your Claude Code session, the prompt and the tool call, so the console shows one conversation, and each subagent gets its own lane under it. A plain
claude mcp addconnection sends no conversation id, so the model has to pass the Telem session id back itself. -
The tool names. With the plugin, the tools are
mcp__plugin_telem_telem__telem_searchandmcp__plugin_telem_telem__telem_fetch. Withclaude mcp add, they aremcp__telem__telem_searchand so on. Use these names in permission rules. -
Telem search and page reads run without a prompt. The installer adds
mcp__plugin_telem_telem__telem_searchandmcp__plugin_telem_telem__telem_fetchtopermissions.allowin~/.claude/settings.json. The other Telem tools, the monitor tools among them, get no rule, so Claude Code asks before it uses them. If your owndenyoraskrule covers one of the two tools, the installer adds nothing for it, and your rule wins. After a by-hand install, add the rules yourself:{ "permissions": { "allow": ["mcp__plugin_telem_telem__telem_search", "mcp__plugin_telem_telem__telem_fetch"] } } -
A broken options file. If
~/.telem/telem.jsonor a project’s.telem/telem.jsonis not valid JSON, the plugin ignores that file and shows you one line, such as “Telem: ignored ~/.telem/telem.json (not valid JSON). Searches and page reads use your other settings and Telem’s defaults.” It shows the line again only when the file changes. Claude does not see it. -
Switch the default search and fetch to Telem by hand. The plugin does not do it; the installer asks. To do it yourself, add both rules to
~/.claude/settings.json, or to a project’s.claude/settings.json:{ "permissions": { "deny": ["WebSearch", "WebFetch"] } }Claude Code then searches and reads pages with Telem. An install from before 0.1.30 added only
"WebSearch": run the installer again, and it asks about"WebFetch".
Update and remove
Section titled “Update and remove”To update, run the installer again. If your saved key still works, it uses it and does not ask. If you installed by hand:
claude plugin marketplace update telemclaude plugin update telem@telemTo remove the plugin, uninstall it, remove its marketplace, and delete the folder the installer copied it to:
claude plugin uninstall telem@telemclaude plugin marketplace remove telemrm -r ~/.telem/plugins/claude-plugin-telemclaude plugin uninstall telem@telemclaude plugin marketplace remove telemRemove-Item -Recurse ~\.telem\plugins\claude-plugin-telemRestart Claude Code after you update or remove. Uninstalling also deletes the key Claude Code saved.
What the installer changed outside the plugin
| File | 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. |
~/.telem/plugins/claude-plugin-telem/ |
The plugin. Claude Code runs it from this folder. | Delete the folder after you uninstall the plugin. |
~/.claude/settings.json |
mcp__plugin_telem_telem__telem_search and mcp__plugin_telem_telem__telem_fetch in permissions.allow |
Remove both entries. |
~/.claude/settings.json |
"WebSearch" and "WebFetch" in permissions.deny, if you said yes |
Remove both entries, or Claude Code has no web search or page fetch of its own after you remove Telem. |
Learn more
Section titled “Learn more”Set the tier, the providers and auto-routing in one file, for Claude Code and your other agents.
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.