@dmsdc-ai/aigentry-telepty 0.1.4 → 0.1.6

package/.claude/commands/telepty-allow.md

@@ -0,0 +1,58 @@
+# telepty-allow
+
+Allow inject on an LLM CLI (or any command) via telepty.
+
+## Instructions
+
+### Usage
+```bash
+telepty allow [--id <session_id>] -- <command> [args...]
+```
+
+### Examples
+```bash
+# Claude Code with custom session ID
+telepty allow --id my-claude -- claude
+
+# Codex with auto-generated ID
+telepty allow -- codex
+
+# Gemini with custom ID
+telepty allow --id gemini-main -- gemini
+
+# Any shell command
+telepty allow --id dev-shell -- bash
+```
+
+### What it does
+1. Registers the session with the telepty daemon
+2. Spawns the command locally via `node-pty` (preserves isTTY, raw mode, colors)
+3. Connects to daemon as WebSocket owner for inject reception
+4. Sets `TELEPTY_SESSION_ID` env var inside the process
+
+### Key behaviors
+- **isTTY preserved**: TUI apps (claude, codex, gemini) work normally
+- **Daemon fault-tolerant**: if daemon dies, the CLI keeps running (inject unavailable until reconnect)
+- **Session auto-cleanup**: when the command exits, session is deregistered
+
+### After allowing, from another terminal:
+```bash
+# List sessions
+telepty list
+
+# Inject into the session
+telepty inject <session_id> "your prompt here"
+
+# Attach to watch output
+telepty attach <session_id>
+```
+
+## Execute
+If the user provides arguments, run the allow command for them:
+
+```bash
+cd /Users/duckyoungkim/projects/aigentry-telepty
+node cli.js allow $ARGUMENTS
+```
+
+If no arguments, show the usage guide above and ask what they want to run.

package/.claude/commands/telepty-attach.md

@@ -0,0 +1,22 @@
+# telepty-attach
+
+Attach to an active telepty session to observe its output in real-time.
+
+## Instructions
+
+### Execute
+```bash
+cd /Users/duckyoungkim/projects/aigentry-telepty && node cli.js attach $ARGUMENTS
+```
+
+### If no arguments
+1. List available sessions: `node cli.js list`
+2. Ask the user which session to attach to
+
+### Notes
+- For **spawned** sessions: you can both view output and send input
+- For **wrapped** sessions: input from attached clients is forwarded to the owner as inject
+- Press `Ctrl+C` to detach without killing the session
+
+## Arguments
+- `$ARGUMENTS`: session ID to attach to

package/.claude/commands/telepty-inject.md

@@ -0,0 +1,34 @@
+# telepty-inject
+
+Inject a prompt into a telepty session (spawned or wrapped).
+
+## Instructions
+
+Parse `$ARGUMENTS` to extract target session ID and prompt text.
+
+### Format
+```
+<session_id> <prompt text>
+```
+
+### Execute
+```bash
+cd /Users/duckyoungkim/projects/aigentry-telepty && node cli.js inject $ARGUMENTS
+```
+
+### If no arguments
+1. List available sessions: `node cli.js list`
+2. Ask the user which session to target and what to inject
+
+### Multicast (multiple targets)
+```bash
+node cli.js multicast <id1>,<id2> "<prompt>"
+```
+
+### Broadcast (all sessions)
+```bash
+node cli.js broadcast "<prompt>"
+```
+
+## Arguments
+- `$ARGUMENTS`: `<session_id> "<prompt>"` or empty for interactive mode

package/.claude/commands/telepty-list.md

@@ -0,0 +1,22 @@
+# telepty-list
+
+List all active telepty sessions with their types and status.
+
+## Instructions
+
+1. Run:
+```bash
+cd /Users/duckyoungkim/projects/aigentry-telepty && node cli.js list
+```
+
+2. If the daemon is not running, tell the user and suggest `/project:telepty-start`.
+
+3. Format the output as a clear table showing:
+   - Session ID
+   - Type (spawned / wrapped)
+   - Command
+   - Active clients
+   - Created time
+
+## Arguments
+- `$ARGUMENTS`: ignored

package/.claude/commands/telepty-manual-test.md

