hcom 0.1.5__tar.gz → 0.1.7__tar.gz

{hcom-0.1.5/src/hcom.egg-info → hcom-0.1.7}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: hcom
-Version: 0.1.5
-Summary: Lightweight CLI tool for real-time messaging between Claude Code subagents using hooks
+Version: 0.1.7
+Summary: Lightweight CLI tool for real-time communication between Claude Code subagents using hooks
 Author-email: aannoo <your@email.com>
 License: MIT
 Project-URL: Homepage, https://github.com/aannoo/claude-hook-comms
@@ -26,9 +26,9 @@ Classifier: Topic :: Communications
 Requires-Python: >=3.6
 Description-Content-Type: text/markdown
 
-# Claude Code Hook Comms
+# hcom - Claude Hook Comms
 
-Lightweight CLI tool for real-time communication between claude code [subagents](https://docs.anthropic.com/en/docs/claude-code/sub-agents) using [hooks](https://docs.anthropic.com/en/docs/claude-code/hooks).
+Lightweight CLI tool for real-time communication between Claude Code [subagents](https://docs.anthropic.com/en/docs/claude-code/sub-agents) using [hooks](https://docs.anthropic.com/en/docs/claude-code/hooks).
 
 ## 🦆 What It Does
 
@@ -38,7 +38,7 @@ Creates a group chat where you and multiple interactive Claude Code subagents ca
 
 ## 🦷 Features
 
-- **Multi-Terminal Launch** - Launch claude code subagents in new terminals
+- **Multi-Terminal Launch** - Launch Claude Code subagents in new terminals
 - **Live Dashboard** - Real-time monitoring of all instances
 - **Multi-Agent Communication** - Claude instances talk to each other across projects
 - **@Mention Targeting** - Send messages to specific subagents or teams
@@ -100,11 +100,12 @@ cd backend && hcom open api-specialist
 cd ../frontend && hcom open ui-specialist
 
 # Create named teams that can be @mentioned
-cd ~/api && hcom open --prefix api debugger
-cd ~/auth && hcom open --prefix auth debugger
+cd ~/api && hcom open --prefix api debugger  # Creates api-hovoa7
+cd ~/auth && hcom open --prefix auth debugger  # Creates auth-hovob8
 
-# Message specific teams
-hcom send "@api login works but API fails" # or in dashboard: hcom watch
+# Message specific teams or instances
+hcom send "@api login works but API fails"  # Messages all api-* instances
+hcom send "@hovoa7 can you check this?"     # Message specific instance by name
 ```
 
 
@@ -120,7 +121,7 @@ hcom send "@api login works but API fails" # or in dashboard: hcom watch
 ### Automation Commands
 | Command | Description |
 |---------|-------------|
-| `hcom send 'message'` | Send message |
+| `hcom send 'message'` | Send message to chat |
 | `hcom watch --logs` | View message history (non-interactive) |
 | `hcom watch --status` | Show instance status (non-interactive) |
 | `hcom watch --wait [timeout]` | Wait and notify for new messages |
@@ -195,18 +196,18 @@ HCOM_MAX_MESSAGE_SIZE=8192 hcom send "$(cat long_report.txt)"
 
 hcom adds hooks to your project directory's `.claude/settings.local.json`:
 
-1. **Sending**: Claude writes messages with `echo "HCOM_SEND:message"` - captured by PostToolUse hook
+1. **Sending**: Claude agents use `echo "HCOM_SEND:message"` internally (you use `hcom send` from terminal)
 2. **Receiving**: Other Claudes get notified via Stop hook
 3. **Waiting**: Stop hook keeps Claude in a waiting state for new messages
 
 - **Identity**: Each instance gets a unique name based on conversation UUID (e.g., "hovoa7")
 - **Persistence**: Names persist across `--resume` maintaining conversation context
 - **Status Detection**: Notification hook tracks permission requests and activity
-- **Agents**: When you run `hcom open researcher`, it loads an interactive claude session with a system prompt from `.claude/agents/researcher.md` (local) or `~/.claude/agents/researcher.md` (global). Agents can specify `model:` and `tools:` in YAML frontmatter
+- **Agents**: When you run `hcom open researcher`, it loads an interactive Claude session with a system prompt from `.claude/agents/researcher.md` (local) or `~/.claude/agents/researcher.md` (global). Agents can specify `model:` and `tools:` in YAML frontmatter
 
 ### Architecture
 - **Single conversation** - All instances share one global conversation
-- **Opt-in participation** - Only claude code instances launched with `hcom open` join the chat
+- **Opt-in participation** - Only Claude Code instances launched with `hcom open` join the chat
 - **@-mention filtering** - Target messages to specific instances or teams
 
 ### File Structure

{hcom-0.1.5 → hcom-0.1.7}/README.md

@@ -1,6 +1,6 @@
-# Claude Code Hook Comms
+# hcom - Claude Hook Comms
 
-Lightweight CLI tool for real-time communication between claude code [subagents](https://docs.anthropic.com/en/docs/claude-code/sub-agents) using [hooks](https://docs.anthropic.com/en/docs/claude-code/hooks).
+Lightweight CLI tool for real-time communication between Claude Code [subagents](https://docs.anthropic.com/en/docs/claude-code/sub-agents) using [hooks](https://docs.anthropic.com/en/docs/claude-code/hooks).
 
 ## 🦆 What It Does
 
@@ -10,7 +10,7 @@ Creates a group chat where you and multiple interactive Claude Code subagents ca
 
 ## 🦷 Features
 
-- **Multi-Terminal Launch** - Launch claude code subagents in new terminals
+- **Multi-Terminal Launch** - Launch Claude Code subagents in new terminals
 - **Live Dashboard** - Real-time monitoring of all instances
 - **Multi-Agent Communication** - Claude instances talk to each other across projects
 - **@Mention Targeting** - Send messages to specific subagents or teams
@@ -72,11 +72,12 @@ cd backend && hcom open api-specialist
 cd ../frontend && hcom open ui-specialist
 
 # Create named teams that can be @mentioned
-cd ~/api && hcom open --prefix api debugger
-cd ~/auth && hcom open --prefix auth debugger
+cd ~/api && hcom open --prefix api debugger  # Creates api-hovoa7
+cd ~/auth && hcom open --prefix auth debugger  # Creates auth-hovob8
 
-# Message specific teams
-hcom send "@api login works but API fails" # or in dashboard: hcom watch
+# Message specific teams or instances
+hcom send "@api login works but API fails"  # Messages all api-* instances
+hcom send "@hovoa7 can you check this?"     # Message specific instance by name
 ```
 
 
@@ -92,7 +93,7 @@ hcom send "@api login works but API fails" # or in dashboard: hcom watch
 ### Automation Commands
 | Command | Description |
 |---------|-------------|
-| `hcom send 'message'` | Send message |
+| `hcom send 'message'` | Send message to chat |
 | `hcom watch --logs` | View message history (non-interactive) |
 | `hcom watch --status` | Show instance status (non-interactive) |
 | `hcom watch --wait [timeout]` | Wait and notify for new messages |
@@ -167,18 +168,18 @@ HCOM_MAX_MESSAGE_SIZE=8192 hcom send "$(cat long_report.txt)"
 
 hcom adds hooks to your project directory's `.claude/settings.local.json`:
 
-1. **Sending**: Claude writes messages with `echo "HCOM_SEND:message"` - captured by PostToolUse hook
+1. **Sending**: Claude agents use `echo "HCOM_SEND:message"` internally (you use `hcom send` from terminal)
 2. **Receiving**: Other Claudes get notified via Stop hook
 3. **Waiting**: Stop hook keeps Claude in a waiting state for new messages
 
 - **Identity**: Each instance gets a unique name based on conversation UUID (e.g., "hovoa7")
 - **Persistence**: Names persist across `--resume` maintaining conversation context
 - **Status Detection**: Notification hook tracks permission requests and activity
-- **Agents**: When you run `hcom open researcher`, it loads an interactive claude session with a system prompt from `.claude/agents/researcher.md` (local) or `~/.claude/agents/researcher.md` (global). Agents can specify `model:` and `tools:` in YAML frontmatter
+- **Agents**: When you run `hcom open researcher`, it loads an interactive Claude session with a system prompt from `.claude/agents/researcher.md` (local) or `~/.claude/agents/researcher.md` (global). Agents can specify `model:` and `tools:` in YAML frontmatter
 
 ### Architecture
 - **Single conversation** - All instances share one global conversation
-- **Opt-in participation** - Only claude code instances launched with `hcom open` join the chat
+- **Opt-in participation** - Only Claude Code instances launched with `hcom open` join the chat
 - **@-mention filtering** - Target messages to specific instances or teams
 
 ### File Structure

{hcom-0.1.5 → hcom-0.1.7}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "hcom"
-version = "0.1.5"
-description = "Lightweight CLI tool for real-time messaging between Claude Code subagents using hooks"
+version = "0.1.7"
+description = "Lightweight CLI tool for real-time communication between Claude Code subagents using hooks"
 readme = "README.md"
 requires-python = ">=3.6"
 license = {text = "MIT"}

{hcom-0.1.5 → hcom-0.1.7}/src/hcom/__init__.py

@@ -1,3 +1,3 @@
 """Claude Hook Comms - Real-time messaging between Claude Code agents."""
 
-__version__ = "0.1.5"
+__version__ = "0.1.7"

{hcom-0.1.5 → hcom-0.1.7}/src/hcom/__main__.py

@@ -1,7 +1,7 @@
 #!/usr/bin/env python3
 """
 hcom - Claude Hook Comms
-A lightweight multi-agent communication system for claude code
+Lightweight CLI tool for real-time communication between Claude Code subagents using hooks
 """
 
 import os
@@ -170,27 +170,22 @@ def get_config_value(key, default=None):
     return config.get(key, default)
 
 def get_hook_command():
-    """Determine the best hook command approach based on paths"""
+    """Get hook command with silent fallback
+    
+    Uses ${HCOM:-true} for clean paths, conditional for paths with spaces.
+    Both approaches exit silently (code 0) when not launched via 'hcom open'.
+    """
     python_path = sys.executable
     script_path = os.path.abspath(__file__)
     
-    # Characters that cause issues in shell expansion
-    problematic_chars = [' ', '`', '"', "'", '\\', '\n', ';', '&', '|', '(', ')', ':', 
-                        '$', '*', '?', '[', ']', '{', '}', '!', '~', '<', '>']
-    
-    has_problematic_chars = any(char in python_path or char in script_path 
-                               for char in problematic_chars)
-    
-    if has_problematic_chars:
-        # Use direct paths with proper escaping
-        # Escape backslashes first, then quotes
-        escaped_python = python_path.replace('\\', '\\\\').replace('"', '\\"')
-        escaped_script = script_path.replace('\\', '\\\\').replace('"', '\\"')
-        return f'"{escaped_python}" "{escaped_script}"', {}
+    if ' ' in python_path or ' ' in script_path:
+        # Paths with spaces: use conditional check
+        escaped_python = shlex.quote(python_path)
+        escaped_script = shlex.quote(script_path)
+        return f'[ "${{HCOM_ACTIVE}}" = "1" ] && {escaped_python} {escaped_script} || true', {}
     else:
-        # Use single clean env var
-        env_vars = {'HCOM': f'{python_path} {script_path}'}
-        return '$HCOM', env_vars
+        # Clean paths: use environment variable
+        return '${HCOM:-true}', {}
 
 def build_claude_env():
     """Build environment variables for Claude instances"""
@@ -206,9 +201,11 @@ def build_claude_env():
     
     env.update(config.get('env_overrides', {}))
     
-    # Add hook-specific env vars if using that approach
-    _, hook_env_vars = get_hook_command()
-    env.update(hook_env_vars)
+    # Set HCOM only for clean paths (spaces handled differently)
+    python_path = sys.executable
+    script_path = os.path.abspath(__file__)
+    if ' ' not in python_path and ' ' not in script_path:
+        env['HCOM'] = f'{python_path} {script_path}'
     
     return env
 
@@ -423,15 +420,22 @@ def _remove_hcom_hooks_from_settings(settings):
     
     # Patterns to match any hcom hook command
     # - $HCOM post/stop/notify
+    # - ${HCOM:-...} post/stop/notify
+    # - [ "${HCOM_ACTIVE}" = "1" ] && ... hcom.py ... || true
     # - hcom post/stop/notify  
+    # - uvx hcom post/stop/notify
     # - /path/to/hcom.py post/stop/notify
+    # - sh -c "[ ... ] && ... hcom ..."
     # - "/path with spaces/python" "/path with spaces/hcom.py" post/stop/notify
     # - '/path/to/python' '/path/to/hcom.py' post/stop/notify
     hcom_patterns = [
-        r'\$HCOM\s+(post|stop|notify)\b',           # Environment variable
+        r'\$\{?HCOM',                                # Environment variable (with or without braces)
+        r'\bHCOM_ACTIVE.*hcom\.py',                 # Conditional with HCOM_ACTIVE check
         r'\bhcom\s+(post|stop|notify)\b',           # Direct hcom command
+        r'\buvx\s+hcom\s+(post|stop|notify)\b',     # uvx hcom command
         r'hcom\.py["\']?\s+(post|stop|notify)\b',   # hcom.py with optional quote
         r'["\'][^"\']*hcom\.py["\']?\s+(post|stop|notify)\b',  # Quoted path with hcom.py
+        r'sh\s+-c.*hcom',                           # Shell wrapper with hcom
     ]
     compiled_patterns = [re.compile(pattern) for pattern in hcom_patterns]
     
@@ -713,7 +717,7 @@ def setup_hooks():
     if hcom_send_permission not in settings['permissions']['allow']:
         settings['permissions']['allow'].append(hcom_send_permission)
     
-    # Get the hook command approach (env vars or direct paths based on spaces)
+    # Get the hook command template
     hook_cmd_base, _ = get_hook_command()
     
     # Add PostToolUse hook
@@ -1280,18 +1284,21 @@ def cmd_help():
 
 Usage:
   hcom open [n]                Launch n Claude instances
+  hcom open <agent>            Launch named agent from .claude/agents/
   hcom open --prefix name n    Launch with name prefix
   hcom watch                   View conversation dashboard
-  hcom clear                 Clear and archive conversation
-  hcom cleanup               Remove hooks from current directory
-  hcom cleanup --all         Remove hooks from all tracked directories
-  hcom help                  Show this help
+  hcom clear                   Clear and archive conversation
+  hcom cleanup                 Remove hooks from current directory
+  hcom cleanup --all           Remove hooks from all tracked directories
+  hcom help                    Show this help
 
 Automation:
-  hcom send 'msg'            Send message
-  hcom send '@prefix msg'    Send to specific instances
-  hcom watch --logs          Show logs
-  hcom watch --status        Show status""")
+  hcom send 'msg'              Send message
+  hcom send '@prefix msg'      Send to specific instances
+  hcom watch --logs            Show logs
+  hcom watch --status          Show status
+
+Docs: https://raw.githubusercontent.com/aannoo/claude-hook-comms/main/README.md""")
     return 0
 
 def cmd_open(*args):

{hcom-0.1.5 → hcom-0.1.7/src/hcom.egg-info}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: hcom
-Version: 0.1.5
-Summary: Lightweight CLI tool for real-time messaging between Claude Code subagents using hooks
+Version: 0.1.7
+Summary: Lightweight CLI tool for real-time communication between Claude Code subagents using hooks
 Author-email: aannoo <your@email.com>
 License: MIT
 Project-URL: Homepage, https://github.com/aannoo/claude-hook-comms
@@ -26,9 +26,9 @@ Classifier: Topic :: Communications
 Requires-Python: >=3.6
 Description-Content-Type: text/markdown
 
-# Claude Code Hook Comms
+# hcom - Claude Hook Comms
 
-Lightweight CLI tool for real-time communication between claude code [subagents](https://docs.anthropic.com/en/docs/claude-code/sub-agents) using [hooks](https://docs.anthropic.com/en/docs/claude-code/hooks).
+Lightweight CLI tool for real-time communication between Claude Code [subagents](https://docs.anthropic.com/en/docs/claude-code/sub-agents) using [hooks](https://docs.anthropic.com/en/docs/claude-code/hooks).
 
 ## 🦆 What It Does
 
@@ -38,7 +38,7 @@ Creates a group chat where you and multiple interactive Claude Code subagents ca
 
 ## 🦷 Features
 
-- **Multi-Terminal Launch** - Launch claude code subagents in new terminals
+- **Multi-Terminal Launch** - Launch Claude Code subagents in new terminals
 - **Live Dashboard** - Real-time monitoring of all instances
 - **Multi-Agent Communication** - Claude instances talk to each other across projects
 - **@Mention Targeting** - Send messages to specific subagents or teams
@@ -100,11 +100,12 @@ cd backend && hcom open api-specialist
 cd ../frontend && hcom open ui-specialist
 
 # Create named teams that can be @mentioned
-cd ~/api && hcom open --prefix api debugger
-cd ~/auth && hcom open --prefix auth debugger
+cd ~/api && hcom open --prefix api debugger  # Creates api-hovoa7
+cd ~/auth && hcom open --prefix auth debugger  # Creates auth-hovob8
 
-# Message specific teams
-hcom send "@api login works but API fails" # or in dashboard: hcom watch
+# Message specific teams or instances
+hcom send "@api login works but API fails"  # Messages all api-* instances
+hcom send "@hovoa7 can you check this?"     # Message specific instance by name
 ```
 
 
@@ -120,7 +121,7 @@ hcom send "@api login works but API fails" # or in dashboard: hcom watch
 ### Automation Commands
 | Command | Description |
 |---------|-------------|
-| `hcom send 'message'` | Send message |
+| `hcom send 'message'` | Send message to chat |
 | `hcom watch --logs` | View message history (non-interactive) |
 | `hcom watch --status` | Show instance status (non-interactive) |
 | `hcom watch --wait [timeout]` | Wait and notify for new messages |
@@ -195,18 +196,18 @@ HCOM_MAX_MESSAGE_SIZE=8192 hcom send "$(cat long_report.txt)"
 
 hcom adds hooks to your project directory's `.claude/settings.local.json`:
 
-1. **Sending**: Claude writes messages with `echo "HCOM_SEND:message"` - captured by PostToolUse hook
+1. **Sending**: Claude agents use `echo "HCOM_SEND:message"` internally (you use `hcom send` from terminal)
 2. **Receiving**: Other Claudes get notified via Stop hook
 3. **Waiting**: Stop hook keeps Claude in a waiting state for new messages
 
 - **Identity**: Each instance gets a unique name based on conversation UUID (e.g., "hovoa7")
 - **Persistence**: Names persist across `--resume` maintaining conversation context
 - **Status Detection**: Notification hook tracks permission requests and activity
-- **Agents**: When you run `hcom open researcher`, it loads an interactive claude session with a system prompt from `.claude/agents/researcher.md` (local) or `~/.claude/agents/researcher.md` (global). Agents can specify `model:` and `tools:` in YAML frontmatter
+- **Agents**: When you run `hcom open researcher`, it loads an interactive Claude session with a system prompt from `.claude/agents/researcher.md` (local) or `~/.claude/agents/researcher.md` (global). Agents can specify `model:` and `tools:` in YAML frontmatter
 
 ### Architecture
 - **Single conversation** - All instances share one global conversation
-- **Opt-in participation** - Only claude code instances launched with `hcom open` join the chat
+- **Opt-in participation** - Only Claude Code instances launched with `hcom open` join the chat
 - **@-mention filtering** - Target messages to specific instances or teams
 
 ### File Structure