A reference to a working handoff.

01 / Install from your Windows terminal

Install Node.js 22.13.0 or newer with npm. Open Downloads in your account and copy the command for the published version. Its HTTPS URL includes the release version and SHA-256, so it identifies one immutable archive.

# Replace the placeholder with the exact URL shown in Downloads
npm.cmd install --global "<immutable release URL from Downloads>"
rebuildo.cmd --version
rebuildo.cmd doctor --json

These Windows commands use the .cmd launchers without changing your PowerShell execution policy. The command remains rebuildo under the Rebuildez brand. Keep it outside your application repository. The archive and npm dependencies are separate downloads; local verification tools are optional. This release is Windows x64 first; Linux and macOS installation has not been qualified for it.

Alternative / Download and install in your user folder

Use the direct archive link and SHA-256 on Downloads. The downloaded filename includes the release version. Replace <version> and the checksum placeholder below with the values shown there. If your browser renamed the file, update its path too. Check the hash before installing. A mismatch means stop and download the published archive again.

$archive = "$env:USERPROFILE\Downloads\rebuildo-client-<version>.tgz"
$expectedSha256 = "<SHA-256 shown in Downloads>"
if ((Get-FileHash -LiteralPath $archive -Algorithm SHA256).Hash.ToLowerInvariant() -ne $expectedSha256) {
  throw "Download checksum mismatch. Do not install this file."
}
$prefix = Join-Path $env:LOCALAPPDATA "Rebuildo Tools"
npm.cmd install --global --prefix $prefix $archive
if ($LASTEXITCODE -ne 0) { throw "Installation failed. Check the npm error before retrying." }
$rebuildoCli = Join-Path $prefix "rebuildo.cmd"
& $rebuildoCli --version
& $rebuildoCli doctor --json
& $rebuildoCli login
& $rebuildoCli setup --project "D:\My App" --agent codex --no-autostart --json

This chooses a folder owned by your Windows account and does not need administrator rights or change your global npm settings. npm still installs the locked dependencies. Keep using & $rebuildoCli in this PowerShell session; in a new session, set that variable to the same full path. Replace the project path with your own folder. Existing application files remain in place.

Optional / Add local verification tools

Cloud extraction and reading saved evidence do not need a local browser. For local visual checks, including PNG comparisons, install Rebuildez's pinned Chromium and Windows monitoring tools. Doctor shows their expected download size before you choose to install them.

rebuildo.cmd doctor --json
rebuildo.cmd tools install verification --json

The tools command verifies downloaded files and uses a per-user cache. It does not silently use your system Chrome or change Windows security settings. If the credential store needs a prerequisite, follow the official guidance reported by doctor before signing in.

02 / Connect your account and project

Rebuildez includes its public service settings. Sign in through your browser, then replace the project path below with your existing folder. Login credentials stay in your operating system credential store.

rebuildo.cmd login
rebuildo.cmd setup --project "D:\My App" --agent codex --no-autostart --dry-run --json
rebuildo.cmd setup --project "D:\My App" --agent codex --no-autostart --json

Reopen that trusted project in Codex after setup. Setup preserves instructions outside its managed sections. The example keeps Figma helper startup off; direct HTML extraction does not need it. Login identifies your account, while the server checks your allowance for every new cloud extraction.

03 / Extract an HTML design

Declare the HTML, its asset root, and every desired viewport. Reference PNGs are optional; a supplied PNG is compared only at matching dimensions. A missing reference is explicitly unverified.

rebuildo.cmd extract --html "D:\Design Files\screen.html" --asset-root "D:\Design Files" --reference "D:\Design Files\desktop.png" --viewport desktop=1600x1280 --viewport mobile=390x844 --project "D:\My App" --json

For multiple screens and per-viewport reference images, use a manifest. Paths inside the manifest are relative to its location.

{
  "viewports": ["desktop=1600x1280", "mobile=390x844"],
  "screens": [{
    "name": "dashboard",
    "html": "./dashboard/index.html",
    "assetRoot": "./dashboard",
    "references": {
      "desktop": "./dashboard/desktop.png",
      "mobile": "./dashboard/mobile.png"
    }
  }]
}

rebuildo.cmd extract --manifest "D:\Design Files\screens.json" --project "D:\My App" --json

Or send complete Figma frames

Rebuildez for Figma is supplied separately during the pilot. In Figma Desktop, import its manifest.json as a development plugin and run it. If you choose this route, enable the local helper with rebuildo.cmd helper start; this also enables Windows login startup. Pair the plugin, select complete layered frames, choose a registered project, and use Send & extract. The plugin shows the destination before sending.

Figma does not export a standard HTML page by itself. Rebuildez preserves the original PNG and native layer data, then creates derived HTML through its converter. Missing fonts, unsupported nodes, or image-only frames remain explicit limitations. A static conversion does not prove Smart Animate fidelity.

If the helper cannot be reached or local-network delivery is blocked, download the capture bundle from the plugin and use rebuildo.cmd figma import --bundle with your selected project.

04 / Use the evidence, then verify

The project's .rebuildo/inbox/ keeps original captures, runs/ keeps immutable evidence, components/ keeps reviewed reuse mappings, and progress/ keeps implementation evidence. Review these files before committing: they can contain private design content.

Ask your agent to inspect every obligation and component occurrence, reuse existing library components with the correct parameters, and record code citations. Once your agent starts the application, invoke Rebuildez verification against its local URL or matching PNGs.

Review differences in one grouped accept / fix / defer decision. Human acceptance stays separate from measured facts. A screenshot alone cannot verify interactions or a native app's component tree.