Max

Announcing Worktrunk! A git worktree manager, designed for running AI agents in parallel. A few points on why I'm so excited about the project, and why I hope it becomes broadly adopted 🧵

@robinhanson personal benefits _for the insiders_

@max_sixty Well connected reporters DO gain concrete personal benefits from that.

Many worried about "insider trading", but few worry about "insider journalism". But is it fair that reporters with better connections write more informative and interesting stories? Shouldn't we make sure news stories are only based on public info equally open to all reporters?

@WillManidis very difficult to beat

just peak Tyler, it doesn’t get better than this

@ortonomy_ ah sorry, that's also v simple though, just normal GHA: github.com/max-sixty/work…

@max_sixty Thanks for sharing - what is running the bot user/claude though? Claude scheduling?

@max_sixty Hey would you be open to sharing your bot setup for worktrunk? It seems incredibly efficient.

@dmwlff @badlogicgames @sprobertson @swyx @dillon_mulroy but /fork doesn't fork, it's more like exec; it starts from new history!

@sprobertson @swyx @dillon_mulroy @badlogicgames I am working on this! I just renamed Claude Code's existing /fork command to /branch in preparation for a new primitive I'm excited about.

thoughts after day 1 of using pi full time - less is more - i don't miss subagents like i thought i would - /tree is an insanely good context management primitive (and partially why i havent reached for subagents yet) - based only on vibes, i think having a minimum system prompt is improving code quality - telling pi to copy opencodes webfetch and websearch tools was a good play

guys, please, let my kids spend some time with their father

@nickcammarata `@AGENTS.md` will do this deterministically

all my claude.mds just say please read agents.md

@devopstoolbox it needs a `git fetch`, and then it's good! #issuecomment-4018520610" target="_blank" rel="nofollow noopener">github.com/max-sixty/work…

@max_sixty exactly. I don't find myself using merge not even when I'm the only dev on an open source project simply bc I'd like this to go through github's PRs

Worktrunk by @max_sixty is a fantastic utility! Check it out: youtu.be/WBQiqr6LevQ

@T0bias_Brandt @devopstoolbox thanks dude! miss you! come by LA again soon

@max_sixty @devopstoolbox I didn't realise this was your project until I installed it. This is awesome! 🚀

beautifully made video on Worktrunk from @devopstoolbox youtu.be/WBQiqr6LevQ?t=…

@devopstoolbox let me confirm the first point. personally, I have a skill which does the PR workflow, and it does `git up` and then ` git merge main`, and then the branch shows as merged sounds like I need to ensure that Worktrunk can understand when something has been squash-merged

@devopstoolbox good question! - if we run `git fetch`, then we shouldn't need the `-D` - recently added `wt step prune` which will clear up old worktree / branches that have merged into main

one downside of selling weapons to rich nepotistic allies is their newfound cability to mistakenly shoot down your planes

@devopstoolbox (fyi we do have the fuzzy finding! only Mac & Linux. but try `wt switch`. I need to make it faster for huge repos though)

@devopstoolbox awesome video, very beautifully made! ofc let me know any feature requests, seems like you've really thought about the workflows

@rsms @jtaby maintainer here: I think we could implement this with an alias-like command, thanks for the case. will think about a good design this week github.com/max-sixty/work…

@jtaby Looks like it can only be used to "set things up", not replace the executable (exec.) #post-create" target="_blank" rel="nofollow noopener">worktrunk.dev/hook/#post-cre…

A workflow I've found useful lately for agent-driven programming is to have an extra level of git-repo indirection locally: a bare git repo + many local clones that pull/push to that one bare repo. The bare repo push/pull to a central repo like github. I.e. ~/src/foo-bare # git remote on different computer ~/src/foo-a # git remote is ~/src/foo-bare ~/src/foo-b # git remote is ~/src/foo-bare ~/src/foo-... The -a -b etc clones are like tables in a workshop. Pick an empty table when you start a new project for foo, then keep working on that table. When you're done, clean the table. Reuse the -a -b ... clones. What this enables is both offline work as well as merging/sharing changes across projects very quickly and without the need to push them to something like github. Maybe there's a better way and I'm only starting to try this approach out, but it's interesting enough to share I think!

@digital_parad0x I haven't heard much about this specific problem; though possibly I don't have a large enough sample size I've tried to focus on single-repo solutions so far...

@max_sixty Anyway, does that response mean it hasn't really been discussed and/or isn't a problem you'd consider addressing in worktrunk?

Announcing Worktrunk! A git worktree manager, designed for running AI agents in parallel. A few points on why I'm so excited about the project, and why I hope it becomes broadly adopted 🧵

@digital_parad0x why not move to a monorepo?

@max_sixty (2/2) if there was a way to declare these associated repos and when creating a worktree create a corresponding one for each of the repos (either always, or when explicitly instructed to at creation time). Has this been thought about/discussed? (my GH search terms came up empty)

whatever OpenAI's object-level beliefs, defecting when Anthropic is attempting to cooperate, is terrible behavior and makes the future more dangerous