Add /dog command to switch Telegram chat to dog wolt

Open Beginner friendly
#308 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Start in container/bot/telegram_adapter.py, reading the help text around line 1026 and command registration around line 1077, along with the existing /wolt handler. Add the /dog handler where it clears active_wolt and active_session, confirms the switch, and appears in /help; done means subsequent messages use _handle_dog().

Written by the indexing model from the issue text.

Description

Summary

Add a /dog command to the Telegram bot that switches the active chatter to the dog wolt (Haiku). This is the inverse of /wolt <name> — instead of routing messages to a rodent session, messages go to the dog.

Current behavior

  • /wolt <name> sets active_wolt in chat state → messages route to that wolt's Claude Code session
  • When active_wolt is empty → messages route to _handle_dog() (bot's Haiku LLM)
  • No way to switch back to dog without killing the active session

Proposed behavior

  • /dog clears active_wolt and active_session from the chat state
  • Subsequent messages route to _handle_dog() — the dog becomes the main chatter
  • Dog ack message confirms the switch (e.g. "🐶 tail wag — I'm here!")
  • Add to /help output

Implementation

  • Add handle_dog command handler in container/bot/telegram_adapter.py
  • Clear chat state (active_wolt, active_session) for the calling chat
  • Register command alongside existing handlers (~line 1077)
  • Update help text (~line 1026)

Files

  • container/bot/telegram_adapter.py — command handler + help text
Dominant language
Python
Stars
12
Forks
1
Avg merge
7h 13m
Merged PRs (30d)
31

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jerpint/woltspace

All issues in jerpint/woltspace

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.