fix: revert to resumeSession(agentId) — API conversations incompatible with SDK

resumeSession(conversationId) silently fails (0 chars response) when the
conversation was created via the raw Letta API. The SDK needs to manage
its own conversation. Revert to agentId for now.

Written by Cameron ◯ Letta Code

"Move fast and fix things." - Unknown
This commit is contained in:
Cameron
2026-03-13 16:34:49 -07:00
parent 4c3c457f7a
commit e71fc2f976

View File

@@ -61,13 +61,13 @@ async function sendViaSdk(payload: SdkPayload): Promise<boolean> {
}
// 'full' mode: no allowedTools restriction (all tools available)
log(`Creating SDK session for conversation ${payload.conversationId} (mode: ${payload.sdkToolsMode})`);
log(` agent: ${payload.agentId}`);
log(`Creating SDK session for agent ${payload.agentId} (mode: ${payload.sdkToolsMode})`);
log(` cwd: ${payload.cwd}`);
log(` allowedTools: ${payload.sdkToolsMode === 'read-only' ? readOnlyTools.join(', ') : 'all'}`);
// Resume the specific conversation so messages appear in the same thread on app.letta.com
const session = resumeSession(payload.conversationId, sessionOptions);
// Use agentId — the SDK creates/manages its own conversation.
// The Letta API conversation (payload.conversationId) is incompatible with SDK sessions.
const session = resumeSession(payload.agentId, sessionOptions);
try {
log(`Sending message (${payload.message.length} chars)...`);