back

Disable the Telegram-based AFK bridge to restore direct terminal control.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gmotyl/afk-claude-telegram-bridge-skill --skill back
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: back
Source: https://github.com/gmotyl/afk-claude-telegram-bridge-skill/tree/main/skills/back
Command: npx skills add https://github.com/gmotyl/afk-claude-telegram-bridge-skill --skill back

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables users to deactivate the Telegram Bridge to stop forwarding events and resume local control of Claude interactions.

Core Features & Use Cases

  • Deactivate AFK Mode: Stops forwarding messages from the Telegram bridge.
  • Return to Local Control: Restores direct interaction with Claude in the local environment.
  • Use Case: When a user is back at keyboard, they can deactivate the bridge to regain influence over Claude workflows directly from the terminal.

Quick Start

Type the back command in your terminal to deactivate the Telegram bridge and regain local control over Claude.

Frequently Asked Questions about back

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I disable the Telegram AFK bridge and return to local terminal control?

To disable the Telegram AFK bridge and return to local terminal control, run the back command. This cleanly stops message forwarding scripts and restores direct interaction with Claude in your local environment.

What does deactivating a Telegram bridge do to my Claude session state?

Deactivating a Telegram bridge stops forwarding events to remote messaging and restores direct terminal communication with Claude. It manages multi-modal workflow session states by cleanly stopping message forwarding scripts.

When should I stop forwarding Telegram messages and resume local terminal control?

You should stop forwarding Telegram messages and resume local terminal control when you return to your keyboard. Deactivating the AFK bridge lets you regain direct influence over Claude workflows from the terminal.

Do I need any additional dependencies to deactivate the Telegram bridge?

No additional dependencies are required to deactivate the Telegram bridge. The command operates independently using scripts to cleanly stop message forwarding and ensure system safety by restoring normal operation.

What is the best way to transition from remote Telegram messaging to direct terminal communication?

The best way to transition from remote Telegram messaging to direct terminal communication is running the back command. It safely deactivates the forwarding bridge, ensuring system safety by cleanly stopping message forwarding scripts.