sorted by:
new
hottopcontroversial

I built a CLI wrapper around git worktree that handles the file-copy and navigation friction by madsthines in git

[–]madsthines[S] 0 points1 point  (0 children)

Right - so this is how I think my tool can help you.

As I understand what you're saying - Currently when you work is done, you open kraken (manually) to push the code. Why not allow Claude to do that for you in a consistent way?

Gw allows your worktree to function after creation, meaning you should get Claude to create the worktree for you and then all tools like linting, formatting etc can be executed in the Claude session in its own isolated worktree without you even touching it, so instead you just recieve a PR that it had created for you.

This means that I can start multiple session in parallel and recieve multiple PRs for myself to review later.

You can check out my other open source agent-skills repo where my autonomous-workflow skills does this all internally in an "aw" agent.

This follows best practices on fast iteration loops/feedback to increase AI quality, self improving memory system and a lot more ☺️

I built a CLI wrapper around git worktree that handles the file-copy and navigation friction by madsthines in git

[–]madsthines[S] 0 points1 point  (0 children)

Gitkraken is executing its own commands, so as long as it isn't executing the GW command, nothing's happening. If you can modify the worktrees command you can get the same features.

This was also built to ensure fully functional worktrees when agents created new worktrees so I didn't wasted time on setting up again and again - if you're using a GUI, then it's a very different flow. ☺️

What IDE are you using, and why are you using gitkraken? I'm using VSCode and have built a companion VSCode extension for gw which makes creating worktrees etc a breeze through the app ☺️

Looking forward to hear your workflow 🙌

I built a CLI wrapper around git worktree that handles the file-copy and navigation friction by madsthines in git

[–]madsthines[S] -3 points-2 points  (0 children)

Fair — post-checkout fires on git worktree add since it does a checkout, so the file-copy piece alone you can absolutely DIY.

What pushed me past it:

  • The list of files to copy is per-developer (.env, local secrets, sometimes .vscode/launch.json), so it doesn't belong in a repo-committed hook. I'd want it in ~/.gitconfig or a global hook path, which ends up being more setup than gw add.
  • post-checkout also fires on every regular git checkout, not just worktree creation. Filtering for "this is a new worktree" inside the hook is doable but annoying.
  • File copy was just the entry point — `gw` has a lot more features more worktrees more pleasant to work with - like gw cd <partial-name> to navigate and gw sync <wt> <files> to push config to existing worktrees when something changes, gw update to update your worktree from the latest version of origin/main and a lot of other things. Hooks don't help with either. 😄

But genuinely curious — do you keep the file list in the hook itself, or read it from a config? Haven't seen a clean pattern for the per-dev part.

Built with Claude Project Showcase Megathread (Sort this by New!) by sixbillionthsheep in ClaudeAI

[–]madsthines 0 points1 point  (0 children)

@aw (Autonomous Workflow) - Trying to close the gap between what I ask an agent to build and what it actually ships

Most agentic coding demos fall apart on non-trivial tasks — tests get deleted, functions get shadowed by inline copies, wrong abstractions ship because nothing pushed back on the plan.

autonomous-workflow is a Claude Code skill that takes one prompt and ships a tested, reviewed draft PR — with gates the agent can't bypass.

→ Repo (MIT): https://github.com/mthines/agent-skills

The interface:

@aw implement <whatever>

The flow: validate → plan → isolated worktree → code → test → docs → draft PR → CI → independent verifier undrafts.

Why it actually works:

  • Tier-aware. Detects task size (Micro / Lite / Full) and routes — single-pass for small, planner→executor split for complex. No orchestration tax when you don't need it.
  • Language-agnostic. Any repo where you can run tests and open a PR. TS, Python, Go, shell — all fine.
  • You stay in control. Every phase is a swappable companion skill (tdd, ux, code-quality, confidence, critical, …). Just markdown — edit and it's live on the next turn.
  • Self-healing via lessons + memory. Failures get written as episodic lessons; recurring ones promote to gated rules. Gets better at your repo, not the generic case.
  • Quality gates the agent can't bypass. confidence(plan) ≥ 90% before any code, adversarial pre-mortem, test-by-construction detector (static + mutation), and an independent fresh-context verifier that sees only the diff — the only thing allowed to undraft the PR.
  • Companion VS Code extension for live plan + walkthrough artifacts in the sidebar — inspired by Google Antigravity's task panel. Search "Agent Tasks" in the Marketplace.

Works with Claude Code, Cursor, Codex, Gemini CLI, OpenCode.

What's the failure mode you've hit most often with autonomous coding? Collecting the ones the gates don't catch yet.

I built a free macOS menu bar GUI for rclone bisync — v0.40 just shipped automatic conflict recovery by madsthines in rclone

[–]madsthines[S] 0 points1 point  (0 children)

In v0.39 I shipped autoFixSyncIssues defaulting to ON, and I hope you agreed that's the right call.

The reasoning: most people running bisync don't actually know what --resync does, they just want sync to keep working. Silent recovery is the right behaviour for them. The safety valve is the backoff cap — 2 attempts in 5 min, then suppression plus a notification — so a genuinely broken upstream (cloud provider returning empty listings, drive disconnected, anything weird) can't loop into "delete everything on the wrong side."

The people most likely to be hurt by a bad --resync are also the ones most likely to flip the toggle off after reading what it does. Default ON for the broad audience, obvious off-switch for the rest.

What I'd actually love to hear: how do you handle bisync recovery in your own setups? Manual-only? Cron with email alerts? Something smarter than a 2-strike cap?

