Conversation modes¶

Takopi can handle follow-up messages in two ways: chat mode (auto-resume) or stateless (reply-to-continue).

During onboarding, you chose a workflow (assistant, workspace, or handoff) that automatically configured this for you:

This page explains what those settings mean and how to change them.

Chat mode (auto-resume)¶

What it feels like: a normal chat assistant.

Takopi treats the second message as a continuation. If you want a clean slate, use:

To pin a project or branch for the chat, use:

/new clears the session but keeps the bound context.

Tip: set a default engine for this chat with /agent set claude.

Stateless (reply-to-continue)¶

What it feels like: every message is independent until you reply.

To continue the same session, reply to a message with a resume line:

Changing your settings¶

You can manually change these settings in your config file:

takopi config set transports.telegram.session_mode "chat"
takopi config set transports.telegram.show_resume_line false

[transports.telegram]
session_mode = "chat"      # "chat" or "stateless"
show_resume_line = false   # true or false

Or re-run onboarding to pick a different workflow:

takopi --onboard

Resume lines in chat mode¶

If you enable chat mode (or topics), Takopi can auto-resume, so you can hide resume lines for a cleaner chat. Disable them if you want a fully clean footer, or enable show_resume_line to keep reply-branching visible.

If you prefer always-visible resume lines, set:

takopi config set transports.telegram.show_resume_line true

[transports.telegram]
show_resume_line = true

Reply-to-continue still works¶

Even in chat mode, replying to a message with a resume line takes precedence and branches from that point.

Related¶

• Routing and sessions
• Chat sessions
• Forum topics
• Commands & directives

Next¶

Now that you know which mode you want, move on to your first run:

First run →