MCP discovery found the datamate server already configured in altimate-code, but did not update .altimate-code/altimate-code.json even though the ALTIMATE_EXTENSION_RPC value differed from the VS Code MCP config in .vscode/mcp.json. The discovery flow appears to treat an existing server name as already handled and skips checking or reconciling configuration drift.
Expected behavior: either detect and report config differences for already-configured servers, offer to update the existing config, or explain that runtime/ephemeral values such as ALTIMATE_EXTENSION_RPC are intentionally not synchronized.
Metadata
| Field |
Value |
| CLI Version |
0.8.0 |
| Platform |
darwin |
| Architecture |
arm64 |
| OS Release |
24.3.0 |
| Category |
improvement |
| Working Directory |
jaffle-shop-core |
| Session ID |
ses_171316440ffeH2T9jD3XM22tdO |
MCP discovery found the
datamateserver already configured in altimate-code, but did not update.altimate-code/altimate-code.jsoneven though theALTIMATE_EXTENSION_RPCvalue differed from the VS Code MCP config in.vscode/mcp.json. The discovery flow appears to treat an existing server name as already handled and skips checking or reconciling configuration drift.Expected behavior: either detect and report config differences for already-configured servers, offer to update the existing config, or explain that runtime/ephemeral values such as
ALTIMATE_EXTENSION_RPCare intentionally not synchronized.Metadata