/editing-letta-code-desktop-preferences
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
$ npx -y skills add letta-ai/letta-code --skill editing-letta-code-desktop-preferences --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/editing-letta-code-desktop-preferences
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
editing-letta-code-desktop-preferences.SKILL.mdname: editing-letta-code-desktop-preferences
description: 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.
Editing Letta Code Desktop Preferences
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.
Preferences file
The Desktop preferences file is:
~/.letta/desktop_preferences.json
Known 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.
- `remoteEnvName`: environment name shown for remote access.
Workflow
1. Read the existing JSON first. 2. Preserve unknown keys. 3. Merge only the requested preference updates. 4. Write pretty JSON with a trailing newline. 5. Do not edit token, provider, secret, agent, conversation, memory, or unrelated state files. 6. Tell the user that the change applies live only if their Desktop build watches preference-file changes; otherwise they should reload/restart Desktop or use Preferences → General.
Safe edit command
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');
NODEValidation
After 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')"Read more
name: editing-letta-code-desktop-preferences description: 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.
Editing Letta Code Desktop Preferences
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.
Preferences file
The Desktop preferences file is:
~/.letta/desktop_preferences.json
Known 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.
- `remoteEnvName`: environment name shown for remote access.
Workflow
1. Read the existing JSON first. 2. Preserve unknown keys. 3. Merge only the requested preference updates. 4. Write pretty JSON with a trailing newline. 5. Do not edit token, provider, secret, agent, conversation, memory, or unrelated state files. 6. Tell the user that the change applies live only if their Desktop build watches preference-file changes; otherwise they should reload/restart Desktop or use Preferences → General.
Safe edit command
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');
NODEValidation
After 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')"Letta Code is a stateful agent harness for creating agents that are more like people than tools. Letta Code agents have memory, identity, and a sense of experience over time.
Repo: letta-ai/letta-code
Other skills on letta-code.
- /acquiring-skills
Discover and install skills from Hermes, ClawHub, GitHub, and other registries. Load this skill whenever a user asks for a capability you don't already have — image generation, social media, email, calendar, finance, DevOps, search, browser automation, etc.
Open skill - /context-doctor
Identify and repair degradation in system prompt, external memory, and skills preventing you from following instructions or remembering information as well as you should.
Open skill - /converting-mcps-to-skills
Connect to MCP (Model Context Protocol) servers and create skills for repeated use. Load when a user wants to use an MCP server, connect to external tools via MCP, or when they mention MCP, model context protocol, or specific MCP servers.
Open skill - /creating-mods
Creates and edits trusted local Letta Code mods, including tools, slash commands, local-only model providers, lifecycle/turn events, scoped conversation helpers, panels, and capability-gated behavior. Use when asked to make a mod, add an agent-callable tool, add a slash command,
Open skill - /creating-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Letta Code's capabilities with specialized knowledge, workflows, or tool integrations.
Open skill - /customizing-commands
Creates, edits, and enables Letta Code mod-provided slash commands. Use when the user asks to add a custom /command, slash command, command shortcut, scoped conversation-backed command, or command-driven panel behavior.
Open skill

