claude-tempo 0.1.2 → 0.2.0

package/CLAUDE.md

@@ -16,6 +16,7 @@ claude-tempo is an MCP server that enables multiple Claude Code sessions to coor
 ```
 src/
 ├── server.ts          # MCP server entry point
+├── copilot-bridge.ts  # Copilot SDK bridge for Copilot CLI players
 ├── worker.ts          # Temporal worker setup
 ├── workflows/
 │   ├── session.ts     # claude-session workflow

package/README.md

@@ -155,7 +155,8 @@ The `claude-tempo` CLI handles setup, session management, and diagnostics.
 
 ```
 --temporal-address <addr>   Temporal server address (default: localhost:7233)
--n, --name <name>           Set the session window name (start/conduct/up)
+-n, --name <name>           Set the player name for the session (start/conduct/up)
+--agent <claude|copilot>    Agent type to spawn (default: claude; start/conduct)
 --skip-preflight            Skip preflight checks (start/conduct)
 --background, -d            Run Temporal in background (server only)
 --dir <path>                Target directory for init (default: cwd)
@@ -186,6 +187,7 @@ ok You're all set!
 
   What next?
   claude-tempo start myband    Add a player session
+  claude-tempo start myband --agent copilot -n copilot-1   Add a Copilot player
   claude-tempo status myband   See who's active
   Or ask the conductor to recruit players for you
 ```
@@ -331,13 +333,13 @@ The `recruit` tool and CLI automatically detect and open sessions in your termin
 | Terminal.app | `.command` file | — | — |
 | gnome-terminal | — | `--` flag | — |
 | konsole / xterm | — | `-e` flag | — |
-| cmd.exe / PowerShell | — | — | `shell:true` |
+| cmd.exe / PowerShell | — | — | `start` command |
 
 All macOS terminals use approaches that preserve the user's full shell environment (fish, zsh, bash) including node version managers (fnm, nvm).
 
 ### Session naming
 
-Sessions start with a random 8-character hex ID. Use `set_name` to give a session a human-readable name:
+Sessions start with a random 8-character hex ID. You can set a name at launch with `-n` or use `set_name` inside a session:
 
 - Names are stored as Temporal search attributes (`ClaudeTempoPlayerId`) and updated in-place — no workflow restart needed
 - Other players use the name to send messages via `cue` and discover sessions via `ensemble`
@@ -354,6 +356,7 @@ Sessions start with a random 8-character hex ID. Use `set_name` to give a sessio
 | `CLAUDE_TEMPO_TASK_QUEUE` | `claude-tempo` | Task queue name |
 | `CLAUDE_TEMPO_ENSEMBLE` | `default` | Ensemble name (isolates groups of players) |
 | `CLAUDE_TEMPO_CONDUCTOR` | `false` | Set to `true` to enable conductor mode |
+| `CLAUDE_TEMPO_PLAYER_NAME` | *(random hex)* | Set a player name on startup (used by `-n` flag) |
 
 ## Development
 
@@ -392,9 +395,99 @@ When a Claude Code session crashes or is closed without graceful shutdown, its T
 
 This means you don't need to manually clean up crashed sessions — just `cue` the dead player and the system handles the rest.
 
-## Known limitations
+## Copilot CLI integration (experimental)
 
-- **`recruit` requires manual acknowledgment**: Recruited sessions use `--dangerously-load-development-channels` to enable channel-based message delivery. Claude Code shows an interactive confirmation prompt that must be manually acknowledged (press Enter) in the spawned terminal window. This will be resolved once claude-tempo is published as an approved channel plugin.
+GitHub Copilot CLI sessions can join an ensemble via the **Copilot bridge**. The bridge uses the [Copilot SDK](https://github.com/github/copilot-sdk) to spawn a Copilot session with claude-tempo as an MCP server, and injects incoming messages as prompts.
+
+### Setup
+
+The Copilot SDK is an optional dependency — install it only if you want Copilot support:
+
+```bash
+npm install @github/copilot-sdk
+```
+
+You also need:
+- [GitHub Copilot CLI](https://docs.github.com/en/copilot/github-copilot-in-the-cli) installed and authenticated
+- An active GitHub Copilot subscription
+
+### Starting a Copilot player
+
+```bash
+# Via CLI (recommended):
+claude-tempo start --agent copilot -n copilot-dev
+
+# Or directly with env vars (Linux/macOS):
+CLAUDE_TEMPO_ENSEMBLE=default COPILOT_BRIDGE_NAME=copilot-dev npx ts-node src/copilot-bridge.ts
+
+# Or directly with env vars (Windows PowerShell):
+$env:TEMPORAL_ADDRESS="localhost:7233"; $env:CLAUDE_TEMPO_ENSEMBLE="default"; $env:COPILOT_BRIDGE_NAME="copilot-dev"; npx ts-node src/copilot-bridge.ts
+
+# Or from any session in the ensemble, recruit one:
+# "Recruit a copilot session named 'copilot-dev' with agent copilot"
+```
+
+The CLI `--agent` flag and the `recruit` tool's `agent` parameter both accept `"claude"` (default) or `"copilot"`.
+
+### Shell shortcuts
+
+Add these functions to your shell profile to simplify launching Copilot bridge sessions:
+
+**Linux/macOS** — add to `~/.bashrc` or `~/.zshrc`:
+
+```bash
+copilot-tempo() {
+  CLAUDE_TEMPO_ENSEMBLE="${1:-default}" COPILOT_BRIDGE_NAME="${2}" \
+    npx ts-node /path/to/claude-tempo/src/copilot-bridge.ts
+}
+```
+
+**Windows** — add to your PowerShell `$PROFILE`:
+
+```powershell
+function copilot-tempo($ensemble = "default", $name = "") {
+  $env:TEMPORAL_ADDRESS = "localhost:7233"
+  $env:CLAUDE_TEMPO_ENSEMBLE = $ensemble
+  $env:COPILOT_BRIDGE_NAME = $name
+  npx ts-node C:\path\to\claude-tempo\src\copilot-bridge.ts
+  $env:CLAUDE_TEMPO_ENSEMBLE = ""
+  $env:COPILOT_BRIDGE_NAME = ""
+}
+```
+
+Usage:
+
+```bash
+copilot-tempo                        # join "default" ensemble, auto-generated name
+copilot-tempo my-project copilot-1   # join "my-project" ensemble as "copilot-1"
+```
+
+### How it works
+
+1. The bridge spawns a Copilot CLI session via the SDK with claude-tempo configured as an MCP server
+2. The MCP server registers the session as a Temporal workflow (same as Claude Code players)
+3. An initial prompt is sent to trigger MCP server initialization (the SDK lazily starts MCP servers)
+4. The bridge polls the workflow for pending messages every 2 seconds
+5. When messages arrive, they're injected as prompts via `session.sendAndWait()`
+6. The Copilot session can use all claude-tempo tools (`ensemble`, `cue`, `report`, etc.)
+
+### Environment variables
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `COPILOT_BRIDGE_NAME` | *(none)* | Player name (calls `set_name` automatically) |
+| `COPILOT_BRIDGE_MODEL` | *(Copilot default)* | Model override for the Copilot session |
+| `GITHUB_TOKEN` | *(logged-in user)* | GitHub auth token |
+
+### Limitations
+
+- **`recruit` requires manual acknowledgment (Claude backend)**: Recruited Claude Code sessions use `--dangerously-load-development-channels` to enable channel-based message delivery. Claude Code shows an interactive confirmation prompt that must be manually acknowledged (press Enter) in the spawned terminal window. This will be resolved once claude-tempo is published as an approved channel plugin. The Copilot backend does not have this limitation.
+- **No interactive access** — Copilot bridge sessions run in the background. Unlike Claude Code sessions where you can chat directly, bridge sessions only respond to cues from other players. To send messages to a bridge session, use `cue` from another player or signal the workflow directly via the Temporal CLI.
+- **Conductor polling latency** — Copilot conductors poll for messages every 2 seconds, unlike Claude Code conductors which receive instant channel notifications. This adds slight latency to orchestration.
+- **No push-based message delivery** — the bridge polls for messages (2s interval), unlike Claude Code sessions which receive instant channel notifications.
+- **Copilot sessions must be spawned via the bridge** to participate (not standalone Copilot CLI).
+- **The `@github/copilot-sdk` adds ~243MB** to node_modules when installed.
+- **Node 20+ required for Copilot features** — the `@github/copilot-sdk` requires Node.js 20 or later. The rest of claude-tempo works on Node 18+.
 
 ## License
 

package/dist/cli/commands.d.ts

@@ -4,6 +4,7 @@ interface StartOpts {
     temporalAddress: string;
     name?: string;
     skipPreflight?: boolean;
+    agent: 'claude' | 'copilot';
 }
 export declare function start(opts: StartOpts): Promise<void>;
 interface StatusOpts {

package/dist/cli/commands.js

@@ -85,25 +85,61 @@ async function start(opts) {
             // No existing conductor — proceed normally
         }
     }
-    out.log(`Starting ${out.bold(role)} in ensemble ${out.cyan(opts.ensemble)}`);
-    const claudeArgs = [
-        '--dangerously-skip-permissions',
-        '--dangerously-load-development-channels', 'server:claude-tempo',
-    ];
-    if (opts.name) {
-        claudeArgs.push('-n', opts.name);
-    }
-    const envVars = {
-        CLAUDE_TEMPO_ENSEMBLE: opts.ensemble,
-    };
-    if (opts.conductor) {
-        envVars.CLAUDE_TEMPO_CONDUCTOR = 'true';
+    out.log(`Starting ${out.bold(role)} in ensemble ${out.cyan(opts.ensemble)}${opts.agent === 'copilot' ? out.dim(' (copilot)') : ''}`);
+    if (opts.agent === 'copilot') {
+        // Spawn copilot-bridge as a detached headless subprocess
+        const isDev = __filename.endsWith('.ts');
+        const cmd = isDev ? 'npx' : 'node';
+        const cmdArgs = isDev
+            ? ['ts-node', (0, path_1.resolve)(__dirname, '..', '..', 'src', 'copilot-bridge.ts')]
+            : [(0, path_1.resolve)(__dirname, '..', 'copilot-bridge.js')];
+        // Log bridge output for debugging
+        const fs = require('fs');
+        const logName = opts.name || `copilot-${Date.now()}`;
+        const logPath = (0, path_1.join)(workDir, 'logs', `${logName}.log`);
+        fs.mkdirSync((0, path_1.join)(workDir, 'logs'), { recursive: true });
+        const logFd = fs.openSync(logPath, 'a');
+        let child;
+        try {
+            child = (0, child_process_1.spawn)(cmd, cmdArgs, {
+                cwd: workDir,
+                detached: true,
+                stdio: ['ignore', logFd, logFd],
+                env: {
+                    ...process.env,
+                    CLAUDE_TEMPO_ENSEMBLE: opts.ensemble,
+                    COPILOT_BRIDGE_NAME: opts.name || '',
+                    TEMPORAL_ADDRESS: opts.temporalAddress,
+                    ...(opts.conductor ? { CLAUDE_TEMPO_CONDUCTOR: 'true' } : {}),
+                },
+            });
+            child.unref();
+        }
+        finally {
+            fs.closeSync(logFd);
+        }
+        out.success(`Launched copilot bridge${opts.name ? ` "${opts.name}"` : ''} (pid ${child.pid ?? 'unknown'})`);
     }
-    if (opts.name) {
-        envVars.CLAUDE_TEMPO_PLAYER_NAME = opts.name;
+    else {
+        const claudeArgs = [
+            '--dangerously-skip-permissions',
+            '--dangerously-load-development-channels', 'server:claude-tempo',
+        ];
+        if (opts.name) {
+            claudeArgs.push('-n', opts.name);
+        }
+        const envVars = {
+            CLAUDE_TEMPO_ENSEMBLE: opts.ensemble,
+        };
+        if (opts.conductor) {
+            envVars.CLAUDE_TEMPO_CONDUCTOR = 'true';
+        }
+        if (opts.name) {
+            envVars.CLAUDE_TEMPO_PLAYER_NAME = opts.name;
+        }
+        const { pid } = (0, spawn_1.spawnInTerminal)(claudeArgs, workDir, envVars);
+        out.success(`Launched ${role} session${opts.name ? ` "${opts.name}"` : ''} (pid ${pid ?? 'unknown'})`);
     }
-    const { pid } = (0, spawn_1.spawnInTerminal)(claudeArgs, workDir, envVars);
-    out.success(`Launched ${role} session${opts.name ? ` "${opts.name}"` : ''} (pid ${pid ?? 'unknown'})`);
     out.log(`  Ensemble: ${opts.ensemble}`);
     out.log(`  Directory: ${workDir}`);
     out.log(`\nCheck status: ${out.dim('claude-tempo status ' + opts.ensemble)}`);
@@ -541,6 +577,7 @@ ${out.bold('Commands:')}
 ${out.bold('Options:')}
   --temporal-address <addr>   Temporal server address (default: localhost:7233)
   -n, --name <name>           Set the session window name (start/conduct/up only)
+  --agent <claude|copilot>    Agent type to spawn (default: claude; start/conduct)
   --skip-preflight            Skip preflight checks (start/conduct only)
   --background                Run Temporal in background (server only)
   --keep-mcp                  Don't remove .mcp.json entry (down only)
@@ -554,6 +591,7 @@ ${out.bold('Typical workflow:')}
   ${out.dim('claude-tempo server')}               Start Temporal (once, keep running)
   ${out.dim('claude-tempo conduct myband')}       Start a conductor
   ${out.dim('claude-tempo start myband')}         Add player sessions
+  ${out.dim('claude-tempo start myband --agent copilot -n copilot-1')}   Add a Copilot player
   ${out.dim('claude-tempo status myband')}        Check who's active
 
 ${out.bold('Environment:')}

package/dist/cli.js

@@ -68,6 +68,14 @@ function parseArgs(argv) {
         else if (arg === '--keep-mcp') {
             result.keepMcp = true;
         }
+        else if (arg === '--agent' && i + 1 < argv.length) {
+            const val = argv[++i];
+            if (val !== 'claude' && val !== 'copilot') {
+                out.error(`Invalid agent type: "${val}". Must be "claude" or "copilot".`);
+                process.exit(1);
+            }
+            result.agent = val;
+        }
         else if (arg === '--help' || arg === '-h') {
             result.command = 'help';
         }
@@ -100,6 +108,7 @@ async function main() {
                 temporalAddress: args.temporalAddress,
                 name: args.name,
                 skipPreflight: args.skipPreflight,
+                agent: args.agent ?? 'claude',
             });
             break;
         case 'start':
@@ -109,6 +118,7 @@ async function main() {
                 temporalAddress: args.temporalAddress,
                 name: args.name,
                 skipPreflight: args.skipPreflight,
+                agent: args.agent ?? 'claude',
             });
             break;
         case 'status':

package/dist/copilot-bridge.d.ts

@@ -0,0 +1,21 @@
+/**
+ * Copilot Bridge — allows GitHub Copilot CLI sessions to participate
+ * as players in a claude-tempo ensemble.
+ *
+ * The bridge:
+ * 1. Spawns a Copilot CLI session via the Copilot SDK
+ * 2. Configures it with claude-tempo as an MCP server (so it gets all tools)
+ * 3. Polls the Temporal workflow for pending messages
+ * 4. Injects messages as prompts via the SDK
+ *
+ * Usage:
+ *   npx ts-node src/copilot-bridge.ts
+ *
+ * Environment variables:
+ *   CLAUDE_TEMPO_ENSEMBLE     — ensemble name (default: "default")
+ *   CLAUDE_TEMPO_PLAYER_NAME  — player ID for workflow registration (set by spawner for deterministic workflow IDs)
+ *   COPILOT_BRIDGE_NAME       — player name for set_name (optional)
+ *   COPILOT_BRIDGE_MODEL      — model to use (optional)
+ *   GITHUB_TOKEN              — GitHub auth token (optional, uses logged-in user by default)
+ */
+export {};