An early version, being tested

Build real software with Claude.

Railset guides you from your idea to software that works, step by step, the way the best teams build it. You don't need to know how to code.

curl -fsSL https://github.com/railset/cli/releases/latest/download/install.sh | sh

One line, pasted into Terminal on your Mac. Setup takes it from there, in about 15 minutes.

Railset works on Macs for now, with macOS 13 or newer, and this computer isn't one. Come back on a Mac when you can.

Open this on your Mac

Railset runs on a Mac, so that's where you set it up. In a browser on your Mac, go to:

railset.app
  1. 1Open TerminalPress Command and Space, type Terminal and press Return. It's an app your Mac already has.
  2. 2Paste the linePress Command and V, then Return.
  3. 3Setup takes overIt makes a folder for your idea, connects GitHub and opens Claude there.

If Terminal says it couldn't connect, check your connection and paste the line again.

What to have ready

  • A MacWith macOS 13 or newer.
  • ClaudeThe Claude app and a paid Claude plan.
  • A GitHub accountIt's free, and you can make one during setup, in about 10 minutes.
What Railset shares, and how to stop it

Setup asks you first, and no answer means no. With your yes, Railset sends usage data to PostHog, in Europe, so I can find and fix problems: which steps ran on your Mac, how long they took and what, if anything, went wrong. It's sent under a random code for your Mac, and a yes includes what Railset recorded before you answered. It never includes your code, your files or their names, what you type, or your name or email. Each send shows PostHog your Mac's internet address as it arrives, and it keeps none. PostHog keeps the rest for up to seven years, unless you ask me to delete it sooner.

The full list: which command or setup step ran, when, how long it took, how it ended and the kind of failure from Railset's own list; which of Railset's files Claude read; which agent started it; which step of getting started was under way; the kind of computer and its chip; Railset's version and the short id of the save a release was built from; whether the run had a terminal, ran in CI or was a test build; a number for each run; and Railset's housekeeping, such as how far a send got. If you send a problem report, it also holds the last day of this, and the words you wrote.

To stop, type railset data-sharing off in Terminal, or ask Claude to. Data already sent can't be taken back from your side, so to have it deleted, send me what this line prints: grep ^computer ~/.railset/settings.toml