Edits Letta Code Desktop (LCD) preferences by safely reading and updating ~/.letta/desktop_preferences.json. Use only when the user asks to change current Desktop/LCD settings such as theme, default working directory, remote access preference, or remote environment name via the preferences JSON.
71
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Use this skill only to edit the active Letta Code Desktop preferences JSON file. Do not use it for Desktop product-code changes, Electron IPC work, UI changes, or general Letta Cloud Desktop implementation tasks.
The Desktop preferences file is:
~/.letta/desktop_preferences.jsonUser-editable preference keys:
defaultWorkingDirectory: default folder for new local sessions.theme: auto, light, or dark.allowRemoteAccess: boolean for whether remote access should be enabled in preferences.runInBackground: boolean for whether Desktop stays alive in tray/menu bar when all windows close.startAtLogin: boolean for whether Desktop starts hidden at login.remoteEnvName: environment name shown in the Letta Cloud environment picker for the cloud listener.localBackendDirectory: directory containing local backend agents, conversations, and memory.allowLocalAgentsWhenSignedIn: boolean for whether signed-in Desktop sessions can see local/offline agents.System-managed keys (do not edit directly):
artifactsByAgent: per-agent artifacts panel state, written by Desktop UI.debugPanelEnabled: developer debug panel, controlled via app menus.remoteAppServerEnabled: Remote App Server toggle, applied at startup.remoteAppServerUrl: Remote App Server URL, configured via preferences UI.Use a merge-style edit like this, changing only the requested keys:
node - <<'NODE'
const fs = require('fs');
const os = require('os');
const path = require('path');
const file = path.join(os.homedir(), '.letta', 'desktop_preferences.json');
fs.mkdirSync(path.dirname(file), { recursive: true });
const current = fs.existsSync(file)
? JSON.parse(fs.readFileSync(file, 'utf8'))
: {};
const next = {
...current,
// Example update. Replace this with the user's requested setting.
theme: 'dark',
};
fs.writeFileSync(file, JSON.stringify(next, null, 2) + '\n');
NODEAfter editing, read the file back or parse it to confirm valid JSON:
node -e "JSON.parse(require('fs').readFileSync(require('os').homedir() + '/.letta/desktop_preferences.json', 'utf8')); console.log('desktop_preferences.json is valid')"7a4337e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.