Andrew Nutter-Upham andynu

tmx-claude & tmx-worktree

Spawn Claude Code sessions in tmux windows — either in your current repo or in isolated git worktrees. Lets you run multiple Claude agents in parallel without blocking your terminal.

Notes

WORKTREE_BASE defaults to ~/work/src/ in tmx-worktree and worktree-clean. Edit the variable at the top of each script to match your layout.
tmx-claude --help mentions bd-lite, a lightweight issue tracker I use. You can ignore that or rip it out.

What's included

Two-Context Execution Pattern with Beads

A workflow pattern for AI-assisted development that separates planning from execution, using context isolation to keep each layer focused.

The Problem

Large tasks overwhelm a single Claude session:

Context fills with implementation details
Hard to track overall progress
Easy to lose sight of the plan while deep in code

Multi-Agent Claude Code Workflow

A lightweight pattern for spawning secondary Claude Code sessions using tmux, enabling parallel work across projects without context collision.

Why Spawn Secondary Sessions?

When working from a "mission control" directory (like ~/work/src/ with 100+ projects), you often need to:

Dispatch deep work to a specific project while continuing meta-level coordination
Run parallel investigations that would pollute a single session's context

name	description
C4 Diagrams	Creating C4 architecture diagrams using D2 diagram language. Use when creating system context diagrams, container diagrams, component diagrams, code diagrams, deployment diagrams, or any software architecture visualization following the C4 model. Also applies when discussing architecture at different zoom levels or explaining system boundaries.

C4 Architecture Diagrams with D2

Create C4 model diagrams using D2's text-to-diagram syntax. Supports both graphical (SVG/PNG) and ASCII output.

description	argument-hint	allowed-tools	context
execute a single bd issue	<issue key>	Bash(bd ), Bash(git ), Bash(tea *), Read(.)	fork

Execute Single BD Issue

Overview

Execute a single bd issue with proper status tracking, commenting, and git workflow integration. This command handles one issue in isolation, keeping context clean.

description	allowed-tools
execute a set of bd issues	Bash(bd:*)

Execute BD Plan Command

Overview

Execute a bd plan by working through issues with proper status tracking, commenting, and git workflow integration. Do not ask which one to start with. Start with any ready task by priority, if there is a tie, choose the first one. Please continue implementing until all ready tasks are complete, or you hit a critical question that demands a human answer.

	# frozen_string_literal: true

	# ╔══════════════════════════════════════════════════════════════════════╗
	# ║ WARNING: ruby-oci8 ONLY ║
	# ║ ║
	# ║ This patch uses cursor.rowid, a ruby-oci8 API. It is NOT ║
	# ║ compatible with JDBC (JRuby). For a cross-platform fix that ║
	# ║ handles composite primary keys only, see: ║
	# ║ https://gist.github.com/andynu/508ed5b16f348d474db377ab1e870778 ║
	# ║ ║

	# frozen_string_literal: true

	# Monkey patch: Fix LOB writes for tables with composite primary keys
	#
	# The stock oracle-enhanced adapter's write_lobs method assumes a single
	# primary key column. With a composite key, klass.primary_key returns an
	# Array, which causes:
	# - attributes[[:col_a, :col_b]] → nil (Hash doesn't find Array keys)
	# - quote_column_name([:col_a, :col_b]) → garbage column name
	# - SELECT FOR UPDATE returns no rows → RecordNotFound / data loss

	---
	- name: ruby build dependencies
	apt:
	pkg:
	- git
	- build-essential
	- libssl-dev
	- zlib1g-dev
	- libreadline-dev
	- libffi-dev

	#!/bin/bash
	input=$(cat)
	MODEL=$(echo "$input" \| jq -r '.model.display_name // "Claude"')
	DIR=$(echo "$input" \| jq -r '.workspace.current_dir // "~"')
	FOLDER="${DIR##*/}"

	# Git branch
	BRANCH=""
	if git -C "$DIR" rev-parse --git-dir > /dev/null 2>&1; then
	BRANCH=$(git -C "$DIR" branch --show-current 2>/dev/null)