From 93c8ef6a4e9d2d71fb71541cc46847dff0393bd1 Mon Sep 17 00:00:00 2001 From: Himanshu Dongre Date: Sun, 17 May 2026 12:31:20 +0530 Subject: [PATCH] Resolve README MCP-block overlap from the merge MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 3-way merge auto-applied both Claude's and Codex's MCP-config intros without flagging a conflict, leaving two paragraphs that both say "smriti init prints the config." Collapse them into one — keeping the quickstart-first onboarding wording and folding in Codex's `which smriti-mcp` manual-config tip. --- README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index ca41aac..dabbde0 100644 --- a/README.md +++ b/README.md @@ -172,11 +172,9 @@ SessionStart hook, and prints the exact next steps to follow. **MCP config** (Claude Code, Cursor, Windsurf). `smriti init` prints a ready-to-paste MCP config block with the executable path and API URL already -resolved for your machine — use what it prints. The shape: - -`smriti init` prints the exact config for your install. If you configure -MCP manually, activate the Smriti venv first and use the absolute path from -`which smriti-mcp` so the host does not pick up a stale executable. +resolved for your machine — use what it prints. If you configure MCP manually +instead, activate the Smriti venv first and use the absolute path from +`which smriti-mcp` so the host does not pick up a stale executable. The shape: ```json {