What problem does it solve?
Changing how a Letta Code agent behaves requires choosing the right configuration layer—memory files, server agent fields, conversation overrides, local settings, mods, channels, or schedules—and a wrong-layer change can clobber system prompts, brick the agent, or leak secrets.
Core Features & Use Cases
- Layered configuration routing: Decision tables map each request (rename, model change, permission rule, schedule, channel setup) to the correct layer, with a safe inspect-then-patch workflow and rollback guidance.
- Guarded server updates: Helper scripts patch agent/conversation model, context window, model settings, compaction prompts, and system prompts with dry-run previews, cross-agent mismatch rejection, and confirmation gates for dangerous writes.
- Local settings and permissions management: Scripts report merged user/project/local settings without printing secrets and add allow/deny/ask/alwaysAsk permission rules atomically.
- Use Case: A user asks to switch their agent to a new model with a larger context window; the skill dry-runs a conversation-scoped patch first, verifies the effective state, then persists the agent-level default.
Quick Start
Ask the agent to show its current configuration and change its default model to a specific provider handle with a dry run first.