aaif-goose/goose

Silent Rollback of Manually Edited config.yaml on Restart Breaks Custom MCP Extensions

Open

#8970 opened on May 2, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (45,211 stars) (4,628 forks)batch import
help wantedsnoozed:20260530

Description

Describe the bug windows 10 22H2 , python 3.10.11 ,nodejs 22.16.0, goose 1.33.1 Bug Description: The UI state is seriously out of sync with config.yaml. Manually edited changes in the YAML are silently rolled back on restart, preventing custom MCP extensions from persisting. Environment: The config directory has been physically redirected to the D: drive using mklink, and a custom LMStudio provider is in use. Core Pain Point: The configuration self‑check mechanism on software startup is too aggressive, directly wiping out any non‑built‑in extensions.

💡 Before filing, please check common issues:
https://goose-docs.ai/docs/troubleshooting

📦 To help us debug faster, attach your diagnostics zip if possible.
👉 How to capture it: https://goose-docs.ai/docs/troubleshooting/diagnostics-and-reporting/

A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Please provide the following information

  • OS & Arch: [e.g. Ubuntu 22.04 x86]
  • Interface: [UI / CLI]
  • Version: [e.g. v1.0.2]
  • Extensions enabled: [e.g. Computer Controller, Figma]
  • Provider & Model: [e.g. Google – gemini-1.5-pro]

Additional context Add any other context about the problem here.

Contributor guide

Tech stack
rustpythonnodejs
Domain
backenddeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Rust knowledgeconcept of config file parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the startup configuration self check mechanism in the Rust source code, likely under src/config/ or similar. The issue states that on restart, manually edited config.yaml entries are silently overwritten. Locate where the config is validated or reset, and modify the logic to preserve user customizations rather than reverting to default extensions.