Skip to content

Coding agents

Telem adds web search, page reading and monitors to Muse Code, Meta’s coding agent for the terminal. The tools come from Telem’s hosted MCP server. A Telem hook sends your options with each search, and records why Muse Code searched when the model gives reasoning summaries.

Using Muse on the web or in the app? That is a different product, with its own page: see Muse.

Node.js 20 or later, on the PATH of the shell that runs muse. The installer checks for it and offers to install it. The hook runs on it.

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 Muse Code. Every path below sets it for you.

Connect Muse Code to Telem

  1. Run the installer in your terminal. If it shows a menu, pick Muse CLI, the installer’s name for Muse 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 Muse Code’s default web search and fetch to Telem.

    Terminal window
    curl -fsSL https://docs.telem.ai/install.sh | sh
  2. Start a new Muse Code session. Muse Code reads its settings when a session starts.

  3. Check the install. telem is in the list of your skills. Then ask Muse Code to search the web: the search shows in the console.

    Terminal window
    muse skills list --source user
Install with no prompts, for example in CI
Terminal window
curl -fsSL https://docs.telem.ai/install.sh | sh -s -- --yes --client muse --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 Muse Code at that MCP url instead of https://mcp.telem.ai/mcp, and saves both urls for later runs.

With --yes, Muse Code keeps its own web search and fetch as the default. Add --muse-disable-web-search to switch the default search and fetch to Telem too.

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.

Muse Code runs the search and read tools without asking, also in muse exec. It asks before monitor_create, monitor_pause, monitor_resume and monitor_delete, because they change your monitors.

  • Options come from the file, not your shell. Muse Code does not give your shell’s environment to the hook, so the TELEM_* variables do not apply. Put your options in .telem/telem.json: the project file, then ~/.telem/telem.json. The hook sends them with every search and page read, the fetch keys included. providerOverrides is not sent. The hook reads the project file even in a workspace that Muse Code does not trust.
  • Why Muse Code searched. The hook sends the reasoning summary that led to each search. Some models give their reasoning only in encrypted form. Then the hook sends the text Muse Code wrote before the search, if there is any.
  • Muse Code’s default web search and fetch. If you say yes, the installer switches them to Telem: it sets { "tools": { "web_search": { "mode": "off" } } } in Muse Code’s settings. Muse Code’s model then has no web_search or web_fetch of its own, and uses Telem’s tools.
  • Muse on the web and in the app is a different product. It has no installer and needs no key: you add Telem as a custom connector and sign in. See Muse.
  • The tool names in Muse Code are mcp__telem__telem_search, mcp__telem__telem_fetch and so on.
If something goes wrong
  • 401 on every call: the server’s Authorization header is missing or has an old key. Run the installer again, or edit the header. Muse Code reports “authentication failed” for any refused connection. With a valid key, the telem entry needs a User-Agent header, such as "User-Agent": "telem-muse"; the installer writes one.
  • Searches show without their session or reasoning: node is not on the PATH of the shell that runs muse. The search still runs, without lineage.
  • No Telem tools, or no MCP tools at all: a header that names an unset variable, such as "Bearer ${TELEM_API_KEY}", turns off every MCP server with no error. Write the key itself. A settings file with both an mcpServers and an mcp_servers block also runs with no MCP servers: keep mcpServers.
  • Muse Code stops the whole run when Telem cannot be reached: the telem entry is missing "mode": "optional".

To update, run the installer again. It rewrites the hook and the skill when they changed. If your saved key still works, it uses it and does not ask.

To remove Telem, take these out of ~/.config/muse/settings.json:

  • the telem entry under mcpServers;
  • the Telem handler under hooks.PreToolUse (its command runs telem-muse.mjs);
  • tools.web_search.mode, if the installer set it and you want Muse Code’s own web search back.

Then delete the telem and skills/telem folders in ~/.config/muse/, and start a new Muse Code session. Muse Code then has no Telem tools or skill, and its own web search is back if you removed the setting.

What the installer changed outside Muse Code’s settings
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.
Configuration

Set the tier, the providers and auto-routing in one file, for Muse 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?