/setconv command registered and documented in /help but not implemented in handleCommand()

[ezra-letta]

Summary

/setconv <id> appears in the /help output and is registered as a Telegram command handler in src/channels/telegram.ts (line 341), but handleCommand() in src/core/bot.ts has no case 'setconv': branch. The command falls through to default: return null, which the Telegram adapter renders as "Failed to set conversation".

Root Cause

• src/core/commands.ts line 7: setconv is in the COMMANDS array
• src/core/commands.ts line 26: /setconv <id> appears in HELP_TEXT
• src/channels/telegram.ts line 341: this.bot.command('setconv', ...) is registered
• src/core/bot.ts line 843-986: handleCommand() switch statement has cases for status, heartbeat, reset, cancel, approve, disapprove, model -- but no case for setconv
• default: on line 984 returns null
• telegram.ts line 351: result || 'Failed to set conversation' shows the fallback

Impact

Users cannot switch conversations from within Telegram (or any channel). The only workaround is manually editing lettabot-agent.json to set the conversationId field, which requires stopping LettaBot, understanding the V2 JSON format, and restarting.

This is especially painful when combined with corrupted conversation history (orphaned tool_use/tool_result messages) -- users have no escape path from a broken conversation without manual file editing.

Expected Behavior

/setconv conv-xxx should update the active conversation for the caller's chat, similar to how the Letta Code CLI's lettabot set-conversation works.

Reproduction

1. Start LettaBot with Telegram channel
2. Send /setconv conv-<any-valid-id> in Telegram
3. Observe: "Failed to set conversation"

Reporter

Community user stardust_supernova (Discord)

[RhoMancer]

Fixed in #695 — the /setconv command now validates the conversation ID, resolves the caller's conversation key, invalidates the old session, and sets the new conversation ID. Includes 5 unit tests.