r/wkbefwky

Typing is the bottleneck on a long brief. Hold the key, talk like you're walking a colleague through it, release. Opus xhigh fills in the typing-quality gap.

The house is quiet, the inbox is closed, and Opus is in a steady cadence. The longest streak (24 days) was built one 10pm session at a time.

Why it's there: The 'just let it cook' triplet. effortLevel:xhigh for plan quality, defaultMode:auto to skip the polite check-ins, skipAutoPermissionPrompt to remove the prompt-on-first-tool dialog. Pair with a tight allow/deny list so the autonomy doesn't bite.

{
  "effortLevel": "xhigh",
  "permissions": { "defaultMode": "auto" },
  "skipAutoPermissionPrompt": true
}

Why it's there: The voice-key acts like a push-to-talk radio. Hold → speak → release inserts the transcription as your prompt. Removes the typing latency from long briefs.

{
  "voice": { "enabled": true, "mode": "hold" }
}

Why it's there: Normal-mode keybindings in the prompt input + fullscreen TUI to take over the terminal. The session name carries the work label so I know which window I'm in.

{
  "editorMode": "normal",
  "tui": "fullscreen"
}

Why it's there: auto-mode is reckless without a deny list. Allow the common safe Bash verbs + scoped Read/Write/Edit; hard-deny destructive git + rm -rf + sudo.

{
  "permissions": {
    "allow": [
      "WebFetch", "WebSearch", "Read",
      "Edit(~/Documents/projects/**)",
      "Write(~/Documents/projects/**)",
      "Bash(git *)", "Bash(gh *)", "Bash(npm *)", "Bash(npx *)",
      "Bash(node *)", "Bash(open *)", "Bash(ls *)", "Bash(cat *)",
      "Bash(mkdir *)", "Bash(cp *)", "Bash(mv *)",
      "Bash(pwd)", "Bash(which *)", "Bash(echo *)",
      "Bash(wc *)", "Bash(head *)", "Bash(tail *)",
      "Bash(sort *)", "Bash(curl *)"
    ],
    "deny": [
      "Bash(git push --force *)",
      "Bash(git push -f *)",
      "Bash(git reset --hard *)",
      "Bash(rm -rf *)",
      "Bash(sudo *)"
    ],
    "defaultMode": "auto"
  }
}

Why it's there: A single short chime when the agent stops talking. Trains you that 'silence then Tink = your turn'. Nothing fancier.

{
  "hooks": {
    "Stop": [{
      "matcher": "",
      "hooks": [{
        "type": "command",
        "command": "[ -z \"${_LIVED_BADGE_HOOK:-}\" ] && afplay /System/Library/Sounds/Tink.aiff &"
      }]
    }]
  }
}

Why it's there: UserPromptSubmit hook writes the user's prompt as the iTerm badge immediately (instant feedback), then fires a background Haiku call that returns a 3–6 word topic phrase and overwrites the badge. statusline.sh reads the per-session file every tick and pushes OSC 1337 SetBadgeFormat to the terminal. Net effect: the watermark on the top-right of each session tracks the work as it evolves. Cost: pennies/month. Recursion guard via _LIVED_BADGE_HOOK so the Haiku subprocess doesn't re-fire the hook.

#!/bin/bash
# Recursion guard: the Haiku call below is itself a `claude -p` which fires hooks.
[ -n "${_LIVED_BADGE_HOOK:-}" ] && exit 0

input=$(cat)
prompt=$(printf '%s' "$input" | jq -r '.prompt // empty')
session_id=$(printf '%s' "$input" | jq -r '.session_id // empty')
[ -z "$session_id" ] && exit 0

state_file="$HOME/.claude/badge-state/$session_id"
mkdir -p "$(dirname "$state_file")"

clean=$(printf '%s' "$prompt" | tr '\n\t' '  ' | sed 's/^[^[:alnum:]]*//; s/[[:space:]]\{2,\}/ /g')
[ "${#clean}" -lt 12 ] && exit 0

# 1) Immediate: write the truncated prompt as the label.
printf '%s' "${clean:0:60}" > "$state_file"

Why it's there: One bar shows everything that matters per tick: session name, worktree purpose (with a ⚠MAIN warning if you're NOT in a worktree), branch, PR state (cached 60s via gh), context % dot, 5h rate dot + reset countdown, sandbox/remote flags. Also pushes OSC 1337 SetBadgeFormat + OSC 1 tab title to the terminal so each tab is identifiable at a glance. Falls back from /dev/tty to the parent's ttys### when the statusline subprocess has no controlling terminal — the part that makes the badge actually show reliably.

# (excerpt — the file is ~200 lines; the trick is the OSC + parent-tty fallback)
if [ "${TERM_PROGRAM:-}" = "iTerm.app" ]; then
  badge_b64=$(printf '%s' "$badge_label" | base64)
  term_dev=""
  if { : > /dev/tty; } 2>/dev/null; then
    term_dev="/dev/tty"
  else
    # statusline subprocess often has no controlling tty — fall back to parent's.
    ppid_tty=$(ps -o tty= -p "${PPID:-0}" | tr -d ' ')
    case "$ppid_tty" in
      ttys*|tty*) [ -w "/dev/$ppid_tty" ] && term_dev="/dev/$ppid_tty" ;;
    esac
  fi
  [ -n "$term_dev" ] && {
    printf '\e]1337;SetBadgeFormat=%s\a' "$badge_b64" > "$term_dev"
    printf '\e]1;%s\a' "$session_label" > "$term_dev"
  }
fi

Why it's there: Remote-control opens the door to controlling sessions from the phone; push notifs page me when a long agent run finishes. Lets the night-shift cadence keep working when I'm not staring at the screen.

{
  "remoteControlAtStartup": true,
  "agentPushNotifEnabled": true
}

Why it's there: Distinctive frontend output — used heavily on the howiclaude rig-page redesign.

Why it's there: Brainstorming, TDD, systematic-debugging, writing-plans — the discipline rails.

Why it's there: Swift work outside this repo.

Why it's there: Periodic CLAUDE.md audits + the revise-claude-md command.

Why it's there: Building / editing custom skills.

Why it's there: code-architect / code-explorer / code-reviewer subagents.

Why it's there: Automation recommender + setup helpers.

Why it's there: Search threads, draft replies, label triage from inside Claude — kills the context-switch cost of jumping back to mail mid-session.

Why it's there: Yes, on an Air. The Air is enough — Claude does the heavy lifting in the datacenter. The constraint forces tight session hygiene + worktree discipline.

Why it's there: 27" 5K at 2560×1440 UI scale. One big canvas: editor + statusline + terminal all visible at once; no window-shuffling between context-switches.

Why it's there: MX Master scroll wheel + back/forward buttons are worth real money for fast file navigation. The MX keyboard's quiet keys matter on the night shift.

Why it's there: Voice-hold dictation goes through the AirPods mic. The noise-canceling means the household can be loud without it bleeding into the transcription.

Why it's there: Scaled from the 113-day window. Dollar figure stays private.

Why it's there: ≈11 sessions a day across ~14 projects. The rhythm is project-switching, not single-flow.

Why it's there: Opus does the work, Haiku does the background labels (badge updater), Sonnet barely appears. The price tag is the trade — bought back in throughput.

Why it's there: Hour-of-start buckets: 21h=158, 22h=146, 20h=119, 19h=97. The Night Shift signature is unambiguous.

Why it's there: Built one 10pm session at a time. Current streak: 5 days.