WeWorkBuddy

Show HN: Record, branch, and compare command runs in stdlib-only Python

Hi, this is a package I developed for keeping track of short toy-model development cycles and explaining what changed between runs. The core idea: commands run through the package, and their declared parameters (or injected parameters with --substitute) and outcomes go into a dependency-free ledger stored in the project. Because that ledger lives in the project directory, it has worked well for passing context between different agents. I’ve also found some use for it in CI work.

Read original source
Source page screenshot: Show HN: Record, branch, and compare command runs in stdlib-only Python
Source page screenshot · news.ycombinator.com

Source record

Recorded metrics

points · 3 votes
2026-11-09 00:00:22.456Z
cumulative since publication

Research analysis

Project record

Repository: Protention/ocura-oss. Source account: Hi, this is a package I developed for keeping track of short toy-model development cycles and explaining what changed between runs. The core idea: commands run through the package, and their declared parameters (or injected parameters with --substitute) and outcomes go into a dependency-free ledger stored in the project. Because that ledger lives in the project directory, it has worked well for passing context between different agents. I’ve also found some use for it in CI work.

Observed adoption & comparisons

Source votes: 3 votes (Nov 9, 2026 UTC; cumulative since publication) Recent records to compare: “meta/astryx” (GitHub Trending, Nov 8, 2026); “vercel-labs/agent-browser” (GitHub Trending, Nov 8, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Adoption decision

Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.

Unverified requirements

Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.

Next test

Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.