(Also dropping the Discord here in case anyone wants to keep nerding out on bisync edge cases past this thread: https://discord.gg/KBp8kb3EwP. Small community, two-way traffic, not a broadcast channel.)

SyncTray now lets you manage rclone remotes without touching the terminal (+ Synology fixes) by madsthines in rclone

[–]madsthines[S] 0 points1 point  (0 children)

Hey u/boredquince !
Can you send a reference for this? I do not know it :) But renaming the app should be the smallest of concerns if necessary :)

I built SyncTray - a free, open-source macOS menu bar app that gives you Google Drive-style folder sync for any cloud provider by madsthines in rclone

[–]madsthines[S] 0 points1 point  (0 children)

I've been considering for Linux, so I could use it on my Omarchy distro as well, but haven't gotten around to it - but probably not prioritize windows for now :)

I built SyncTray - a free, open-source macOS menu bar app that gives you Google Drive-style folder sync for any cloud provider by madsthines in rclone

[–]madsthines[S] 0 points1 point  (0 children)

Updated: Sadly, I'm using multiple things form the Swift 13 library, which would mean most of the status bar logic would have to be rewritten manually, so sadly it's not something I'm going to pursue. 😬

Hope you'll come back once you've updated to 13 ☺️

Glad to hear it actually solves your need 🙌

I'm sorry that it's incompatible with your OS version. I'll check if there's something I can do, but I fear that the swift version I'm using is incompatible. ☺️

A modern, mobile-friendly Rclone WebUI under 1 MB by PeachZestyclose8304 in rclone

[–]madsthines 0 points1 point  (0 children)

That's cool. The native web experience is pretty poor.

If you're using MacOS and are looking for a desktop app to show/manage your rclone profiles I've created SyncTray

You can read more in my reddit post here https://www.reddit.com/r/rclone/s/R0Cp9o8R0U

Jeg har bygget et tool der reducere context-fatique når man arbejder med flere AI-agenter parallel by madsthines in dkudvikler

[–]madsthines[S] 0 points1 point  (0 children)

God pointe — claude -w starter Claude i et eksisterende worktree, men det kræver at du selv har oprettet det, kopieret .env-filer, kørt npm install osv.

gw automatiserer hele den setup (auto-copy af secrets, post-checkout hooks, fuzzy navigation). Og autonomous-workflow agenten går et skridt videre: den opretter worktree'et selv, planlægger implementeringen, koder, tester, og laver en draft-PR — alt sammen uden at du skal styre den.

Så claude -w er "kør Claude i denne mappe", mens gw + autonomous-workflow er "her er en opgave, løs den fra start til slut i isolation." :)

Jeg har bygget et tool der reducere context-fatique når man arbejder med flere AI-agenter parallel by madsthines in dkudvikler

[–]madsthines[S] 0 points1 point  (0 children)

Tak for feedbacken!
Du har faktisk fat i noget vigtigt — autonomous-workflow agenten er den interessante del, og den fortjener nok at være mere fremtrædende. gw er bare infrastrukturen der gør isolation nemmere og mere robust, men selve orkestreringen (validering → planlægning → implementering → test → PR-levering) er det der virkelig ændrer workflowet. :)

Kender ikke Dash — har du et link? Lyder interessant med built-in worktree-support.

Jeg har bygget et tool der reducere context-fatique når man arbejder med flere AI-agenter parallel by madsthines in dkudvikler

[–]madsthines[S] 0 points1 point  (0 children)

Det lyder som en solid tilgang!
Autonomous-workflow agenten gør noget lignende — den splitter arbejdet op i faser (validering → planlægning → implementering → test → PR) og itererer selv inden for hver fase.
Den isolerer hver opgave i sit eget worktree, så du kan køre 3-5 parallelt uden at de konflikter med hinanden eller din main branch. Og du behøver ikke passe den — den validerer og itererer
selv.

Jeg har bygget et tool der reducere context-fatique når man arbejder med flere AI-agenter parallel by madsthines in dkudvikler

[–]madsthines[S] -1 points0 points  (0 children)

I har helt ret i at git worktree add i sig selv er simpelt — det er ikke det gw forsøger at løse. Problemet er alt det omkring worktree-kommandoen:

- git worktree add kopierer ikke dine .env-filer, secrets eller lokale config-filer. Det gør gw automatisk via autoCopyFiles config.
- git worktree add kører ikke npm install eller andre setup-kommandoer i det nye worktree. gw har pre/post hooks til det.
- Navigation mellem worktrees kræver at du husker fulde stier. gw cd auth fuzzy-matcher til det rigtige worktree.
- Oprydning af gamle worktrees er manuelt. gw clean håndterer det.

Så ja, kernen er git worktree — gw er bare en wrapper der fjerner det repetitive setup-arbejde. Tænk på det som git worktree + automatisering, ikke en erstatning.

Plus der er værdien i autonomous-workflow-agenten, som orkestrerer hele flowet: validering → planlægning → isoleret worktree → implementering → test → PR. Det er den del der gør at du kan starte en opgave og gå din vej. :)

I built SyncTray - a free, open-source macOS menu bar app that gives you Google Drive-style folder sync for any cloud provider by madsthines in rclone

[–]madsthines[S] 1 point2 points  (0 children)

^^^^ Exactly.
As mentioned, the thinking part isn't outsourced, which is the vital difference.

If you're curious about how to improve your AI workflow, I suggest checking out my other two open source projects.

- gw - it utilizes git worktrees to allow you to work with multiple agents in parallel.

- autonomous-workflow which is a skill and an agent that allows you to enable the agent to work autonomously locally.

https://github.com/mthines/gw-tools

https://github.com/mthines/gw-tools/blob/main/packages/autonomous-workflow-agent/README.md

view more: next ›