Nick Rempel
@nrempel.com
Software engineer @foxglove.dev by day, tinkerer by night, dad 24/7. Token intermediator.
Why I built it
I like to keep context small and focused. Spin up parallel agents without dragging in extra surface area.
It makes starting/parking work cheap so you can explore, review, and merge with less friction.
Check it out github.com/nrempel/wt
I like to keep context small and focused. Spin up parallel agents without dragging in extra surface area.
It makes starting/parking work cheap so you can explore, review, and merge with less friction.
Check it out github.com/nrempel/wt
GitHub - nrempel/wt
Contribute to nrempel/wt development by creating an account on GitHub.
github.com
November 6, 2025 at 5:28 AM
Why I built it
I like to keep context small and focused. Spin up parallel agents without dragging in extra surface area.
It makes starting/parking work cheap so you can explore, review, and merge with less friction.
Check it out github.com/nrempel/wt
I like to keep context small and focused. Spin up parallel agents without dragging in extra surface area.
It makes starting/parking work cheap so you can explore, review, and merge with less friction.
Check it out github.com/nrempel/wt
wt status shows the state of every worktree at a glance.
wt archive bundles a branch + writes a diff; wt restore brings it back when you’re ready.
Hooks let you auto‑run team/agent setup after new, archive, or restore—great for kicking off Claude Code or Codex in that workspace.
wt archive bundles a branch + writes a diff; wt restore brings it back when you’re ready.
Hooks let you auto‑run team/agent setup after new, archive, or restore—great for kicking off Claude Code or Codex in that workspace.
November 6, 2025 at 5:28 AM
wt status shows the state of every worktree at a glance.
wt archive bundles a branch + writes a diff; wt restore brings it back when you’re ready.
Hooks let you auto‑run team/agent setup after new, archive, or restore—great for kicking off Claude Code or Codex in that workspace.
wt archive bundles a branch + writes a diff; wt restore brings it back when you’re ready.
Hooks let you auto‑run team/agent setup after new, archive, or restore—great for kicking off Claude Code or Codex in that workspace.
So I built wt, a tiny wrapper around git worktree that makes worktrees feel disposable and fast.
What it does
wt new <name> spins up a clean worktree under .worktrees/<name> (from origin/main) and drops you into it.
wt switch jumps between worktrees without losing shell history.
What it does
wt new <name> spins up a clean worktree under .worktrees/<name> (from origin/main) and drops you into it.
wt switch jumps between worktrees without losing shell history.
November 6, 2025 at 5:28 AM
So I built wt, a tiny wrapper around git worktree that makes worktrees feel disposable and fast.
What it does
wt new <name> spins up a clean worktree under .worktrees/<name> (from origin/main) and drops you into it.
wt switch jumps between worktrees without losing shell history.
What it does
wt new <name> spins up a clean worktree under .worktrees/<name> (from origin/main) and drops you into it.
wt switch jumps between worktrees without losing shell history.
This reminds me of playing Starcraft, coordinating several agents at once. Multitasking is the new meta.
November 3, 2025 at 10:38 PM
This reminds me of playing Starcraft, coordinating several agents at once. Multitasking is the new meta.
It has built in git diff/review features built in. Tell it to use your gh CLI and you can have each agent open its own PR.
You can use both Claude and Codex AND it leverages your monthly plan (or API keys if you want).
You can use both Claude and Codex AND it leverages your monthly plan (or API keys if you want).
November 3, 2025 at 10:38 PM
It has built in git diff/review features built in. Tell it to use your gh CLI and you can have each agent open its own PR.
You can use both Claude and Codex AND it leverages your monthly plan (or API keys if you want).
You can use both Claude and Codex AND it leverages your monthly plan (or API keys if you want).
Totally agree that it's not a silver bullet. But I think we can tilt the build vs import scale much further in favour of build now.
But yes, I'm definitely not suggesting we codegen rustls or something as some others in this thread suggest. (I addressed that directly in the post)
But yes, I'm definitely not suggesting we codegen rustls or something as some others in this thread suggest. (I addressed that directly in the post)
November 1, 2025 at 8:46 PM
Totally agree that it's not a silver bullet. But I think we can tilt the build vs import scale much further in favour of build now.
But yes, I'm definitely not suggesting we codegen rustls or something as some others in this thread suggest. (I addressed that directly in the post)
But yes, I'm definitely not suggesting we codegen rustls or something as some others in this thread suggest. (I addressed that directly in the post)
OpenAI’s charter language. "Highly autonomous systems that outperform humans at most economically valuable work."
blogs.microsoft.com/blog/2025/1...
blogs.microsoft.com/blog/2025/1...
The next chapter of the Microsoft–OpenAI partnership - The Official Microsoft Blog
Since 2019, Microsoft and OpenAI have shared a vision to advance artificial intelligence responsibly and make its benefits broadly accessible. What began as an investment in a research organization has grown into one of the most successful partnerships in our industry. As we enter the next phase of this partnership, we’ve signed a new definitive...
blogs.microsoft.com
October 30, 2025 at 5:28 PM
OpenAI’s charter language. "Highly autonomous systems that outperform humans at most economically valuable work."
blogs.microsoft.com/blog/2025/1...
blogs.microsoft.com/blog/2025/1...
If you have been using the old storyline that OpenAI would declare AGI to void the deal, update your model. The revised terms shift this from a cliff to a controlled process with longer dated IP certainty.
Definition I am using for AGI:
Definition I am using for AGI:
October 30, 2025 at 5:28 PM
If you have been using the old storyline that OpenAI would declare AGI to void the deal, update your model. The revised terms shift this from a cliff to a controlled process with longer dated IP certainty.
Definition I am using for AGI:
Definition I am using for AGI:
• Strategy is more flexible on both sides. Microsoft can build independently. OpenAI can partner outside some previous constraints while keeping guardrails around core IP
October 30, 2025 at 5:28 PM
• Strategy is more flexible on both sides. Microsoft can build independently. OpenAI can partner outside some previous constraints while keeping guardrails around core IP
• The governance risk is reduced. The decision, and the economic triggers tied to it, move from a unilateral board call to a verification gate
October 30, 2025 at 5:28 PM
• The governance risk is reduced. The decision, and the economic triggers tied to it, move from a unilateral board call to a verification gate
What this means in practice:
• The incentive to declare AGI early is weaker. A declaration alone does not change Microsoft’s commercial rights. Verification is required, and Microsoft’s product runway now stretches to 2032
• The incentive to declare AGI early is weaker. A declaration alone does not change Microsoft’s commercial rights. Verification is required, and Microsoft’s product runway now stretches to 2032
October 30, 2025 at 5:28 PM
What this means in practice:
• The incentive to declare AGI early is weaker. A declaration alone does not change Microsoft’s commercial rights. Verification is required, and Microsoft’s product runway now stretches to 2032
• The incentive to declare AGI early is weaker. A declaration alone does not change Microsoft’s commercial rights. Verification is required, and Microsoft’s product runway now stretches to 2032
• Revenue share continues until AGI is verified by the panel. The arrangement ends once verification occurs
• Other business terms also shifted. Microsoft no longer has cloud right of first refusal. OpenAI committed very large incremental Azure spend that has been widely reported
• Other business terms also shifted. Microsoft no longer has cloud right of first refusal. OpenAI committed very large incremental Azure spend that has been widely reported
October 30, 2025 at 5:28 PM
• Revenue share continues until AGI is verified by the panel. The arrangement ends once verification occurs
• Other business terms also shifted. Microsoft no longer has cloud right of first refusal. OpenAI committed very large incremental Azure spend that has been widely reported
• Other business terms also shifted. Microsoft no longer has cloud right of first refusal. OpenAI committed very large incremental Azure spend that has been widely reported
• Microsoft’s access to OpenAI’s research IP lasts until verified AGI or 2030, whichever comes first
• Microsoft can pursue AGI independently. OpenAI can co‑develop some products with third parties
• Microsoft can pursue AGI independently. OpenAI can co‑develop some products with third parties
October 30, 2025 at 5:28 PM
• Microsoft’s access to OpenAI’s research IP lasts until verified AGI or 2030, whichever comes first
• Microsoft can pursue AGI independently. OpenAI can co‑develop some products with third parties
• Microsoft can pursue AGI independently. OpenAI can co‑develop some products with third parties
• Any AGI declaration by OpenAI now needs verification by an independent expert panel
• Microsoft’s product and model IP rights run through 2032, including post‑AGI models, with safety guardrails
• Microsoft’s product and model IP rights run through 2032, including post‑AGI models, with safety guardrails
October 30, 2025 at 5:28 PM
• Any AGI declaration by OpenAI now needs verification by an independent expert panel
• Microsoft’s product and model IP rights run through 2032, including post‑AGI models, with safety guardrails
• Microsoft’s product and model IP rights run through 2032, including post‑AGI models, with safety guardrails