Tmux Session Manager logo

Tmux Session Manager

Community
minicoohei
tmux-session-manager

Lightsail上のClaude Code tmuxセッションをSSH経由で管理。 「セッション確認」「PR同期」「tmuxの状態」等のリクエストで発動。

Overview

Publisherminicoohei
Repositoryai-agent-camp
Skill nametmux-session-manager
Stars
346
Forks
13
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by minicoohei on GitHub. Read the source before you install it.

Installation

Install the Tmux Session Manager AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/minicoohei/ai-agent-camp/tree/main/.claude/skills/tmux-session-manager
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/minicoohei/ai-agent-camp.git /tmp/ai-agent-camp
mkdir -p .claude/skills
cp -r /tmp/ai-agent-camp/.claude/skills/tmux-session-manager .claude/skills/tmux-session-manager
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Tmux Session Manager in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Tmux Session Manager on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Tmux Session Manager is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Tmux Session Manager Skill

Lightsail 上で稼働する Claude Code tmux セッションを SSH 経由で管理するスキル。 Issue/PR 単位のセッション状況確認、指示送信、PR 同期を行う。

トリガー

以下のキーワードで発動:

  • 「セッション確認」「セッション一覧」「tmux の状態」
  • 「PR の進捗」「Issue の作業状況」
  • 「セッション作成」「PR 同期」「sync-prs」
  • 「ダッシュボード」「tmux dashboard」
  • 「セッションに指示」「send-keys」

スクリプトパス

リモート (Lightsail) 上:

REPO=/home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata
CC=$REPO/ops/tmux-manager/cc-session.sh
SYNC=$REPO/ops/tmux-manager/sync-prs.sh

コマンド実行方法

全てのコマンドは SSH 経由で実行する。ssh lightsail のエイリアスが ~/.ssh/config に設定済み。

ダッシュボード表示

bash
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh dashboard"

セッション一覧

bash
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh list"

セッション状態確認

bash
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh status PR-45"

セッション出力キャプチャ

bash
# デフォルト100行
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh capture PR-45"

# 行数指定
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh capture PR-45 200"

セッション作成

bash
# PR 用
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh create PR-45"

# Issue 用
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh create ISSUE-123"

指示送信 (send-keys)

bash
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh send PR-45 'このPRのレビューコメントに対応して push してください'"

全 Open PR 同期

bash
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/sync-prs.sh --cleanup"

セッション終了

bash
ssh lightsail "cd /home/runner/actions-runner/_work/githubactions_fordata/githubactions_fordata && bash ops/tmux-manager/cc-session.sh kill PR-45"

ワークフロー

1. 全体状況確認

ユーザーが「セッション確認」「今の状態は?」と聞いた場合:

  1. dashboard コマンドで全体概要を表示
  2. 必要に応じて個別の status で詳細確認
  3. 結果をユーザーに分かりやすく要約して報告

2. PR 同期 + セッション作成

ユーザーが「PR 同期して」「全 PR のセッション作って」と言った場合:

  1. sync-prs.sh --cleanup で全 Open PR を同期
  2. 結果(作成数、スキップ数、クリーンアップ数)を報告

3. 特定セッションへの指示

ユーザーが「PR-45 にレビュー対応させて」と言った場合:

  1. status PR-45 で現在の状態を確認
  2. アイドル状態なら send PR-45 "指示内容" で指示を送信
  3. 作業中なら「現在作業中です。完了を待ちますか?」と確認

4. セッション出力の確認・要約

ユーザーが「PR-45 で何してる?」と聞いた場合:

  1. capture PR-45 100 で最新出力を取得
  2. 内容を要約してユーザーに報告

注意事項

  • SSH 接続がタイムアウトする場合は -o ConnectTimeout=10 を追加
  • 作業中のセッションに send-keys しない(状態を必ず確認)
  • セッション数は同時 5 以下を推奨(Lightsail リソース制約)
  • ログは ops/tmux-manager/logs/ に保存されている

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Tmux Session Manager AI skill do?

Lightsail上のClaude Code tmuxセッションをSSH経由で管理。 「セッション確認」「PR同期」「tmuxの状態」等のリクエストで発動。

Why use Tmux Session Manager on TypingMind?

Because you install it once and use it with any model. Tmux Session Manager is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Tmux Session Manager in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/minicoohei/ai-agent-camp/tree/main/.claude/skills/tmux-session-manager. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Tmux Session Manager?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Tmux Session Manager?

As many as you like. As long as a model supports skills, you can use Tmux Session Manager with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Tmux Session Manager AI skill free?

It is published on GitHub by minicoohei. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