sisyphi 0.1.3 → 0.1.4

package/README.md

@@ -1,13 +1,31 @@
 ```
- _____ _____ _______   _______ _   _ _   _ _____
-/  ___|_   _/  ___\ \ / / ___ \ | | | | | /  ___|
-\ `--.  | | \ `--. \ V /| |_/ / |_| | | | \ `--.
- `--. \ | |  `--. \ \ / |  __/|  _  | | | |`--. \
-/\__/ /_| |_/\__/ / | | | |   | | | | |_| /\__/ /
-\____/ \___/\____/  \_/ \_|   \_| |_/\___/\____/
+╔═══════════════════════════════════════════════════════╗
+║ @@@@@@@@@@@@@@@@@@@@@@@@@@@%%%#*++**#%%@@@@@@@@@@@@@@ ║
+║ @@@@@@@@@@@@@@@@@@@@@@@@%*====-----::::-:=%@@@@@@@@@@ ║
+║ @@@@@@@@@@@@@@@@@@@@@%#=:.:-=------:...    -%@@@@@@@@ ║
+║ @@@@@@@@@@@@@@@@@@%%#= .....:-:..........    *%@@@@@@ ║
+║ @@@@@@@@@@@@@@%+==-+%*:  .:---::::....:....   #@@@@@@ ║
+║ @@@@@@@@@@@@%#:. ..:.    ..:-...:.....    .  :%@@@@@@ ║
+║ @@@@@@@@@@@@#:.:..  :*= ............       . :%@@@@@@ ║
+║ @@@@@@@@@@@@#--:..   -%+............... ..   *%#=-:.: ║
+║ @@@@@@@@@@%#----.:#%+.::::...       .....    .... .:# ║
+║ @@@@@@@@%+-:::.. :%@@@@@@@@%*=:                 ..*%@ ║
+║ @@@@@@%*-=:..::.:-..+@@@@@@%%#=:.   ..   . ...   *@@@ ║
+║ @@@@#==::%@@@@@@%=:::=%*-:.     ....  .   ...  :%@@@@ ║
+║ @@#::=#@@@@%#-.:-...    .::...               :#%@@@@@ ║
+║ %=:%%%#####+:.:     .    .....    .  .      *%@@@@@@@ ║
+║ :::.:.:::..::.        .                 ..  :#@@@@@@@ ║
+║ %#*++===--============++===-::::::::---=====#%@@@@@@@ ║
+║    _____ _____ _______   _______ _   _ _   _ _____    ║
+║   /  ___|_   _/  ___\ \ / / ___ \ | | | | | /  ___|   ║
+║   \ `--.  | | \ `--. \ V /| |_/ / |_| | | | \ `--.    ║
+║    `--. \ | |  `--. \ \ / |  __/|  _  | | | |`--. \   ║
+║   /\__/ /_| |_/\__/ / | | | |   | | | | |_| /\__/ /   ║
+║   \____/ \___/\____/  \_/ \_|   \_| |_/\___/\____/    ║
+╚═══════════════════════════════════════════════════════╝
 ```
 
