[uninstall] Could not write settings during server runtime…

Error message

[uninstall] Could not write settings during server runtime cleanup:

What it means

During uninstall's server runtime cleanup, if the atomic write of the modified settings JSON (writeSettingsJsonAtomic) fails after keys were removed, this warning is logged. The uninstall continues, but the settings file may retain server runtime keys (or in a worst case was not updated).

Solutions

Check write permission on ~/.claude/settings.json and the directory (chown/chmod as needed), then re-run uninstall.
Free disk space / resolve quota issues if the write failed for capacity reasons.
Manually delete the server runtime keys from settings.json with an editor after uninstall completes.

Example fix

// before: read-only settings
classic chmod: -r--r--r-- settings.json
// after
chmod u+w ~/.claude/settings.json
npx claude-mem uninstall

Defensive patterns

Strategy: validation

Validate before calling

// Ensure settings are writable before uninstall
import { accessSync, constants } from 'node:fs';
accessSync(USER_SETTINGS_PATH, constants.W_OK);
import { statSync } from 'node:fs';
// check free disk space if writes have been failing
statSync(USER_SETTINGS_PATH);

Type guard

function isWriteFailure(e: unknown): boolean {
  const msg = e instanceof Error ? e.message : String(e);
  return /EACCES|EPERM|ENOSPC|EROFS|EBUSY/i.test(msg);
}

Try / catch

try {
  writeSettingsJsonAtomic(USER_SETTINGS_PATH, flat);
} catch (error) {
  console.warn('[uninstall] Could not write settings during server runtime cleanup:', error instanceof Error ? error.message : String(error));
  // advise manual cleanup of leftover keys
}

Prevention

Keep settings.json and ~/.claude owned by the current user
Ensure adequate disk space / quota before uninstall
Exclude ~/.claude from sync tools that lock files
Re-check settings.json contents after uninstall to confirm keys were removed

When it happens

Trigger: Running `claude-mem uninstall` when server runtime keys exist and writing the updated settings file fails — read-only file, permission denied, disk full, or the atomic rename target is locked/immutable.

Common situations: Settings file owned by root or another user; ~/.claude directory read-only; disk quota exceeded; file editors/sync tools (Dropbox/iCloud) holding locks or immutability flags.

Understand the failure class

Background: "failed to write file", "Could not save figure", "Error saving remote file" — file write failed: causes and fixes across languages and libraries — this error's family across 38 libraries.

Related errors

AI-assisted analysis of thedotmack/claude-mem@d8bc9755e7 (2026-09-17). Data as JSON: /api/errors/20be550ed7eb03bd. Report an issue: GitHub.

Appendix: source

Thrown at src/npx-cli/commands/uninstall.ts:62

  try {
    flat = readFlatSettings(USER_SETTINGS_PATH);
  } catch (error: unknown) {
    console.warn('[uninstall] Could not read settings for server runtime cleanup:', error instanceof Error ? error.message : String(error));
    return;
  }
  if (!flat) return;
  let changed = false;
  for (const key of keys) {
    if (key in flat) {
      delete flat[key];
      changed = true;
    }
  }
  if (changed) {
    try {
      writeSettingsJsonAtomic(USER_SETTINGS_PATH, flat);
    } catch (error: unknown) {
      console.warn('[uninstall] Could not write settings during server runtime cleanup:', error instanceof Error ? error.message : String(error));
    }
  }
}

function removeMarketplaceDirectory(): boolean {
  const marketplaceDir = marketplaceDirectory();
  if (existsSync(marketplaceDir)) {
    rmSync(marketplaceDir, { recursive: true, force: true });
    return true;
  }
  return false;
}

function removeCacheDirectory(): boolean {
  const cacheDirectory = join(pluginsDirectory(), 'cache', 'thedotmack', 'claude-mem');
  if (existsSync(cacheDirectory)) {
    rmSync(cacheDirectory, { recursive: true, force: true });
    return true;

View on GitHub (pinned to d8bc9755e7)