Feature: launchers

[nocksock]

Makes it possible to run arbitrary launchers for the selected task. Will offer to add defaults if none are configured.

This could prove quite powerful when paired with custom scripts, eg: a launcher bash script, that creates a worktree, new tmux session with coding agent open and useful prompt to get things going immediately.

Note: not yet properly code-reviewed or cleaned up. Thus this is still a draft. But it's working.

Can be configured like this:

launchers:
  # Simple single-line launcher
  - name: opencode
    exec: opencode -p "Work on task $BEANS_ID"
    description: "Open task in OpenCode"
  
  # Git worktree + tmux launcher
  - name: worktree-tmux
    description: "Create git worktree and open in new tmux pane"
    exec: |
      #!/bin/bash
      set -euo pipefail
      
      WORKTREE_DIR=".worktrees/$BEANS_ID"
      
      # Create worktree if it doesn't exist
      if [ ! -d "$WORKTREE_DIR" ]; then
        git worktree add "$WORKTREE_DIR" -b "task/$BEANS_ID"
      fi
      
      # Open in new tmux pane
      tmux split-window -h -c "$BEANS_ROOT/$WORKTREE_DIR"
      tmux send-keys "opencode -p 'Work on task $BEANS_ID'" Enter

I'm unsure about using env-vars vs. template-vars (eg {{.Title}}).

[sotte]

When I just looked at the PR description I did not fully understand what this is. The README was helpful though.

I actually have a similar, albeit more manual workflow. I yank the bean id from the tui and run a script that launches a tmux window with Claude and a prompt "Work on BEAN_ID. Make a plan, update the bean."

This is basically your launcher.