---
name: hermes-chat-organization
description: "Organize Hermes chats into themed sessions or separate Telegram bots — simple /new+/title approach vs full multi-bot isolation."
version: 1.0.0
author: hermes-agent
tags: [hermes, organization, telegram, sessions, profiles]
platforms: [telegram, cli]
---

# Hermes Chat Organization

Two approaches to organizing Hermes chats by theme (work, investment, personal, etc.).

## Approach 1: Sessions with /new + /title (Recommended)

For most users, this is simpler and sufficient:

| Command | Purpose |
|---------|---------|
| `/new` | Fresh session |
| `/title "Investasi-Saham"` | Name the session |
| `/title "Investasi-Emas"` | Separate session |
| `/resume [name]` | Resume a named session |

Each session has isolated context. Switching between topics = `/resume` to a different session name.

## Approach 2: Separate Telegram Bots (Full Isolation)

Use when topics must be fully isolated — different memory, different skills, different bot.

### When this is needed
- Different API keys per topic
- Different skills/behavior per topic
- User wants distinct Telegram bot per theme

### Setup steps
1. Create bot via **@BotFather** → `/newbot`
2. Note the bot token
3. `hermes profile create <name>` — creates isolated profile
4. In profile `.env`: `TELEGRAM_BOT_TOKEN=<token>`
5. In profile `config.yaml`: `platforms.telegram.enabled: true`
6. `hermes gateway start` (profile gateway)

### Limitation
Multiple Hermes gateways on the same VPS need different ports or separate VPS. They cannot run two gateway instances on the same machine without process isolation.

## User Preference (Edi Santosa)

Prefers **Approach 1** — simpler. Gets frustrated when over-engineered solutions are proposed. Start with the simple solution, offer complexity only if user explicitly needs it.

## LightClaw Users

If the user runs Hermes through LightClaw (plugin `lightclawbot`), the native Hermes Telegram adapter is bypassed. Multiple Telegram bots require different setup paths — check if LightClaw itself supports multi-bot before proposing Hermes-native solutions.