Skip to main content
How-To Guides Last updated: 31 March 2026

Choose a workflow mode

Untether has three workflow modes that control how conversations continue and how sessions are organised. Each mode suits a different working style.

Untether has three workflow modes that control how conversations continue and how sessions are organised. Each mode suits a different working style.

Which mode is right for me?

graph TD
    A["How do you work?"] --> B{"Multiple projectsor branches?"}
    B -->|"Yes, with forum topics"| C["Workspace"]
    B -->|"No"| D{"Terminalintegration?"}
    D -->|"Copy resume linesto terminal"| E["Handoff"]
    D -->|"Stay in Telegram"| F["Assistant"]

    style C fill:#e8f5e9
    style E fill:#fff3e0
    style F fill:#e3f2fd

Quick decision:

  • Assistant — you want a simple chat that remembers context. Just type and go. (recommended for most users)
  • Workspace — you manage multiple projects and want each Telegram forum topic bound to a project/branch.
  • Handoff — you switch between Telegram and terminal, copying resume lines to continue sessions in your IDE.

Mode comparison

AssistantWorkspaceHandoff
SessionAuto-resumeAuto-resume per topicReply-to-continue
Resume lineHiddenHiddenShown
TopicsOffOnOff
Best forSolo dev, mobileTeams, multi-projectTerminal workflow
/newResets sessionResets topic sessionNo effect

How each mode works

Assistant

Messages automatically continue your last session — no need to reply to a specific message. Use /new to start fresh.

sequenceDiagram
    participant U as You
    participant B as Bot
    U->>B: fix the login bug
    B->>U: done (session A)
    U->>B: now add tests for it
    Note right of B: Auto-resumes session A
    B->>U: done (session A continued)
    U->>B: /new
    Note right of B: Session cleared
    U->>B: refactor the API
    B->>U: done (session B — fresh)

Workspace

Each forum topic maintains its own independent session. Topics can be bound to specific projects and branches via /ctx set.

sequenceDiagram
    participant U as You
    participant T1 as Topic: frontend
    participant T2 as Topic: backend
    U->>T1: fix the CSS
    T1->>U: done (topic A session)
    U->>T2: update the API
    Note right of T2: Independent session
    T2->>U: done (topic B session)
    U->>T1: now add animations
    Note right of T1: Resumes topic A
    T1->>U: done (topic A continued)

Handoff

Every message starts a new run. Resume lines are always shown so you can copy them to continue in terminal. Reply to a bot message to continue that session in Telegram.

sequenceDiagram
    participant U as You
    participant B as Bot
    participant T as Terminal
    U->>B: fix the login bug
    B->>U: done + resume abc123
    U->>B: add a feature
    Note right of B: New run (no auto-resume)
    B->>U: done + resume def456
    U->>T: codex resume abc123
    Note right of T: Continues in terminal

Configuration

Each mode is defined by three settings in untether.toml:

=== “Assistant”

```toml
[transports.telegram]
session_mode = "chat"
show_resume_line = false

[transports.telegram.topics]
enabled = false
```

=== “Workspace”

```toml
[transports.telegram]
session_mode = "chat"
show_resume_line = false

[transports.telegram.topics]
enabled = true
scope = "auto"
```

=== “Handoff”

```toml
[transports.telegram]
session_mode = "stateless"
show_resume_line = true

[transports.telegram.topics]
enabled = false
```

Switching modes

To change modes, edit the three settings in your untether.toml and restart:

systemctl --user restart untether  # or untether-dev

No data is lost when switching modes. Session state files are preserved — they just won’t be used if you switch from chat to stateless mode. Switching back restores them.

Check your mode The startup message shows your current mode: mode: assistant, mode: workspace, or mode: handoff. You can also check via /config — look at the “Resume line” setting (on = handoff, off = assistant/workspace).

Workspace prerequisites

Workspace mode requires additional setup:

  1. Forum-enabled supergroup — create a Telegram group and enable Topics in group settings
  2. Bot as admin — add your bot to the group and promote to admin
  3. Manage Topics permission — the bot needs can_manage_topics to create/edit topics (optional — existing topics work without it)

See Forum topics for detailed setup instructions.

Was this helpful?

Related Articles