telemux 1.0.1__tar.gz → 1.0.3__tar.gz

{telemux-1.0.1/src/telemux.egg-info → telemux-1.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: telemux
-Version: 1.0.1
+Version: 1.0.3
 Summary: Bidirectional Telegram integration for tmux sessions - monitor commands and interact with agents
 Author-email: Marco Almazan <marco@example.com>
 License: MIT
@@ -124,8 +124,8 @@ telemux logs
 # Send a simple notification
 tg_alert "Build complete!"
 
-# Send a message and receive replies
-tg_agent "deploy-agent" "Ready to deploy to production?"
+# Send a message and receive replies (auto-detects tmux session name)
+tg_agent "Ready to deploy to production?"
 # Reply via Telegram: "session-name: yes"
 # The reply appears directly in your terminal
 
@@ -189,27 +189,26 @@ tg_alert "Deploy complete
 
 ### `tg_agent`
 
-Send messages and receive replies via Telegram:
+Send messages and receive replies via Telegram (automatically uses your tmux session name):
 
 ```bash
-tg_agent "agent-name" "Message text"
+tg_agent "Message text"
 ```
 
 **Examples:**
 
 ```bash
-# Ask a question
-tg_agent "deploy-agent" "Ready to deploy to production?"
+# Ask a question (inside a tmux session named "deploy")
+tg_agent "Ready to deploy to production?"
 
 # Wait for user response via Telegram
-# User replies: "session-name: yes, proceed"
+# User replies: "deploy: yes, proceed"
 # Reply appears in your terminal
 
-# Use in scripts
-response=$(tg_agent "approval-agent" "Approve release v2.0?")
-if [[ "$response" == *"yes"* ]]; then
-    ./deploy.sh
-fi
+# Use in scripts (inside a tmux session named "approval")
+tg_agent "Approve release v2.0?"
+# Returns the session name, user responds via Telegram
+# Check incoming message for approval
 ```
 
 ### `tg_done`
@@ -233,10 +232,10 @@ TeleMux uses **session-based routing** for bidirectional communication:
 
 ```bash
 # In tmux session named "deploy"
-tg_agent "deploy-check" "Should I proceed with deployment?"
+tg_agent "Should I proceed with deployment?"
 ```
 
-This sends a message to Telegram with instructions on how to reply.
+This sends a message to Telegram with instructions on how to reply. The session name is automatically detected.
 
 ### Replying from Telegram
 
@@ -368,11 +367,11 @@ fi
 
 ```bash
 #!/bin/bash
-# Deployment with approval
+# Deployment with approval (run in tmux session named "deploy")
 
-tg_agent "deploy-agent" "Ready to deploy v2.0 to production?"
+tg_agent "Ready to deploy v2.0 to production?"
 
-# User responds via Telegram: "session-name: yes"
+# User responds via Telegram: "deploy: yes"
 # Response appears in terminal
 
 read -p "Proceed with deployment? " response
@@ -386,19 +385,19 @@ fi
 
 ```bash
 #!/bin/bash
-# Complex workflow with multiple checkpoints
+# Complex workflow with multiple checkpoints (run in tmux session named "migration")
 
 tg_alert "Starting migration workflow..."
 
 # Step 1: Backup
-tg_agent "migration-agent" "Backup database before migration?"
+tg_agent "Backup database before migration?"
 # Wait for approval...
 
 # Step 2: Migration
 ./run-migration.sh && tg_done
 
 # Step 3: Verification
-tg_agent "migration-agent" "Verify migration results?"
+tg_agent "Verify migration results?"
 # Wait for verification...
 
 tg_alert "Migration workflow complete!"

{telemux-1.0.1 → telemux-1.0.3}/README.md

@@ -86,8 +86,8 @@ telemux logs
 # Send a simple notification
 tg_alert "Build complete!"
 
-# Send a message and receive replies
-tg_agent "deploy-agent" "Ready to deploy to production?"
+# Send a message and receive replies (auto-detects tmux session name)
+tg_agent "Ready to deploy to production?"
 # Reply via Telegram: "session-name: yes"
 # The reply appears directly in your terminal
 
@@ -151,27 +151,26 @@ tg_alert "Deploy complete
 
 ### `tg_agent`
 
-Send messages and receive replies via Telegram:
+Send messages and receive replies via Telegram (automatically uses your tmux session name):
 
 ```bash
-tg_agent "agent-name" "Message text"
+tg_agent "Message text"
 ```
 
 **Examples:**
 
 ```bash
-# Ask a question
-tg_agent "deploy-agent" "Ready to deploy to production?"
+# Ask a question (inside a tmux session named "deploy")
+tg_agent "Ready to deploy to production?"
 
 # Wait for user response via Telegram
-# User replies: "session-name: yes, proceed"
+# User replies: "deploy: yes, proceed"
 # Reply appears in your terminal
 
-# Use in scripts
-response=$(tg_agent "approval-agent" "Approve release v2.0?")
-if [[ "$response" == *"yes"* ]]; then
-    ./deploy.sh
-fi
+# Use in scripts (inside a tmux session named "approval")
+tg_agent "Approve release v2.0?"
+# Returns the session name, user responds via Telegram
+# Check incoming message for approval
 ```
 
 ### `tg_done`
@@ -195,10 +194,10 @@ TeleMux uses **session-based routing** for bidirectional communication:
 
 ```bash
 # In tmux session named "deploy"
-tg_agent "deploy-check" "Should I proceed with deployment?"
+tg_agent "Should I proceed with deployment?"
 ```
 
-This sends a message to Telegram with instructions on how to reply.
+This sends a message to Telegram with instructions on how to reply. The session name is automatically detected.
 
 ### Replying from Telegram
 
@@ -330,11 +329,11 @@ fi
 
 ```bash
 #!/bin/bash
-# Deployment with approval
+# Deployment with approval (run in tmux session named "deploy")
 
-tg_agent "deploy-agent" "Ready to deploy v2.0 to production?"
+tg_agent "Ready to deploy v2.0 to production?"
 
-# User responds via Telegram: "session-name: yes"
+# User responds via Telegram: "deploy: yes"
 # Response appears in terminal
 
 read -p "Proceed with deployment? " response
@@ -348,19 +347,19 @@ fi
 
 ```bash
 #!/bin/bash
-# Complex workflow with multiple checkpoints
+# Complex workflow with multiple checkpoints (run in tmux session named "migration")
 
 tg_alert "Starting migration workflow..."
 
 # Step 1: Backup
-tg_agent "migration-agent" "Backup database before migration?"
+tg_agent "Backup database before migration?"
 # Wait for approval...
 
 # Step 2: Migration
 ./run-migration.sh && tg_done
 
 # Step 3: Verification
-tg_agent "migration-agent" "Verify migration results?"
+tg_agent "Verify migration results?"
 # Wait for verification...
 
 tg_alert "Migration workflow complete!"

{telemux-1.0.1 → telemux-1.0.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "telemux"
-version = "1.0.1"
+version = "1.0.3"
 description = "Bidirectional Telegram integration for tmux sessions - monitor commands and interact with agents"
 readme = "README.md"
 requires-python = ">=3.7"

{telemux-1.0.1 → telemux-1.0.3}/src/telemux/__init__.py

@@ -2,7 +2,7 @@
 TeleMux - Bidirectional Telegram integration for tmux sessions
 """
 
-__version__ = "1.0.1"
+__version__ = "1.0.3"
 __author__ = "Marco Almazan"
 
 from pathlib import Path

{telemux-1.0.1 → telemux-1.0.3}/src/telemux/listener.py

@@ -243,7 +243,7 @@ def process_update(update: Dict[str, Any], bot_token: str, chat_id: str) -> None
         # tmux send-keys interprets special characters like $(), ``, &&, ;
         # Without sanitization, malicious input could execute arbitrary commands
         safe_response = shlex.quote(response)
-        formatted_message = f"{safe_response}\n # Respond using this terminal command: tg_agent \"{session_name}\" \"your response\""
+        formatted_message = f"{safe_response}\n # Respond using: tg_agent \"your response\""
 
         # Send message to tmux session
         result = subprocess.run(

{telemux-1.0.1 → telemux-1.0.3}/src/telemux/shell_functions.sh

@@ -41,18 +41,25 @@ tg_alert() {
 
 # Bidirectional agent alert - sends message and can receive replies
 tg_agent() {
-    local agent_name="$1"
-    local message="$2"
+    local message="$*"
 
-    if [[ -z "$agent_name" ]] || [[ -z "$message" ]]; then
-        echo "Usage: tg_agent <agent_name> <message>"
+    if [[ -z "$message" ]]; then
+        echo "Usage: tg_agent <message>"
         return 1
     fi
 
-    # Use tmux session name as message ID (much simpler!)
+    # Auto-detect tmux session name
     local tmux_session="$(tmux display-message -p '#S' 2>/dev/null || echo 'unknown')"
+    local agent_name="${tmux_session}"
     local msg_id="${tmux_session}"
 
+    # Check if we're in a tmux session
+    if [[ -z "$TMUX" ]]; then
+        echo "Warning: Not in a tmux session. Using 'terminal' as session name."
+        agent_name="terminal"
+        msg_id="terminal"
+    fi
+
     # Record mapping for listener daemon (backward compatibility)
     # NOTE: New routing doesn't require this, but kept for transition period
     mkdir -p "$HOME/.telemux/message_queue"
@@ -61,12 +68,12 @@ tg_agent() {
     # Send to Telegram with identifier
     curl -s -X POST "https://api.telegram.org/bot${TELEMUX_TG_BOT_TOKEN}/sendMessage" \
         -d chat_id="${TELEMUX_TG_CHAT_ID}" \
-        -d text="[>] <b>[${agent_name}:${msg_id}]</b>
+        -d text="[>] <b>[${agent_name}]</b>
 
 ${message}
 
 <i>Reply with: ${msg_id}: your response</i>" \
-        -d parse_mode="HTML" > /dev/null && echo "Agent alert sent: ${msg_id}"
+        -d parse_mode="HTML" > /dev/null && echo "Agent message sent from: ${msg_id}"
 
     echo "$msg_id"  # Return message ID
 }

{telemux-1.0.1 → telemux-1.0.3/src/telemux.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: telemux
-Version: 1.0.1
+Version: 1.0.3
 Summary: Bidirectional Telegram integration for tmux sessions - monitor commands and interact with agents
 Author-email: Marco Almazan <marco@example.com>
 License: MIT
@@ -124,8 +124,8 @@ telemux logs
 # Send a simple notification
 tg_alert "Build complete!"
 
-# Send a message and receive replies
-tg_agent "deploy-agent" "Ready to deploy to production?"
+# Send a message and receive replies (auto-detects tmux session name)
+tg_agent "Ready to deploy to production?"
 # Reply via Telegram: "session-name: yes"
 # The reply appears directly in your terminal
 
@@ -189,27 +189,26 @@ tg_alert "Deploy complete
 
 ### `tg_agent`
 
-Send messages and receive replies via Telegram:
+Send messages and receive replies via Telegram (automatically uses your tmux session name):
 
 ```bash
-tg_agent "agent-name" "Message text"
+tg_agent "Message text"
 ```
 
 **Examples:**
 
 ```bash
-# Ask a question
-tg_agent "deploy-agent" "Ready to deploy to production?"
+# Ask a question (inside a tmux session named "deploy")
+tg_agent "Ready to deploy to production?"
 
 # Wait for user response via Telegram
-# User replies: "session-name: yes, proceed"
+# User replies: "deploy: yes, proceed"
 # Reply appears in your terminal
 
-# Use in scripts
-response=$(tg_agent "approval-agent" "Approve release v2.0?")
-if [[ "$response" == *"yes"* ]]; then
-    ./deploy.sh
-fi
+# Use in scripts (inside a tmux session named "approval")
+tg_agent "Approve release v2.0?"
+# Returns the session name, user responds via Telegram
+# Check incoming message for approval
 ```
 
 ### `tg_done`
@@ -233,10 +232,10 @@ TeleMux uses **session-based routing** for bidirectional communication:
 
 ```bash
 # In tmux session named "deploy"
-tg_agent "deploy-check" "Should I proceed with deployment?"
+tg_agent "Should I proceed with deployment?"
 ```
 
-This sends a message to Telegram with instructions on how to reply.
+This sends a message to Telegram with instructions on how to reply. The session name is automatically detected.
 
 ### Replying from Telegram
 
@@ -368,11 +367,11 @@ fi
 
 ```bash
 #!/bin/bash
-# Deployment with approval
+# Deployment with approval (run in tmux session named "deploy")
 
-tg_agent "deploy-agent" "Ready to deploy v2.0 to production?"
+tg_agent "Ready to deploy v2.0 to production?"
 
-# User responds via Telegram: "session-name: yes"
+# User responds via Telegram: "deploy: yes"
 # Response appears in terminal
 
 read -p "Proceed with deployment? " response
@@ -386,19 +385,19 @@ fi
 
 ```bash
 #!/bin/bash
-# Complex workflow with multiple checkpoints
+# Complex workflow with multiple checkpoints (run in tmux session named "migration")
 
 tg_alert "Starting migration workflow..."
 
 # Step 1: Backup
-tg_agent "migration-agent" "Backup database before migration?"
+tg_agent "Backup database before migration?"
 # Wait for approval...
 
 # Step 2: Migration
 ./run-migration.sh && tg_done
 
 # Step 3: Verification
-tg_agent "migration-agent" "Verify migration results?"
+tg_agent "Verify migration results?"
 # Wait for verification...
 
 tg_alert "Migration workflow complete!"