Reset an IKEA Kajplats lightbulb by power cycling it 6 times and then leaving it on until it blinks, then it’ll be in pairing mode again. Thanks fishymanbits on Reddit!

Step by step:

1. Turn off the bulb for 30s
2. Power cycle 6 times; on until it lights up, off immediately, count “one one thousand”, repeat
3. On the sixth on, leave it on and wait
4. When the bulb blinks it’ll be in pairing mode again

Matter over Thread requires IPv6 on your local network, so if you can’t pair the IKEA Kajplats bulb that might be why.

I didn’t have IPv6 enabled, and my ISP doesn’t assign IPv6, so I used unique-local-ipv6.com to get a unique prefix. Configured it as static in my local network setup, alongside the IPv4 configuration, on my UniFi Dream Machine and then all my bulbs connected.

Now my niece is learning to pronounce English colors as she cycles my apartment through every shade of the rainbow 😁

beads 1.0.1 flipped the export.auto default to on, so old projects silently start exporting issues.jsonl after upgrade. To opt back out, run:

bd config set export.auto false

New projects get prompted during init, only existing projects will get this nice surprise.

If you’re using dolt’s git export instead, commit the config change and delete the issues.jsonl file.

When dolt’s journal is corrupted, dolt fsck --revive-journal-with-data-loss will truncate it back to the last valid record.

I found this error message when starting dolt up after upgrading the server: invalid journal record at offset 5831169: invalid journal record: CRC checksum does not match.

To recover, go to your dolt DB:

cd ~/.beads/shared-server/dolt/<db> \
  && dolt fsck --revive-journal-with-data-loss

It backs up the journal, truncates to the point it failed, and makes it possible to start the server again. In my case the db came back up with data loss. I did a bd dolt pull and it pulled in what I had pushed most recently, so nothing major was lost.

I’m guessing this happened because installing beads 1.0 also upgraded dolt. If you’re upgrading, it’s worth making sure you’ve done bd vc commit && bd dolt push in all repos beforehand. That means configuring a git remote first.

dolt’s shared server won’t pull until all databases on the server have committed changes, not just the beads project you’re pulling.

You’ll get Error 1105 (HY000): cannot merge with uncommitted changes and it’s confusing when the beads project you’re working in has autocommit on. The uncommitted changes are in a different project that’s also using the shared server.

The fix is to go through your other projects and commit their changes (or enable autocommit by adding dolt.auto-commit: "on" to .beads/config.yml). To find which databases have uncommitted changes:

query=$(bd sql "SHOW DATABASES" 2>/dev/null \
  | grep -v -E "^(Database|--|\(|dolt|information_schema|mysql)" \
  | while read db; do
      echo "SELECT '$db' as db, table_name, status FROM \`$db\`.dolt_status WHERE table_name != 'config'"
    done \
  | paste -sd'|' - | sed 's/|/ UNION ALL /g')
bd sql "$query"

For each project that shows up, go in and run bd vc commit -m 'Snapshot', and then you can pull again.

We’re ignoring changes to the config table because they don’t seem to matter for pulling.

You can manually clone a dolt database from its git remote when bd bootstrap or bd init won’t cooperate.

1. bd dolt stop: stop the server in the git repo you’re restoring so you can operate on its database
2. cd ~/.beads/shared-server/dolt: go to the shared dolt server (it’s .beads/dolt/beads otherwise, I think)
3. rm -rf <prefix>: remove the DB if it exists already
4. dolt clone git+ssh://[email protected]/user/repo.git <prefix>: clone it to your prefix
5. cd - && bd ready: see if you can see the listing

I don’t know why my local just refused with bd bootstrap but this allowed me to fix it manually.

To switch beads from a per-project dolt server to the shared server, do a backup, configure shared-server, and restore.

