Advanced Settings

Advanced configuration options for users who want to customize their framework environment beyond the standard Getting Started setup.

Custom Paths

The framework uses default paths within your project’s .claude/data directory. Customize these locations to organize documentation across projects or store files in preferred locations.

Documentation Locations

Configure where conversation logs and diary entries are stored:

{
  "env": {
    "FRAMEWORK_CONVERSATION_PATH": "/Users/username/Documents/claude/conversations",
    "FRAMEWORK_DIARY_PATH": "/Users/username/Documents/claude/diary"
  }
}

When to Customize

• Centralizing documentation from multiple projects into one searchable location
• Storing documentation outside project repositories
• Syncing documentation across devices via cloud storage

Per-Project Templates

Override default templates for specific projects:

{
  "env": {
    "FRAMEWORK_TEMPLATE_PATH": "/Users/username/project/.claude/data/templates"
  }
}

This allows customized conversation log and diary formats per project while keeping the standard templates for other work.

When to Customize

• Domain-specific documentation formats (e.g., research methodology vs engineering specifications)
• Team conventions that differ from standard templates
• Projects requiring specialized metadata fields or structure

Package Output

Configure where /framework:package command saves Claude Desktop capability files:

{
  "env": {
    "FRAMEWORK_PACKAGE_PATH": "/Users/username/Downloads"
  }
}

The command generates .zip skill files and .json cache files for Claude Desktop upload. Customize this path to save directly to a preferred location.

When to Customize

• Direct upload location for convenience (e.g., Desktop or Downloads folder)
• Shared folder for team access to capability files
• Cloud-synced directory for multi-device workflows

Geolocation

Override automatic location detection with a custom geolocation:

{
  "env": {
    "FRAMEWORK_GEOLOCATION": "{'city': 'Montréal', 'country': 'Canada', 'timezone': 'America/Toronto'}"
  }
}

When defined, this setting disables the IPinfo API call that normally resolves your location. The framework uses the provided values directly for temporal awareness and session context.

When to Customize

• Working offline or in environments where external API calls are restricted
• Privacy preference to avoid geolocation API requests
• Correcting inaccurate location detection
• Claude Desktop or claude.ai usage where IPinfo resolves to Anthropic’s server location instead of yours

MCP Servers

Optional MCP servers extend framework capabilities for specific workflows. These integrate with your profile methodology to provide specialized tools.

Language Server Protocol

For Developer and Engineer profiles, the required code-review plugin LSP MCP server enables intelligent code analysis, navigation, and development assistance across multiple programming languages.

{
  "mcpServers": {
    "language-server": {
      "command": "npx",
      "args": ["-y", "@axivo/mcp-lsp"],
      "env": {
        "LSP_FILE_PATH": "/Users/username/github/project/.claude/lsp.json"
      }
    }
  }
}

Server Capabilities

• Symbol navigation and definition lookup
• Cross-file reference analysis
• Language-aware code intelligence
• Multi-project workspace support

User Memory Edits

Claude Desktop users can store memory entries that persist across conversations with memory_user_edits function. These entries appear in every session before any other context loads.

Usage

1. Generate memory from chat history in Settings > Capabilities > Memory section
2. Ask Claude to add, view, update, or remove memory entries:
   • “Please remember that I prefer detailed explanations.”
   • “Please add a memory entry for future instances about our project conventions.”
   • “Please show me what’s currently in memory entries.”
   • “Please remove the memory entry about X.”

Next

Dive right into the following section: