Skip to content

Coding agents

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.

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

  1. Open your project
  2. API keys
  3. Issue API key

tlm_••••••••••••••••Keys start with tlm_.

Open the console

Never paste a key into a chat with Claude. Every path below sets it for you.

Connect Claude Code to Telem

  1. 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 | sh
  2. Restart Claude Code. Plugins load when Claude Code starts.

  3. Check the connection. telem is in the list.

    Terminal window
    claude mcp list
Install with no prompts, for example in CI
Terminal window
curl -fsSL https://docs.telem.ai/install.sh | sh -s -- --yes --client claude-code --key-env TELEM_API_KEY

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.

Search and read

4 tools
  • telem_search Searches the web on several providers in one call.
  • telem_fetch Reads the full text of up to 5 pages.
  • telem_providers Lists the search providers.
  • telem_session_history Lists the earlier searches in a session.

Monitors

8 tools
  • monitor_create Creates a monitor. Its agent keeps the results that match.
  • monitor_list Lists your monitors that have an agent.
  • monitor_get Gets a monitor and its agent.
  • monitor_agent Gets the agent: its status, its plan and what it found.
  • monitor_changes Reads what the agent found, change by change.
  • monitor_pause Pauses a monitor.
  • monitor_resume Resumes a paused monitor.
  • monitor_delete Ends a monitor.
  • 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 add connection 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_search and mcp__plugin_telem_telem__telem_fetch. With claude mcp add, they are mcp__telem__telem_search and 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_search and mcp__plugin_telem_telem__telem_fetch to permissions.allow in ~/.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 own deny or ask rule 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.json or a project’s .telem/telem.json is 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".

To update, run the installer again. If your saved key still works, it uses it and does not ask. If you installed by hand:

Terminal window
claude plugin marketplace update telem
claude plugin update telem@telem

To remove the plugin, uninstall it, remove its marketplace, and delete the folder the installer copied it to:

Terminal window
claude plugin uninstall telem@telem
claude plugin marketplace remove telem
rm -r ~/.telem/plugins/claude-plugin-telem

Restart 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.
Configuration

Set the tier, the providers and auto-routing in one file, for Claude Code and your other agents.

Parameters

Every option, the values it takes, and which setting wins.

Search parameters

What each search option does, from tiers to date windows.

Fetch parameters

Choose the fetch provider and tier, or read pages live.

Was this page helpful?