How to use Claude to configure a NixOS workstation
The author used Claude Code to configure NixOS, trialed it on an old laptop, migrated the main workstation and created a consolidated Neovim configuration.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Create a NixOS workstation configuration for [hardware] with [required applications and services]. Include a Neovim configuration with [desired features]. Support testing on [spare machine] before reusing the configuration on [main workstation].
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- linsomniac
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports a fully used NixOS workstation after a week, straightforward setup of the second machine and a consolidated Neovim configuration.
- Human involvement
- The author tested on a spare laptop before migration and reported a week of exclusive workstation use with nothing missing.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Configure NixOS through Claude Code and install it on an old laptop.
- Keep the existing workstation available during the laptop trial.
- Reinstall the main workstation using the NixOS setup.
The author had experimented with NixOS for about two years without reaching a complete workstation setup. Facing an upgrade from Ubuntu 22.04, they decided to configure NixOS entirely through Claude Code before choosing another Ubuntu release. They wanted a reproducible configuration and the ability to boot an earlier setup if something went wrong.
They first installed NixOS on an old laptop while leaving the current workstation available as a fallback. After that trial, they reinstalled the main workstation. The author says the existing NixOS configuration made setting up the second machine trivial. At the time of writing, they had used the workstation exclusively for a week and reported nothing missing.
Claude Code also helped replace their LunarVim and AstroVim setups with a Neovim configuration containing only the features they wanted. The result was a single roughly 700-line neovim.nix file, including LSPs and TreeSitter. The author saw the reusable system configuration as useful protection against future workstation hardware failure. Who it's for: Linux users moving toward reproducible workstation configuration who can trial a setup on spare hardware before migrating their main machine.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · linsomniac
Frequently asked questions
How did the author reduce migration risk?
They installed NixOS on an old laptop first and kept the current workstation intact in case the experiment failed, then reinstalled the main workstation.
What happened to the author's Neovim setup?
Claude Code helped build a setup with the desired features in one roughly 700-line neovim.nix file, including LSPs and TreeSitter.
More details
Remaining steps
- Use Claude Code to build the desired Neovim configuration in neovim.nix.
About this account
Claude Code handled the configuration work, while the author chose the migration sequence and desired editor features.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=48461620. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: linsomniac on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · NixOS · Neovim · Nix
NixOS · Workstation setup · Neovim
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.