@@ -0,0 +1,73 @@
+# telepty-manual-test
+
+Guided manual test of the telepty enable (inject) feature. Runs step-by-step verification.
+
+## Instructions
+
+Execute each step sequentially, verifying results before proceeding.
+
+### Step 1: Ensure daemon is running
+```bash
+cd /Users/duckyoungkim/projects/aigentry-telepty
+curl -s http://127.0.0.1:3848/api/sessions 2>/dev/null || node daemon.js &
+sleep 1
+```
+
+### Step 2: Register a wrapped session via API
+```bash
+TOKEN=$(cat ~/.telepty/config.json 2>/dev/null | grep authToken | cut -d '"' -f 4)
+curl -s -X POST http://127.0.0.1:3848/api/sessions/register \
+  -H "Content-Type: application/json" \
+  -H "x-telepty-token: $TOKEN" \
+  -d '{"session_id": "manual-test-1", "command": "test", "cwd": "'"$(pwd)"'"}'
+```
+**Verify**: response has `type: "wrapped"` and status 201.
+
+### Step 3: Check session listing
+```bash
+curl -s http://127.0.0.1:3848/api/sessions -H "x-telepty-token: $TOKEN" | python3 -m json.tool
+```
+**Verify**: `manual-test-1` appears with `type: "wrapped"`.
+
+### Step 4: Test inject without owner (should fail)
+```bash
+curl -s -X POST http://127.0.0.1:3848/api/sessions/manual-test-1/inject \
+  -H "Content-Type: application/json" \
+  -H "x-telepty-token: $TOKEN" \
+  -d '{"prompt": "hello"}'
+```
+**Verify**: returns 503 with "not connected" error.
+
+### Step 5: Clean up test session
+```bash
+curl -s -X DELETE http://127.0.0.1:3848/api/sessions/manual-test-1 \
+  -H "x-telepty-token: $TOKEN"
+```
+**Verify**: returns status "closing".
+
+### Step 6: Verify session removed
+```bash
+curl -s http://127.0.0.1:3848/api/sessions -H "x-telepty-token: $TOKEN"
+```
+**Verify**: `manual-test-1` no longer in the list.
+
+### Step 7: Run automated tests
+```bash
+npm test
+```
+**Verify**: all 25 tests pass.
+
+### Report
+Summarize all verification results in a table:
+
+| Step | Check | Result |
+|------|-------|--------|
+| 2 | Register returns 201 + wrapped | ? |
+| 3 | Session in list with type | ? |
+| 4 | Inject without owner = 503 | ? |
+| 5 | DELETE returns closing | ? |
+| 6 | Session removed | ? |
+| 7 | All tests pass | ? |
+
+## Arguments
+- `$ARGUMENTS`: ignored

package/.claude/commands/telepty-start.md

@@ -0,0 +1,25 @@
+# telepty-start
+
+Start the telepty daemon process.
+
+## Instructions
+
+1. Check if daemon is already running:
+```bash
+curl -s http://127.0.0.1:3848/api/sessions 2>/dev/null && echo "RUNNING" || echo "NOT RUNNING"
+```
+
+2. If not running, start it:
+```bash
+cd /Users/duckyoungkim/projects/aigentry-telepty && node daemon.js &
+```
+
+3. Verify it started:
+```bash
+sleep 1 && curl -s http://127.0.0.1:3848/api/sessions
+```
+
+4. Report status.
+
+## Arguments
+- `$ARGUMENTS`: optional port override (e.g., "3849")

package/.claude/commands/telepty-test.md

@@ -0,0 +1,25 @@
+# telepty-test
+
+Run the telepty automated test suite and report results.
+
+## Instructions
+
+1. Run the full test suite:
+```bash
+cd /Users/duckyoungkim/projects/aigentry-telepty && npm test
+```
+
+2. Parse the output and report:
+   - Total tests, passed, failed
+   - If any failures: show the failing test name and error message
+   - If all pass: confirm with count
+
+3. If tests fail, investigate:
+   - Read the failing test in `test/daemon.test.js`
+   - Check if daemon.js has related issues
+   - Suggest or apply fixes
+   - Re-run tests to confirm
+
+## Arguments
+- No arguments: run all tests
+- `$ARGUMENTS`: if provided, use as a grep filter to run specific tests (e.g., "wrap", "register", "inject")

package/.claude/commands/telepty.md