-# sisyphi
+# sisyphus
 
 A tmux-integrated orchestration daemon for [Claude Code](https://docs.anthropic.com/en/docs/claude-code) multi-agent workflows.
 
@@ -38,7 +56,7 @@ You ──► sisyphus start "build auth system"
 ```
 
 1. **You** run `sisyphus start` with a high-level task
-2. **Orchestrator** decomposes it, adds tasks, spawns agents, yields
+2. **Orchestrator** decomposes it, spawns agents, yields
 3. **Agents** work in parallel tmux panes, send progress reports, submit when done
 4. **Daemon** detects completion, respawns orchestrator with updated state
 5. **Orchestrator** reviews reports, spawns more agents or completes the session
@@ -63,7 +81,7 @@ This gives you two commands:
 
 ### Claude Code Plugin (optional)
 
-The companion plugin on the [crouton-kit](https://github.com/CaptainCrouton89/crouton-kit) marketplace adds 11 specialized agent types and an orchestration skill with task breakdown patterns for common workflows (bug fixes, feature builds, refactors, reviews, etc.).
+The companion plugin on the [crouton-kit](https://github.com/CaptainCrouton89/crouton-kit) marketplace adds specialized agent types and an orchestration skill with task breakdown patterns for common workflows (bug fixes, feature builds, refactors, reviews, etc.).
 
 ```bash
 claude plugins install CaptainCrouton89/crouton-kit sisyphus
@@ -79,7 +97,9 @@ This makes `sisyphus:debug`, `sisyphus:implement`, `sisyphus:plan`, and other ag
 sisyphusd
 ```
 
-Or run it in the background. On macOS you can use launchd — create `~/Library/LaunchAgents/com.sisyphus.daemon.plist`:
+The daemon also supports `sisyphusd stop` and `sisyphusd restart` subcommands.
+
+To run it persistently on macOS, use launchd — create `~/Library/LaunchAgents/com.sisyphus.daemon.plist`:
 
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>
@@ -110,6 +130,13 @@ Then load it:
 launchctl load ~/Library/LaunchAgents/com.sisyphus.daemon.plist
 ```
 
+To unload and clean up:
+
+```bash
+sisyphus uninstall          # Unload from launchd
+sisyphus uninstall --purge  # Also remove ~/.sisyphus data
+```
+
 ### 2. Start a session (inside tmux)
 
 ```bash
@@ -121,23 +148,19 @@ The orchestrator spawns in a yellow tmux pane and begins planning.
 ### 3. Watch it work
 
 ```bash
-sisyphus status     # Check session state, tasks, agents
-sisyphus tasks list # View task breakdown
+sisyphus status              # Check session state and agents
+sisyphus list                # List sessions in current project
+sisyphus list --all          # List sessions across all projects
 ```
 
-Agent panes appear as the orchestrator spawns them, color-coded by agent:
-
-| Role | Color |
-|------|-------|
-| Orchestrator | Yellow |
-| Agents | Blue, Green, Magenta, Cyan, Red, White (rotating) |
+Agent panes appear as the orchestrator spawns them, color-coded by role. Agent types from the crouton-kit plugin define their own colors via frontmatter; otherwise agents rotate through blue, green, magenta, cyan, red, and white.
 
 ### 4. Resume or complete
 
 ```bash
 sisyphus resume <session-id>                    # Resume a paused session
 sisyphus resume <session-id> "focus on tests"   # Resume with new instructions
-sisyphus list                                   # List all sessions
+sisyphus kill <session-id>                      # Kill a session and all agents
 ```
 
 ## CLI Reference
@@ -145,25 +168,56 @@ sisyphus list                                   # List all sessions
 ```bash
 # Session lifecycle
 sisyphus start "task description"           # Create session, launch orchestrator
-sisyphus status                             # Current session state
-sisyphus list                               # List all sessions
+sisyphus status [session-id]                # Session state (defaults to active session)
+sisyphus list [-a, --all]                   # List sessions (--all for cross-project)
 sisyphus resume <id> [message]              # Resume paused session
-sisyphus kill <id>                          # Kill a session
+sisyphus kill <id>                          # Kill session and all agents
+sisyphus uninstall [--purge] [-y]           # Unload daemon from launchd
+
+# Daemon management
+sisyphusd                                   # Start the daemon
+sisyphusd stop                              # Stop the daemon
+sisyphusd restart                           # Restart the daemon
 
-# These are used by the orchestrator/agents (not typically run manually):
+# Used by the orchestrator/agents (not typically run manually):
 sisyphus spawn --agent-type <t> --name <n> --instruction "..."
-sisyphus yield                              # Orchestrator yields control
+sisyphus spawn --agent-type <t> --name <n> --instruction "..." --worktree
+sisyphus yield [--prompt "next cycle context"]
 sisyphus complete --report "summary"        # Mark session done
 sisyphus submit --report "findings"         # Agent submits final report
 sisyphus report --message "progress"        # Agent sends progress update
+```
+
+Both `yield`, `submit`, and `report` support stdin piping for long content:
 
-# Task management
-sisyphus tasks list
-sisyphus tasks add "description"
-sisyphus tasks add "idea" --status draft
-echo "long description" | sisyphus tasks add    # stdin piping
-sisyphus tasks update <taskId> --status done
-sisyphus tasks update <taskId> --description "refined"
+```bash
+echo "detailed report" | sisyphus submit
+echo "progress update" | sisyphus report
+```
+
+## Git Worktree Isolation
+
+Agents can work in isolated git worktrees to avoid conflicts when multiple agents edit files in parallel:
+
+```bash
+sisyphus spawn --agent-type sisyphus:implement --name "auth" \
+  --instruction "implement auth module" --worktree
+```
+
+With `--worktree`, the daemon:
+1. Creates a new branch (`sisyphus/{session}/{agent-id}`) and worktree
+2. Symlinks `.sisyphus` and `.claude` directories into the worktree
+3. Runs bootstrap commands from `.sisyphus/worktree.json` (copy files, install deps, etc.)
+4. Automatically merges the agent's branch back when the agent submits
+
+Configure worktree bootstrap in `.sisyphus/worktree.json`:
+
+```json
+{
+  "symlink": [".env", "node_modules"],
+  "copy": ["package.json"],
+  "init": "npm install"
+}
 ```
 
 ## Architecture
@@ -174,7 +228,22 @@ Three layers communicating over a Unix socket (`~/.sisyphus/daemon.sock`):
 - **Daemon** (`sisyphusd`) — Manages sessions, spawns/monitors tmux panes, tracks state
 - **Shared** — Types, protocol definitions, config resolution
 
-State is persisted as JSON at `.sisyphus/sessions/{id}/state.json` (relative to your project directory), written atomically via temp file + rename.
+### State & Persistence
+
+State is persisted as JSON at `.sisyphus/sessions/{id}/state.json` (project-relative), written atomically via temp file + rename.
+
+Each session directory contains:
+```
+.sisyphus/sessions/{id}/
+├── state.json        # Session state (atomic writes)
+├── plan.md           # Orchestrator memory — outstanding work
+├── logs.md           # Orchestrator memory — session log
+├── prompts/          # Rendered system + user prompt files
+├── reports/          # Agent report files
+└── context/          # Persistent artifacts (specs, plans, explorations)
+```
+
+The orchestrator maintains `plan.md` and `logs.md` across cycles as persistent memory — these survive orchestrator respawns and give each new cycle continuity with previous work.
 
 ## Configuration
 
@@ -183,7 +252,8 @@ Config is layered: project (`.sisyphus/config.json`) overrides global (`~/.sisyp
 ```json
 {
   "model": "sonnet",
-  "pollIntervalMs": 3000
+  "pollIntervalMs": 1000,
+  "tmuxSession": "my-session"
 }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sisyphi",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "tmux-integrated orchestration daemon for Claude Code multi-agent workflows",
   "license": "MIT",
   "repository": {