letta code with persistent multi-agent sessions

frequently asked questions

• +Does Letta Code's memory persist across Pane restarts?

  Yes, and the two persistence layers are independent. Letta Code stores agent memory in its own backend (a Letta server or local SQLite). Pane stores session layout and worktree assignments. When you restart Pane, Pane restores the session workspace; when you restart Letta Code, Letta restores agent memory. Neither depends on the other.

• +Can I run multiple Letta Code subagents in separate panes?

  Yes. Start one Letta Code agent process per pane, each pointed at its own worktree. Pane manages the terminal isolation — Letta manages the agent memory. Each subagent accumulates its own memory without cross-contamination.

• +What does Pane add over running Letta Code in a normal terminal?

  Pane organizes the workspace: named sessions, worktree isolation per branch, diff review without leaving the terminal environment, and git actions alongside the agent output. With multiple Letta subagents running in parallel, that workspace organization becomes the bottleneck. Pane removes it.

• +How does Pane handle long-running Letta Code tasks?

  Pane keeps each session's output visible and navigable while the agent runs. A Letta task that runs for several minutes produces output that stays in the session scroll buffer. You can review what the agent wrote, check the diff, and move to another session without losing the context.

• +Does Letta Code need any configuration changes to run inside Pane?

  No. Pane is a terminal host — it does not wrap or intercept the Letta CLI. Configure Letta Code as you normally would (server URL, model provider, agent ID) and start it inside a Pane terminal.

• +How does Letta Code compare to Claude Code with memory in Pane?

  Claude Code with memory extensions adds recall to a coding agent. Letta Code is built around persistent memory at the architecture level — it is the MemGPT lineage applied to software development. If memory persistence across restarts is a requirement, not a feature, Letta Code is the more purpose-built option.

• +Does Pane work with any model provider for Letta Code?

  Yes. Letta Code is model-agnostic — it supports Anthropic, OpenAI, Azure, and local models. Pane does not touch the model configuration. Whatever model Letta is configured to use, it uses inside a Pane terminal exactly as it would anywhere else.

• +Is Pane relevant for TerminalBench-style evaluation workflows?

  If you are running multiple terminal-based agent evaluations in parallel — each on a separate branch, each needing its own session output visible — Pane provides the workspace structure. It does not automate the evaluation loop itself, but it makes running many concurrent sessions manageable.

• +When is a single Letta Code agent enough?

  If one agent and one branch covers your current work, a single terminal is sufficient. Pane is useful when you want multiple Letta subagents running concurrently on separate branches, or when you want to mix Letta Code with other terminal agents and need isolation between them.

• +Does Pane work on Windows with Letta Code?

  Yes. Pane is a native Windows desktop app. Letta Code runs in a Pane terminal on Windows the same way it runs on Mac or Linux.