Computer

One command,
ready to build.

This is how we set up a Mac at Kuberdon. A new laptop runs one command and ends up with the apps we work in, the tools we build with, and a few settings that get out of the way. It is open, so you can read every line, or make it yours.

Terminal
$ git clone https://github.com/kuberdonhq/computer.git ~/Developer/computer$ cd ~/Developer/computer$ ./computer
Read the code on GitHubGet the wallpapers

What we work in,
and why.

Apps

  • 1PasswordEvery password, SSH key and secret. Nothing secret lives in a file.
  • ClaudeThinking, writing and building, in the app and in the terminal.
  • ConductorSeveral Claude Code sessions side by side, each in its own worktree.
  • NotionNotes, plans and docs.
  • LinearWhat we are building, and who is on it.
  • SuperhumanEmail, for everyone.
  • RectangleWindows to halves and thirds from the keyboard.
  • XcodeOur apps are made for iPhone first. Installed through Xcodes.

The tools
we build with.

Command line

  • git
  • gh
  • mise
  • Node
  • pnpm
  • Watchman
  • CocoaPods
  • fastlane
  • Maestro
  • Supabase CLI
  • Docker
  • VS Code
  • jq
  • ImageMagick

All from one Brewfile. Add a line, run Computer again, and every Mac gets it.

Three rules
it never breaks.

How it works

  1. 01

    Secrets stay in 1Password.

    SSH keys live in 1Password and its agent signs every commit. No private key sits on the disk, and no secret goes in a file.

  2. 02

    Run it twice, nothing changes.

    Every step checks first. Run it on a new Mac or a year-old one: it adds what is missing and leaves the rest alone.

  3. 03

    You sign in yourself.

    Computer never touches a password. At the end it opens 1Password, then each app, for you to sign in.

Make it yours.

Fork it, or keep your own extras in ~/.computer.local. Computer runs that file last. Inspired by thoughtbot’s laptop.

kuberdonhq/computer