Add Claude Code setup section to README

[Copilot]

Added a new "Claude Code Setup" section to the README that provides instructions for adding revect to Claude Code after it's already configured in Claude Desktop.

Changes Made

• Updated Table of Contents: Added new entry for Claude Code Setup section
• New Section: Added "🔌 Claude Code Setup" section below the existing MCP Setup section

What's Included

The new section explains:

• Prerequisite of having revect configured in Claude Desktop first
• The exact command to run: claude mcp add-from-claude-desktop
• Benefits of seamless memory access across Claude interfaces
• How it enables recalling and persisting information outside of Claude Code's hard coded memory files

Example Usage

After setting up in Claude Desktop, users can now run:

claude mcp add-from-claude-desktop

This allows users to access their revect memory vault from both Claude Desktop and Claude Code, providing a unified experience across all Claude interfaces.

Fixes #62.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[zackify]

@claude also mention that it's useful if you use Claude code in different environments such as docker and need to reference memory without adding files everywhere on many MCP clients

[claude]

Claude finished @zackify's task —— View job

---

✅ Request completed!

I've successfully enhanced the Claude Code setup section in the README to include the requested information about Docker and multi-environment benefits.

Todo List:

• Read current README.md to understand existing Claude Code setup section
• Add information about Docker environments and avoiding file duplication across MCP clients
• Commit changes to the PR branch

What was added:

Added a new "Benefits for multi-environment usage:" section under the Claude Code setup that explains:

• 🐳 Perfect for Docker environments - Access your memory vault from Claude Code running in containers without duplicating configuration files
• 🔄 Unified MCP client management - Avoid manually configuring MCP servers across multiple environments and development setups
• 🌐 Consistent memory access - Whether you're in Claude Desktop, Claude Code, or other MCP-enabled tools, your memory vault stays connected

The changes have been committed to the existing PR branch (copilot/fix-62) and are now ready for review.

--- |

[Copilot]

@claude also mention that it's useful if you use Claude code in different environments such as docker and need to reference memory without adding files everywhere on many MCP clients

Added the Docker environment benefits to the Claude Code setup section. The new paragraph explains how it's useful for different environments like Docker and avoids managing separate memory files across multiple MCP clients. See commit 5a6dee7.