I was running in “a server per repo” mode and it’s just unnecessary, they clash in annoying ways when switching repos, and once I understood how beads store data in git I embraced dolt and the shared server. I had hesitated because I had somehow connected it with DoltHub, and that’s optional for using beads.

1. bd backup: make sure you have your local database available for restore
2. bd dolt stop: so we don’t conflict on anything
3. bd dolt set shared-server true: to configure this project to use the shared server
4. bd restore: to restore the db

For most of my projects this just worked, but in some cases I had to reset the dolt configuration for the repo.

I tweak the default beads setup to work with Claude instead of the generic agent integration.

As of beads 0.62.0, this is what I run:

# configure agents later
bd init --shared-server --skip-agents

# setup a CLAUDE.md and configure claude hooks to re-prime beads
bd setup claude --project
bd hooks install

# move local settings to project settings
mv .claude/settings{.local,}.json

# amend init commit so .beads-credential-key never enters git
git add .claude/settings.json CLAUDE.md
git commit --amend -CHEAD

# share beads data alongside your git repo
bd dolt remote add origin git+ssh://[email protected]/you/repo.git
echo -e 'sync:\n  git-remote: git+ssh://[email protected]/you/repo.git' >> .beads/config.yaml

The key thing is --skip-agents and then bd setup claude --project instead, so you get Claude-specific hooks rather than the generic agent integration. The dolt remote lines are so your beads data gets stored alongside your git repo.

Start with the smallest test print you can, no, even smaller, when iterating on a 3D model.

• Top: the first print, fully believing I had nailed everything on the first try (also some hope, it was printing over night so hey, it might mean I’m done with this first design)
• Middle: second print, cut smaller but enough to let the device rest. Made me realize I hadn’t taken into account that the device tapers at the top and bottom, so it needs less living space
• Bottom: latest print, cut to print as small as possible, and maybe too small, but it seems to indicate this is good. Next up, a full print

Next time, reverse the order 😅

git rm --cached <file> will remove a file from git’s tracking but leave it on the filesystem. Great if you accidentally commit something that should’ve been in .gitignore.

Set GENERIC_TIMEZONE for n8n or you’ll get ERROR: You specified an invalid date. when you try to publish a time triggered workflow.

I had done a server migration and completely missed the .env file when copying, and after recreating it all started working.

Add commands to both permissions.allow and sandbox.excludedCommands to run them outside Claude Code’s sandbox by default, because allow grants permission to run at all and excludedCommands runs them unsandboxed.

{
  "permissions": {
    "allow": [
      "Bash(pnpm test:unit:*)",
      "Bash(pnpm test:e2e:*)"
    ]
  },
  "sandbox": {
    "excludedCommands": [
      "pnpm test:unit:*",    // Same commands, different purpose
      "pnpm test:e2e:*"
    ]
  }
}

Note: Tested with Claude Code v2.1.3

Write out colon subcommands explicitly for Claude Code permissions because test:* doesn’t match test:unit (prefix matching treats them as separate commands), and the fallback test* is too broad (matches testAndDestroyEnvironment).

For example:

{
  "permissions": {
    "allow": [
      "Bash(pnpm test:unit:*)", // Allows pnpm test:unit --arg etc.
      "Bash(pnpm test:e2e:*)",
      "Bash(pnpm test*)"        // ❌ <- will allow testAndDestroyEnvironment
    ]
  }
}

Note: Tested with Claude Code v2.1.3

Marking the content/ folder for your Hugo site as a “Source Root” in IntelliJ lets you use Path from Source Root to get the path to the file without the content/ prefix you don’t need when linking internally.

To make linking internally easier, I created an Alfred app snippet ({{< relref “{clipboard}” >}}), so now I only have to open the other post, double-tap shift, type “source root”, then run the snippet, and all linked up.

Use /@<name> to access the value of an attribute when you’ve selected an element with XPath.

With the expression //*[@class="published-at"] you will get the HTML tag that has class="published-at", and if you then want the datetime property you add /@datetime to get it.