Forge OS

Portable Control Plane Docs

Install Forge OS on a blank workstation, carry over the hardened operating system, and onboard through a guided setup path instead of memorizing raw commands.

Start Guided Install Browse Commands

Guided Onboarding

Build Your Setup Plan

Fast Path

New Machine Install

git clone https://github.com/leagibson/forge-home.git
cd forge-home
./bin/forge-bootstrap
./bin/forgeos portable-distribution
./bin/forge-login --no-chat

What Travels

Portable By Default

  • Forge OS control plane and daemon
  • Apps under apps/
  • Repo-local skills under .codex/skills/
  • Wrappers, policy, docs, and identity

What Stays Local

Machine-Specific State

  • runtime/
  • projects/registry.json attachments
  • Machine-local secrets and infra bindings

High-Value Commands

Operator Shortcuts

./bin/forge-bootstrap
./bin/forge-bootstrap --install-service
./bin/forgeos portable-distribution
./bin/forgeos promote-skill --skill-name <name>
./bin/forge-login --no-chat
./bin/forgeos skill-catalog
./bin/forgeos background-job-snapshot --lane <lane> --label before-fix --reason "capture state"
./bin/forgeos background-job-fork --lane <lane> --new-lane <fork> --reason "try alternate path"
./bin/forgeos background-job-interrupt --lane <lane> --reason "pause for review"
./bin/forgeos background-job-resume --lane <lane> --reason "continue"
./bin/forge-browser-share
./bin/forge-browser-use --help

SOP

Guided Onboarding Rule

When Forge surfaces a workflow with many configuration options, the operator experience should default to a guided onboarding path rather than a raw list of commands. Documentation should be index-style, operator-first, and capable of producing a tailored setup plan.