Skip to content
tg-claude-bridge

Sessions

A session is an active Claude Code subprocess running against your active repository. While a session is running, every message you send goes to Claude Code.

Starting a session

Send /start to start a session in your last active repo. If no repo is active, the bot prompts you to clone one.

You can also start a session by:

  • Clicking a repo name in the /repo list
  • Typing freely — if a repo is active, the session starts automatically

Ending a session

/end

Sends SIGTERM to the Claude subprocess and removes it. Claude will not be able to continue its work.

Stopping a task

/stop

Sends SIGTERM to interrupt the current Claude task without ending the session. Claude will exit its current tool use and return control to you. The session stays active — send another message to continue.

Checking status

/status

Returns the current session state, including active repo and session uptime.

Auto-cleanup

Sessions end automatically after 10 minutes of inactivity (no messages sent). This prevents stray processes from consuming resources.

To change the timeout:

Terminal window
IDLE_TIMEOUT_MS=300000   # 5 minutes

One-shot sessions

Each message spawns a fresh Claude Code process. There is no conversation carry-over between messages — each request is independent. This ensures clean state and avoids context conflicts between users.