phase3dev

#!/usr/bin/env bash
set -euo pipefail

# --- Your GLM API key, kept OUT of this script -----------------------------
# Put the key in a private file once (readable only by you), and this launcher
# loads it at runtime. That way the key never lives in this script, so you can
# copy, share, or post the launcher without leaking it.
#     mkdir -p ~/.config/glm
#     printf '%s\n' 'YOUR_ZAI_API_KEY' > ~/.config/glm/api_key
#     chmod 600 ~/.config/glm/api_key            # 0600 = only you can read it

davidondrej

Here's the full setup to make Pi use OpenRouter by default, with your API key stored locally inside Pi's own config (no system-wide env var needed):

---

Step 1 — Create Pi's config directory (if it doesn't exist)

mkdir -p ~/.pi/agent

tkafka

Electron Apps Causing System-Wide Lag on Tahoe

This script detects apps with not yet updated versions of Electron.

Repo: https://github.com/tkafka/detect-electron-apps-on-mac

See:

• electron/electron#48311 (comment)
• Michael Tsai: Electron Apps Causing System-Wide Lag on Tahoe

KMJ-007

Manage Multiple Claude Code Accounts

Run two Claude Code accounts simultaneously on macOS without re-authenticating by using separate configuration directories.

Steps

1. Create Separate Config Directories

   mkdir ~/.claude-account1
   mkdir ~/.claude-account2

Killeroid

Every so often I have to restore my gpg keys and I'm never sure how best to do it. So, I've spent some time playing around with the various ways to export/import (backup/restore) keys.

Method 1

Gotten from the RedHat GPG migration manual

Backup the public and secret keyrings and trust database

## Export all public keys

gpg -a --export >mypubkeys.asc

kamito

BLACK  => "\033[30m",
RED    => "\033[31m",
GREEN  => "\033[32m",
YELLOW => "\033[33m",
BLUE   => "\033[34m",
PURPLE => "\033[35m",
CYAN   => "\033[36m",
WHITE  => "\033[37m",

# background color