PulseAugur
EN
LIVE 05:19:16

Claude Code's "mandatory" routing rules found non-functional

A user discovered that the "mandatory" routing rules in a CLAUDE.md file, intended to enforce specific tools for web fetching and command execution, were not actually functional in their Claude Code session. The file instructed against using `curl` or `wget`, instead directing users to `ctx_fetch_and_index` and `ctx_execute`. However, upon inspecting the available tools, the user found no `ctx_` prefixed tools, indicating the underlying infrastructure for these rules was absent. This discrepancy meant that if an explicit override instruction hadn't been provided, the agent would have failed to execute commands as intended, leading to errors or unexpected behavior without a clear recovery path. AI

IMPACT Highlights potential issues with agent instruction following and tool availability in LLM environments.

RANK_REASON User discovers a functional issue with a specific tool/feature within a product.

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Claude Code's "mandatory" routing rules found non-functional

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Enjoy Kumawat ·

    My CLAUDE.md Calls Its Routing Rules "Mandatory." The MCP Server Behind Them Was Never Attached.

    <p>This repo — the same one that runs my scheduled DEV.to publishing job — has a <code>CLAUDE.md</code> file that opens with a section titled "context-mode — MANDATORY routing rules." Not a suggestion. Not a style guide. Mandatory. It says any Bash command containing <code>curl</…