Project Configuration

Configure Synoppy on a per-project basis with synoppy.json.

Creating Project Config

Initialize a project configuration file in your project root:

synoppy init

Or use the slash command during a session:

/init

Example Configuration

{
  "allowedTools": ["read", "write", "bash"],
  "blockedTools": ["delete"],
  "customInstructions": "This is a React project using TypeScript. Follow the existing code patterns.",
  "ignorePatterns": ["node_modules", "dist", ".git", "*.log"],
  "model": "claude-sonnet-4-6",
  "thinkingEnabled": true
}

Configuration Options

Custom Instructions

Add project-specific context and guidelines that Synoppy will follow:

{
  "customInstructions": "This is a Next.js 14 app with App Router. Use Server Components by default. Follow these conventions:\n- Use TypeScript strict mode\n- Prefer 'const' over 'let'\n- Use Tailwind CSS for styling\n- Place components in src/components"
}

Custom instructions are included with every request to help Synoppy understand your project's conventions.

Ignore Patterns

Prevent Synoppy from reading or modifying certain files:

{
  "ignorePatterns": [
    "node_modules",
    "dist",
    "build",
    ".git",
    "*.log",
    "*.env*",
    "secrets/**"
  ]
}

Configuration Hierarchy

Settings are applied in this order (later overrides earlier):

1. Default settings
2. Global config (~/.synoppy/config.json)
3. Project config (synoppy.json)
4. Command line flags
5. Session commands (/model, etc.)