Reuse/inherit configuration from Claude Code CLI

[fullofcaffeine]

Context

I have Claude Code CLI fully configured with MCP tools, custom settings, and other configurations. Now using Roo Code with Claude Code as the provider.

The Core Question

Can Roo Code function as a "smart terminal" / advanced diff viewer that simply inherits ALL configurations from Claude Code CLI?

This would include:

• MCP server configurations (~/.claude.json)
• Custom system prompts (CLAUDE.md)
• Permission settings
• Any other Claude Code configurations

My Understanding

Since Roo Code executes Claude Code CLI as a subprocess, it could theoretically:

• Act as a UI wrapper around Claude Code
• Inherit all existing configurations automatically
• Provide a better interface for reviewing changes while using Claude's full capabilities

Why This Matters

• Zero Duplication: All configurations live in Claude Code only
• Single Source of Truth: Claude Code CLI remains the configuration authority
• Roo as Pure UI: Roo Code becomes an enhanced interface, not a separate system
• Team Consistency: One set of configs works everywhere

Specific Questions

1. Can Roo Code pass through all Claude Code configurations transparently?
2. What configurations currently work vs. which need separate setup?
3. Is this the intended design - Roo as UI layer over Claude Code?

Example

# Everything configured once in Claude Code
claude mcp add [tools]
# Edit ~/.claude.json, CLAUDE.md, etc.

# Then Roo Code just works with ALL of it
# No additional configuration needed