@@ -0,0 +1,82 @@
+# telepty
+
+Help the user interact with the `telepty` daemon — check session IDs, list active sessions, inject commands, send bus events, and manage terminal windows.
+
+## Trigger
+
+When the user asks about their current session ID, wants to check/list active sessions, inject a prompt into a session, send a JSON event via the bus, subscribe to the bus, rename a session, or update telepty.
+
+## Instructions
+
+### 1. Check Current Session ID
+- Run: `echo $TELEPTY_SESSION_ID`
+- If empty: this shell is NOT inside a telepty session.
+- If set: display it. This is the ID other agents use to target this session.
+
+### 2. List All Sessions
+- Run: `telepty list`
+
+### 3. Send a Message to Another Agent
+Choose ONE of three methods based on intent:
+
+**Method A: Prompt Injection (Active Interruption)**
+The receiving AI will IMMEDIATELY read and execute the message as a prompt.
+```bash
+telepty inject <target_session_id> "<prompt text>"
+```
+For multiple targets: `telepty multicast <id1>,<id2> "<prompt>"`
+
+**Method B: Log Injection (Visual Notification)**
+The message appears on the receiving terminal screen for the user to see, but the AI does NOT execute it as a prompt.
+```bash
+telepty inject <target_session_id> "echo '\x1b[33m[Message from $TELEPTY_SESSION_ID]\x1b[0m <message text>'"
+```
+
+**Method C: Background JSON Bus (Passive/Silent)**
+Structured data transfer that won't disturb the receiving terminal screen.
+```bash
+TOKEN=$(cat ~/.telepty/config.json | grep authToken | cut -d '"' -f 4)
+curl -s -X POST http://127.0.0.1:3848/api/bus/publish \
+  -H "Content-Type: application/json" \
+  -H "x-telepty-token: $TOKEN" \
+  -d '{"type": "bg_message", "payload": "..."}'
+```
+
+### 4. Subscribe to the Event Bus
+```bash
+nohup telepty listen > .telepty_bus_events.log 2>&1 &
+```
+
+### 5. Open a New Ghostty Terminal Window
+Physically spawn a new terminal window already attached to a telepty session:
+```bash
+cat << 'EOF' > /tmp/telepty-auto.command
+#!/bin/bash
+telepty spawn --id <ID> <CMD>
+EOF
+chmod +x /tmp/telepty-auto.command
+open -a Ghostty /tmp/telepty-auto.command || open /tmp/telepty-auto.command
+```
+
+### 6. Terminal Title Convention
+Each telepty session displays its ID in the Ghostty tab title:
+- Local: `⚡ telepty :: {session_id}`
+- Remote: `⚡ telepty :: {session_id} @ {host}`
+
+### 7. Allow Inject on a CLI
+Run any command with inject allowed:
+```bash
+# With custom session ID
+telepty allow --id my-claude -- claude
+telepty allow --id codex-main -- codex
+telepty allow --id gemini-1 -- gemini
+
+# Auto-generated session ID
+telepty allow -- bash
+```
+The process runs locally (isTTY preserved), but registers with the daemon so inject works.
+
+### 8. Update
+```bash
+telepty update
+```

package/.gemini/skills/telepty/SKILL.md

@@ -33,5 +33,23 @@ When the user asks about their current session ID, wants to check active session
      ```
 4. **To subscribe to the Event Bus (Listen for JSON events):**
    - Run `nohup telepty listen > .telepty_bus_events.log 2>&1 &`
-5. **To update telepty:**
+5. **To physically OPEN a new Terminal Window for the user (macOS):**
+   - If the user asks you to "open a new telepty terminal" or "방 파줘", you can physically spawn a new Ghostty/Terminal window on their screen that is already attached to a telepty session.
+   - Run this shell command (replace `<ID>` and `<CMD>`):
+     ```bash
+     cat << 'EOF' > /tmp/telepty-auto.command
+     #!/bin/bash
+     telepty spawn --id <ID> <CMD>
+     EOF
+     chmod +x /tmp/telepty-auto.command
+     open -a Ghostty /tmp/telepty-auto.command || open /tmp/telepty-auto.command
+     ```
+6. **To rename a session:**
+   - Run `telepty rename <old_id> <new_id>`
+   - This updates the session key, Ghostty tab title, and broadcasts a `session_rename` event on the bus.
+7. **Terminal Title Convention:**
+   - Each telepty session displays its ID in the Ghostty tab title.
+   - Local: `⚡ telepty :: {session_id}`
+   - Remote: `⚡ telepty :: {session_id} @ {host}`
+8. **To update telepty:**
    - Run `telepty update`.

package/.github/workflows/test-install.yml

@@ -1,32 +1,26 @@
-name: Test Installation Scripts
+name: Regression Tests
 on:
   push:
     branches: [ "main" ]
   pull_request:
     branches: [ "main" ]
+  workflow_dispatch:
 
 jobs:
-  test-windows:
-    runs-on: windows-latest
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        node: [20]
+    runs-on: ${{ matrix.os }}
     steps:
-      - uses: actions/checkout@v3
-      - name: Run Install Script
-        shell: powershell
-        run: |
-          ./install.ps1
-
-  test-ubuntu:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      - name: Run Install Script
-        run: |
-          bash ./install.sh
-
-  test-macos:
-    runs-on: macos-latest
-    steps:
-      - uses: actions/checkout@v3
-      - name: Run Install Script
-        run: |
-          bash ./install.sh
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node }}
+          cache: npm
+      - name: Install dependencies
+        run: npm ci
+      - name: Run regression suite
+        run: npm run test:ci

package/README.md

@@ -39,3 +39,19 @@ iwr -useb https://raw.githubusercontent.com/dmsdc-ai/aigentry-telepty/main/insta
    ```bash
    telepty inject my-session "echo 'Hello from nowhere!'"
    ```
+
+## Testing
+
+Run the full regression suite locally:
+
+```bash
+npm test
+```
+
+Keep the suite running while you work:
+
+```bash
+npm run test:watch
+```
+
+The automated suite covers config generation, daemon HTTP APIs, WebSocket attach/output flow, bus events, session deletion regressions, and CLI smoke tests against a real daemon process.