​

BytePlus Coding Plus Telegram

• BytePlus general traffic and BytePlus Coding traffic are not the same lane
• Telegram is a shipped runtime-backed bot surface
• gateway ownership only comes after the Telegram loop already works

​

When This Is The Right Playbook

• coding quota or pricing should stay on the dedicated coding route
• one Telegram bot should own the reply loop
• you still want a separate general BytePlus profile available for other work
• the team wants explicit profile switching instead of one profile being rewritten repeatedly

​

Use A Different Playbook If

​

Step 1: Keep General And Coding Profiles Separate

active_provider = "coding"

[providers.byteplus_main]
kind = "byteplus"
api_key = { env = "BYTEPLUS_API_KEY" }
model = "auto"

[providers.coding]
kind = "byteplus_coding"
api_key = { env = "BYTEPLUS_API_KEY" }
model = "your-reviewed-coding-model"

• byteplus belongs to the general /api/v3 lane
• byteplus_coding belongs to /api/coding/v3
• keeping both profiles visible is cleaner than patching one profile back and forth with ad-hoc route overrides

​

Step 2: Confirm The Active Coding Lane

loong doctor
loong ask --message "Confirm that the active provider is the dedicated coding lane."

​

Step 3: Add The Telegram Bot Surface

[telegram]
enabled = true
bot_token = { env = "TELEGRAM_BOT_TOKEN" }
allowed_chat_ids = [123456789]

loong channels send telegram --target "123456789" --text "hello from loong"
loong channels serve telegram

• allowed_chat_ids is the trust boundary
• Telegram is the smallest runtime-backed reply-loop lane in the current public docs set

​

Step 4: Move To Named Bot Accounts If Needed

[telegram]
enabled = true
default_account = "bot_123456"

[telegram.accounts.bot_123456]
bot_token = { env = "TELEGRAM_BOT_TOKEN" }
allowed_chat_ids = [123456789]

[telegram.accounts.ops]
bot_token = { env = "TELEGRAM_OPS_BOT_TOKEN" }
allowed_chat_ids = [987654321]

loong gateway run --channel-account telegram=bot_123456
loong gateway status --json

​

Step 5: Choose Foreground Or Persisted Ownership

loong channels serve telegram

loong gateway run --channel-account telegram=bot_123456
loong gateway status --json
loong gateway stop

​

Troubleshooting

​

Continue Reading

• Continue to Common Setups for the setup hub.
• Continue to Provider Guides for the full built-in provider matrix.
• Continue to Provider Recipes for the provider-only recipe set.
• Continue to Channel Guides for the full shipped channel matrix.
• Continue to Channel Recipes for the channel-only recipe set.