The chat never starts over

Meido is one runtime for a conversation that continues: layered memory, recall, a service briefing, and a Markdown vault. Main chat stays one continuous thread. Topics still let you separate that log into titled stretches. Start with the path that matches what you want to do.

“I want the web cockpit.”

Install, start Meido, and finish the wizard on the desk. The web cockpit page names every control.

“I want it in Telegram, Discord, WhatsApp, or WeCom.”

Channels are optional. The web desk is already the same chat.

“I want work to run while I am away.”

Schedules re-enter the same conversation, with the same persona. The board keeps TODO, PLAN, BUILD, and VERIFY in front of you.

“I want it to use my notes.”

The Obsidian vault stays Markdown. MemPalace recalls what this turn needs.

The desk, page by page

• Chat — continuous main chat, topics, Focus, Transcript, side chats, mentions.
• Cockpit — queue, memo, bookmarks.
• Inbox — unread messages and todos.
• Groups — a separate multi-persona transcript.
• Records — artifacts, terminal, principles, memory, run debug.
• Settings and Personas — shared setup, then one attendant.