Enable multiple task instances with unique tmux sessions

[bborn]

Summary

Fixes the issue where every task -l command used the same tmux session, preventing multiple task instances from running simultaneously.

Each task instance now gets its own isolated tmux sessions based on process ID, allowing users to run multiple task app instances in parallel without conflicts.

Changes

Session ID Management

• Added getSessionID() function that generates unique session IDs based on PID
• Session ID can be inherited via TASK_SESSION_ID environment variable
• Session ID propagates through daemon and all child processes

Dynamic Session Naming

• UI Session: Changed from task-ui to task-ui-{PID}
• Daemon Session: Changed from task-daemon to task-daemon-{PID}
• Added helper functions for consistent session naming

Updated Components

• cmd/task/main.go: Updated all UI session references, daemon spawning, and copilot system prompt
• internal/executor/executor.go: Updated all daemon session references and Claude task execution

How It Works

1. When task -l starts without TASK_SESSION_ID, it generates one based on its PID
2. The session ID is set as an environment variable and passed to all child processes
3. All tmux session names include the session ID suffix
4. Each instance gets:
   • Its own UI session: task-ui-12345
   • Its own daemon session: task-daemon-12345
   • Its own set of task windows within the daemon session

Instance Isolation

Each instance now maintains complete isolation:

• ✅ Separate UI session (task-ui-{PID})
• ✅ Separate daemon session (task-daemon-{PID})
• ✅ Independent Claude task windows
• ✅ No session name conflicts between instances

Testing

• ✅ Build succeeds
• ✅ Session naming logic verified
• ✅ PID-based session IDs work correctly
• ✅ Environment variable propagation works

Files Changed

• cmd/task/main.go (98 insertions, 46 deletions)
• internal/executor/executor.go (51 insertions, 46 deletions)

🤖 Generated with Claude Code