nilbus

name	migrate-cmux-to-paseo
description	Migrate cmux workspaces into Paseo, bringing over agent sessions (Claude/Codex/OpenCode), workspace titles, pins, color labels, split layouts, browser tabs and last-activity times. Use when the user wants to move from cmux to Paseo, import cmux workspaces or sessions into Paseo, or redo such a migration.

Migrate cmux to Paseo

One script, migrate.py, does everything in a single run, starting with Paseo quit:

1. Import. Starts the Paseo daemon and runs paseo import for every agent session in the cmux session file, tagged with source=.

nilbus

Security Audit Report: beads (bd) CLI

Date: 2026-08-11
Repository: https://github.com/gastownhall/beads
Version: v1.1.2 + 2 weeks of unrelease commits
Commit SHA: 18c24a3ac3e737c34cb478d58ecf3a805a99e996
Scope: Full security audit of a Go CLI tool for issue tracking with Dolt/SQLite backends, git sync, and AI agent integration.
Methodology: glm-5.2-max investigation covering 300+ Go source files, dependency manifests, CI pipelines, and install scripts, searching for unintentional and malicous security issues.

---

nilbus

Overview

OpenCore Legacy Patcher (OCLP) uninstall has 3 parts:

1. undo any root patches, 2) remove the OpenCore bootloader from EFI (or USB), 3) remove the app and its data.
   Below are safe, step‑by‑step instructions based on the official uninstall guide and current docs.[1][2]

---

Before you start

nilbus

Your big feature is tested and ready to go! Time to merge, and then…

Nooooo! 😭 Memories arise of hours of uncertainty spent trying to resolve past conflicts. Sure, there are lots of UIs that make picking one side or the other easier than using the command line, but is picking sides really the right answer?

I’ll share a hidden gem that, for me, has turned conflict resolution from frustration into something of a joy. Git has a built-in feature that you can enable called the diff3 conflict resolution strategy. Turning this setting on enables a predictable approach to understanding and resolving the conflicts you encounter.

I’ll note that git conflicts can be minimized through practices such as Trunk Based Development with Feature Flags, breaking features into smaller chunks that you can deliver incrementally, and refactoring hotspots

nilbus

GEM
  remote: https://custom.source/repository/gems/
  specs:
<<<<<<< ours
    active_model_serializers (0.10.13)
      actionpack (>= 4.1, < 7.1)
      activemodel (>= 4.1, < 7.1)
      case_transform (>= 0.2)
      jsonapi-renderer (>= 0.1.1.beta1, < 0.3)
    activerecord-import (1.2.0)

nilbus

require 'set'
require 'json'
require 'objspace'

DIFF_FILENAMES = ['/tmp/1.json', '/tmp/2.json', '/tmp/3.json']

def dump_memory(n)
  BatchLoader::Executor.clear_current
  GC.start
  file = File.open("/tmp/#{n}.json", 'w')

nilbus

# Adapted from https://blog.skylight.io/hunting-for-leaks-in-ruby/
require 'set'
require 'json'
require 'objspace'

DIFF_FILENAMES = ['/tmp/1.json', '/tmp/2.json', '/tmp/3.json']

def dump_memory(n)
  BatchLoader::Executor.clear_current
  GC.start

nilbus

# make a temp directory for each repo to examine
mkdir doximity doc-news activities

# copy in migrations from 2019
for dir in *; do cp ~/work/$dir/db/migrate/2019* $dir/; done

# remove migration reversal code to exclude from search
sed -i'' -re '/def down/,$d' */*

# count unique migration files per repo that modify existing schema structure (tables, columns)

nilbus

*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil

nilbus

GIT-ABSORB(1)                            git absorb                            GIT-ABSORB(1)

NAME
       git-absorb - Automatically absorb staged changes into your current branch

SYNOPSIS
       git absorb [FLAGS] [OPTIONS]

DESCRIPTION
       You have a feature branch with a few commits. Your teammate reviewed the branch and