letta-ai/letta-code is an agent harness for building assistants that retain memory, identity, and experience across interactions instead of treating each task as isolated. Developers use it through local, desktop, browser, or messaging interfaces for interactive or continuously running agents, and its catalogue entries configure the agents' skills, instructions, rules, and behavior.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add letta-ai/letta-code --skill editing-letta-code-desktop-preferencesgit clone --depth 1 https://github.com/letta-ai/letta-codeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/letta-ai/letta-code/editing-letta-code-desktop-preferences)<a href="https://agentmods.dev/skills/letta-ai/letta-code/editing-letta-code-desktop-preferences"><img src="https://agentmods.dev/badge/skills/letta-ai/letta-code/editing-letta-code-desktop-preferences.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00066 | $0.00677 |
| Opus 5 | $0.00033 | $0.00338 |
| Sonnet 5 | $0.00013 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
editing-letta-code-desktop-preferences scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
User-editable preference keys:
defaultWorkingDirectory: default folder for new local sessions.theme:auto,light, ordark.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.
Workflow
- Read the existing JSON first.
- Preserve unknown keys.
- Merge only the requested preference updates.
- Write pretty JSON with a trailing newline.
- Do not edit token, provider, secret, agent, conversation, memory, or unrelated state files.
- Changes apply live within ~100ms via Desktop's file watcher; if Desktop is not running, changes take effect on next startup.
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');
NODE
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 78 lines · 66 tokens per session scan A d9f7b1422413
editing-letta-code-desktop-preferences is a skill published in the GitHub repository letta-ai/letta-code (3,225 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 677 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
writing
A writing guide for turning verified facts and calculations into finished text for a specific audience. It follows the requested language, structure, and length.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
ws-ckpt
A Linux-only tool for creating and managing workspace snapshots. A snapshot is a saved view of files that can later be compared, restored, listed, or deleted.
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.