SOP-003: Session Management
DOCUMENT CONTROL
| Field | Value |
|---|---|
| SOP ID | SOP-003 |
| Version | 1.0 |
| Status | Active |
| Last Updated | December 2025 |
Purpose
This SOP covers managing multiple Claude Code sessions simultaneously across different machines and projects using Happy Coder.
Multi-Session Architecture
┌─────────────────────────────────────────────────────────────────┐
│ HAPPY CODER MOBILE APP │
├─────────────────────────────────────────────────────────────────┤
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Session 1 │ │ Session 2 │ │ Session 3 │ │
│ │ Frontend │ │ Backend │ │ DevOps │ │
│ │ [Laptop] │ │ [Desktop] │ │ [VPS] │ │
│ └──────┬──────┘ └──────┬──────┘ └──────┬──────┘ │
└─────────┼────────────────┼────────────────┼─────────────────────┘
│ │ │
▼ ▼ ▼
┌───────────┐ ┌───────────┐ ┌───────────┐
│ Laptop │ │ Desktop │ │ VPS │
│ Claude │ │ Claude │ │ Claude │
│ Code │ │ Code │ │ Code │
└───────────┘ └───────────┘ └───────────┘Procedure Flowchart
┌────────────────────┐
│ START │
└─────────┬──────────┘
│
▼
┌────────────────────┐
│ Start happy CLI on │
│ each machine │
└─────────┬──────────┘
│
▼
┌────────────────────┐
│ Open mobile app │
│ View session list │
└─────────┬──────────┘
│
▼
┌────────────────────┐
│ Select session │
│ to interact with │
└─────────┬──────────┘
│
▼
┌────────────────────┐
│ Send commands or │
│ switch sessions │
└─────────┬──────────┘
│
▼
┌────────────────────┐
│ COMPLETE │
└────────────────────┘Step-by-Step Procedure
Starting Multiple Sessions
Step 1: On your first machine (e.g., laptop):
bash
cd ~/projects/frontend
happyStep 2: On your second machine (e.g., desktop):
bash
cd ~/projects/backend
happyStep 3: Sessions automatically appear in your mobile app.
Switching Between Sessions
- Open Happy Coder mobile app
- Tap the session list icon
- Select the desired session
- Continue conversation in that context
Session Identification
Each session shows:
| Info | Description |
|---|---|
| Machine Name | Hostname of the computer |
| Project Path | Working directory |
| Status | Active/Idle/Needs Input |
| Last Activity | Timestamp of last action |
Running Parallel Tasks
Parallel Exploration Pattern
- Start 3-4 different approaches to a problem
- Let them run on different machines/sessions
- Check results on your phone
- Pick the best approach, discard the rest
Example Setup:
bash
# Machine 1: Try approach A
cd ~/project && git checkout -b experiment-a
happy
# Machine 2: Try approach B
cd ~/project && git checkout -b experiment-b
happy
# Machine 3: Try approach C
cd ~/project && git checkout -b experiment-c
happySession States
| State | Icon | Description |
|---|---|---|
| Active | 🟢 | Claude Code is processing |
| Idle | 🔵 | Waiting for input |
| Needs Input | 🟡 | Permission prompt pending |
| Disconnected | 🔴 | CLI not running |
Best Practices
1. Use Git Worktrees
Set up worktrees for parallel experimentation:
bash
# Create worktrees ahead of time
git worktree add ../project-experiment-1 -b experiment-1
git worktree add ../project-experiment-2 -b experiment-2
git worktree add ../project-experiment-3 -b experiment-32. Connect All Compute Resources
| Device Type | Example Uses |
|---|---|
| Development laptop | Primary coding |
| Desktop workstation | Heavy builds, testing |
| Cloud VPS | Deployment, CI tasks |
| Raspberry Pi | Background automation |
| Mac Mini | iOS development |
3. Session Naming
Name sessions clearly by project or task:
bash
# Set custom session name
HAPPY_SESSION_NAME="frontend-refactor" happyVerification Checklist
- [ ] Multiple sessions visible in mobile app
- [ ] Each session shows correct machine/path
- [ ] Can switch between sessions smoothly
- [ ] Push notifications work for all sessions
- [ ] Session state updates in real-time