Week 0x1E

So, Shannon said the first bear use case she’d like to try is a coding agent. So I looked into wiring something with a Claude Code-like UI to Letta Code or Letta directly. It turns out that is hard. I looked for VS Code plugins that abstract the agent, assuming there would be a standard protocol or at least CLI convention, but this seems to be a wild frontier, still.

Somehow, I noticed that Zed has really matured since I last tried it, and has a solution: ACP. So I set about adding support to Den. I spent a lot of time researching and talking to Lett’s support bot (Ezra) about how to use Letta Code from ACP, and eventually came to the conclusion this cuts against the grain of Letta Code’s state management too much. So now I have introduced different kinds of agents withing one bear: one to do server-side work (Letta Code), one to chat with (also Letta Code), one to speak ACP to IDE clients (and ACP adapter to the Letta API), and one to coordinate the sharing of memory between them all (also direct to Letta API). My Builder Bear talked me into a 5th type for watching and reacting to external events, but that’s last priority.

We made major progress on thie ACP adapter, and now I’m talking to the Builder Bear via Zed. It still gets confused with local tool use, though, so I have much work ahead and am tempted to hand-code.