2026-03-19 Thu

• Task/Management/Git-Friendly/Report/26/CRDT vs SQLite in git for task management
• Beads and Dolt woes
  • Umbrella: consolidate Beads repo-local Dolt runtime layer · Issue #2685 · steveyegge/beads
    • Username/garitar has a big PR that, to me, signals a different era in open source. unlike the notorious issue where an openclaw agent tried to write a disparaging blog post about a maintainer of matplotlib, this is a human driver. they have a quit lengthy "umbrella" issue writen by an AI, and they have five seemingly incremental PRs that are referenced with a human-written follow-up comment indicating that "given the amount of compute I threw at this I'd expect it to be fairly solid ;)." The PR comment itself reads like a bit of Word/Salad to me:

      • The landing sequence follows that dependency order:
        

        • lifecycle precursor
        • runtime foundations
        • doctor/runtime alignment
        • repair safety
        • final-tail hardening
        • embedded/schema tail
    • it's hard to run an open source project today.
  • Added a comment to Moving to dolt pretty much made beads unusable for me · Issue #2573 · steveyegge/beads
    • I must agree that the upgrade to dolt has made beads pretty much unusable.
    • Comment/My referenced Agentic Code Can Harbor Recurrent Heresies (1min) from Person/Steve Yegge

      • To answer your question directly: yes, beads is supposed to store issues in git via .beads/issues.jsonl. The JSONL file is committed to git, so your issue data survives Dolt failures — it just requires a recovery step to reimport it.
        

      • Oh, good to know! I just created a bunch of rules to instruct my agents to not use or mention that file, because the idea of tasks being stored in two places made me uncomfortable because of the risk of heresies, and it was causing the typical merge conflicts that I was getting before the dolt upgrade.
      • Does anyone have a sample skill that they use now that they are on the dolt version of beads?
  • added another comment to the same thread
    • tools from Haplab Haplab:
    • 1. td marcus/td: A minimalist CLI for tracking tasks across AI coding sessions. (docs: td)
    • 2. td/sidecar marcus/sidecar: Use sidecar next to CLI agents for diffs, file trees, conversation history, and task management with td (docs: You might never open your editor again | Sidecar)
    • I haven't used these. I'm curious about how others use td's sqlite approach with git.