Nick Rempel
@nrempel.com
Software engineer @foxglove.dev by day, tinkerer by night, dad 24/7. Token intermediator.
2025: the year of the AI "Agent"
2025: autonomous robots?
2025: autonomous robots?
January 6, 2026 at 7:03 PM
2025: the year of the AI "Agent"
2025: autonomous robots?
2025: autonomous robots?
January 3, 2026 at 5:15 PM
I feel like the Google Pixel is like 90% of the iPhone experience but with generally more freedom and benefits of a more open ecosystem
If Google can close that gap including making some small fundamental changes to Android OS to get there, they will do well.
If Google can close that gap including making some small fundamental changes to Android OS to get there, they will do well.
January 3, 2026 at 3:41 AM
I feel like the Google Pixel is like 90% of the iPhone experience but with generally more freedom and benefits of a more open ecosystem
If Google can close that gap including making some small fundamental changes to Android OS to get there, they will do well.
If Google can close that gap including making some small fundamental changes to Android OS to get there, they will do well.
Thanks @leospalteholz.bsky.social for running House Hunt Victoria and making your data public!
I built a dashboard to visualize the data you made available in the spreadsheet. As you add more rows, it should be reflected automatically in the dashboard.
victoria-real-estate-dashboard.vercel.app/
I built a dashboard to visualize the data you made available in the spreadsheet. As you add more rows, it should be reflected automatically in the dashboard.
victoria-real-estate-dashboard.vercel.app/
December 28, 2025 at 8:34 PM
Thanks @leospalteholz.bsky.social for running House Hunt Victoria and making your data public!
I built a dashboard to visualize the data you made available in the spreadsheet. As you add more rows, it should be reflected automatically in the dashboard.
victoria-real-estate-dashboard.vercel.app/
I built a dashboard to visualize the data you made available in the spreadsheet. As you add more rows, it should be reflected automatically in the dashboard.
victoria-real-estate-dashboard.vercel.app/
I'm not familiar, what's that?
December 27, 2025 at 3:50 PM
I'm not familiar, what's that?
The success of Claude Code is surprising. Why is a TUI so popular? I hear people say it's because users want to feel like a hacker. But what if it's because it removes all the UI chrome and focuses on the conversation? I think it might rather be the beginnings of a new paradigm.
December 27, 2025 at 3:45 PM
The success of Claude Code is surprising. Why is a TUI so popular? I hear people say it's because users want to feel like a hacker. But what if it's because it removes all the UI chrome and focuses on the conversation? I think it might rather be the beginnings of a new paradigm.
I installed Claude Code on my phone
December 22, 2025 at 4:23 PM
I installed Claude Code on my phone
Google just release Gemini 3. It looks fantastic for UI work. But how is it for deeper systems design/architecture work?
What's your experience so far?
What's your experience so far?
November 18, 2025 at 6:27 PM
Google just release Gemini 3. It looks fantastic for UI work. But how is it for deeper systems design/architecture work?
What's your experience so far?
What's your experience so far?
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.
New tool: wt — lightweight Git worktrees
I love Conductor’s “one agent per isolated workspace” idea. It nudged me to run more tasks in parallel. But my day‑to‑day is terminal‑first, and I prefer living in Claude Code and Codex TUIs over a GUI.
I love Conductor’s “one agent per isolated workspace” idea. It nudged me to run more tasks in parallel. But my day‑to‑day is terminal‑first, and I prefer living in Claude Code and Codex TUIs over a GUI.
November 6, 2025 at 5:28 AM
New tool: wt — lightweight Git worktrees
I love Conductor’s “one agent per isolated workspace” idea. It nudged me to run more tasks in parallel. But my day‑to‑day is terminal‑first, and I prefer living in Claude Code and Codex TUIs over a GUI.
I love Conductor’s “one agent per isolated workspace” idea. It nudged me to run more tasks in parallel. But my day‑to‑day is terminal‑first, and I prefer living in Claude Code and Codex TUIs over a GUI.
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).
I've just discovered Conductor (conductor.build/) h/t @hartshorne.ca
This is great. It:
Natively manages git worktrees. You open a new tab, you get a fresh branch to work from without clobbering your work.
Runs in parallel. You can manage as many agents as you want at once.
This is great. It:
Natively manages git worktrees. You open a new tab, you get a fresh branch to work from without clobbering your work.
Runs in parallel. You can manage as many agents as you want at once.
November 3, 2025 at 10:38 PM
I've just discovered Conductor (conductor.build/) h/t @hartshorne.ca
This is great. It:
Natively manages git worktrees. You open a new tab, you get a fresh branch to work from without clobbering your work.
Runs in parallel. You can manage as many agents as you want at once.
This is great. It:
Natively manages git worktrees. You open a new tab, you get a fresh branch to work from without clobbering your work.
Runs in parallel. You can manage as many agents as you want at once.
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)
What if, instead of adding dependencies for most things, we used large language models to generate code instead?
nrempel.com/smaller-sur...
nrempel.com/smaller-sur...
Smaller Surfaces
Modern dependency graphs feel like thickets. Agents make it practical to generate narrow helpers, keep the runtime surface small, and verify the results with the tools you already trust. This essay looks at how to use generation over integration without slipping into wheel reinvention or fragile bespoke stacks.
nrempel.com
November 1, 2025 at 5:49 PM
What if, instead of adding dependencies for most things, we used large language models to generate code instead?
nrempel.com/smaller-sur...
nrempel.com/smaller-sur...