claude-tempo 0.4.0 → 0.4.1

package/README.md

@@ -32,7 +32,7 @@ This will:
 1. Check that Temporal CLI is installed
 2. Start the Temporal dev server (data persists in `~/.claude-tempo/`)
 3. Register required search attributes
-4. Create `.mcp.json` in your project
+4. Register the claude-tempo MCP server (globally by default)
 5. Launch a conductor session in a new terminal window
 
 Then add players:
@@ -52,7 +52,7 @@ For more control, run each step individually:
 # Start Temporal dev server (keep running)
 claude-tempo server
 
-# In your project directory, create .mcp.json
+# Register claude-tempo MCP server (globally by default)
 cd your-project
 claude-tempo init
 
@@ -352,6 +352,7 @@ export TEMPORAL_API_KEY=tcl_...
 | `CLAUDE_TEMPO_ENSEMBLE` | `default` | Ensemble name |
 | `CLAUDE_TEMPO_CONDUCTOR` | `false` | Enable conductor mode |
 | `CLAUDE_TEMPO_PLAYER_NAME` | *(random hex)* | Player name on startup |
+| `CLAUDE_TEMPO_DEFAULT_AGENT` | `claude` | Default agent type (`claude` or `copilot`) |
 
 ## Stale session cleanup
 
@@ -359,7 +360,7 @@ When a session crashes or closes without graceful shutdown, Temporal detects it
 
 - If a message to a dead session remains undelivered for **3 minutes**, the workflow self-completes
 - Before exiting, it notifies the conductor with the undelivered message so work can be reassigned
-- Idle sessions with no pending messages remain running until the 24-hour timeout
+- Idle sessions with no pending messages are probed after 1 hour of inactivity via a heartbeat ping; if the ping goes undelivered, the session self-completes
 
 No manual cleanup needed — `cue` a dead player and the system handles the rest.
 
@@ -367,52 +368,60 @@ No manual cleanup needed — `cue` a dead player and the system handles the rest
 
 > **Warning:** Copilot bridge support is experimental and subject to breaking changes.
 
-GitHub Copilot CLI sessions can join an ensemble via the Copilot bridge. Bridge sessions are headless — they require a Claude conductor or custom Temporal client to receive work via `cue`.
+GitHub Copilot CLI sessions can join an ensemble via the Copilot bridge. Bridge sessions are headless — they require a conductor or another player to receive work via `cue`.
 
 <details>
 <summary>Setup and usage</summary>
 
 ### Prerequisites
 
+- [GitHub Copilot CLI](https://docs.github.com/en/copilot/github-copilot-in-the-cli) installed and authenticated
+- An active GitHub Copilot subscription
+- Node.js 20+
+- Install the Copilot SDK: `npm install @github/copilot-sdk`
+
+### Starting Copilot sessions
+
+Use `--agent copilot` with any session-launching command:
+
 ```bash
-npm install @github/copilot-sdk    # optional dependency (~243MB)
+claude-tempo start myband --agent copilot -n copilot-1      # start a player
+claude-tempo conduct myband --agent copilot                  # start a conductor
+claude-tempo up myband --agent copilot                       # full setup
 ```
 
-Also requires [GitHub Copilot CLI](https://docs.github.com/en/copilot/github-copilot-in-the-cli) installed, authenticated, with an active subscription. Node 20+ required for Copilot features.
+Or recruit from within any active session:
 
-### Starting a Copilot player
+> "Recruit a copilot session named 'copilot-dev' in /repos/my-project with agent copilot"
 
-The easiest way is via `recruit` from any active session:
+### Setting a default agent
 
-> "Recruit a copilot session named 'copilot-dev' in /repos/my-project with agent copilot"
+To avoid passing `--agent copilot` every time:
+
+```bash
+claude-tempo config set default-agent copilot
+```
 
-Or start the bridge directly:
+Or via environment variable:
 
 ```bash
-CLAUDE_TEMPO_ENSEMBLE=default COPILOT_BRIDGE_NAME=copilot-dev npx ts-node src/copilot-bridge.ts
+export CLAUDE_TEMPO_DEFAULT_AGENT=copilot
 ```
 
-### How it works
+Resolution order: `--agent` flag → `CLAUDE_TEMPO_DEFAULT_AGENT` env → config file → `claude`.
 
-1. Bridge spawns a Copilot CLI session via the SDK with claude-tempo as MCP server
-2. MCP server registers the session as a Temporal workflow
-3. Bridge polls for pending messages every 2 seconds
-4. Messages are injected as prompts via `session.sendAndWait()`
-5. The Copilot session can use all claude-tempo tools
+### Model override
 
-### Copilot environment variables
+Set `COPILOT_BRIDGE_MODEL` to use a specific model for Copilot sessions:
 
-| Variable | Default | Description |
-|----------|---------|-------------|
-| `COPILOT_BRIDGE_NAME` | *(none)* | Player name |
-| `COPILOT_BRIDGE_MODEL` | *(Copilot default)* | Model override |
-| `GITHUB_TOKEN` | *(logged-in user)* | GitHub auth token |
+```bash
+COPILOT_BRIDGE_MODEL=gpt-4o claude-tempo start myband --agent copilot
+```
 
 ### Limitations
 
-- No interactive access — bridge sessions only respond to cues
-- 2-second polling latency (vs instant for Claude Code sessions)
-- Must be spawned via the bridge to participate
+- Headless only — bridge sessions respond to cues, no interactive terminal
+- ~2-second polling latency (vs instant for Claude Code sessions)
 - `@github/copilot-sdk` adds ~243MB to node_modules
 - Node 20+ required (rest of claude-tempo works on Node 18+)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-tempo",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "MCP server for multi-session Claude Code coordination via Temporal",
   "repository": {
     "type": "git",