Continue config.yaml

config.yaml

name: Assistant
version: 1.0.0
schema: v1
models:
  - name: Gemma 3 12B
    provider: ollama
    model: gemma3:12b
    roles:
      - chat
      - edit
      - apply
  - name: Gemini 2.0 Flash
    provider: gemini
    model: gemini-2.0-flash
    apiKey: ${{ secrets.GEMINI_API_KEY }}
    roles:
      - chat
      - edit
      - apply
    defaultCompletionOptions:
      contextLength: 1048576
      maxTokens: 8192
  - name: qwen2.5-coder 1.5b
    provider: ollama
    model: qwen2.5-coder:1.5b-base
    roles:
      - autocomplete
  - name: nomic-embed-text latest
    provider: ollama
    model: nomic-embed-text:latest
    roles:
      - embed
mcpServers:
  - name: Memory
    command: npx
    args:
      - "-y"
      - "@modelcontextprotocol/server-memory"
  - name: JetBrains MCP Proxy
    command: npx
    args:
      - "-y"
      - "@jetbrains/mcp-proxy"
  - name: Filesystem
    command: npx
    args:
      - "-y"
      - "@modelcontextprotocol/server-filesystem"
      - "${{ inputs.PATH }}"
prompts:
  - name: Generate branch name
    description: Generate a branch name for the given changes.
    prompt: |
      Given the following `git diff` output, generate a meaningful branch name that reflects the changes made. 
      The branch name should be concise, descriptive, and follow the convention of using hyphens to separate words.
      The branch name should be structured as follows: <type>/<name>
      Use these for <type>: 
        - f for feature
        - h for hotfix
        - p for patch
        - r for release
      Ensure the branch name:
        - Starts with appropriate prefix
        - Does not exceed 36 characters.
    
      Reply only with the one-line branch name, without any additional text, explanations, or line breaks.
  - name: Generate a conventional commit message
    description: Generate a conventional commit message for the given changes.
    prompt: |
      You are an expert software engineer that generates concise, one-line Git commit messages based on the provided diffs.
      Review the provided context and diffs which are about to be committed to a git repo.
      Review the diffs carefully.
      Generate a one-line commit message for those changes.
      The commit message should be structured as follows: <type>: <description>
      Use these for <type>: fix, feat, build, chore, ci, docs, style, refactor, perf, test
      
      Ensure the commit message:
        - Starts with the appropriate prefix.
        - Is in the imperative mood (e.g., \"Add feature\" not \"Added feature\" or \"Adding feature\").
        - Does not exceed 72 characters.
      
      Reply only with the one-line commit message, without any additional text, explanations, or line breaks.
context:
  - provider: web
  - provider: search
  - provider: clipboard
  - provider: url
  - provider: tree
  - provider: debugger
  - provider: currentFile
  - provider: code
  - provider: os
  - provider: docs
  - provider: diff
  - provider: terminal
  - provider: problems
  - provider: folder
  - provider: codebase
  - provider: commit
    params:
      Depth: 50
      LastXCommitsDepth: 10