Skip to content
Gambi

Migrate from Gambiarra

The project is now called Gambi. This guide covers everything you need to update.

What Changed

Section titled “What Changed”
BeforeAfter
gambiarragambi
gambiarra-sdkgambi-sdk
createGambiarra()createGambi()
~/.gambiarra~/.gambi
gambiarra-hub / _gambiarragambi-hub / _gambi

Gambi is the official abbreviation of gambiarra. For the naming background, read Why Gambi?.

Fastest Migration

Section titled “Fastest Migration”

Run the automated script for your platform:

Terminal window
curl -fsSL https://raw.githubusercontent.com/arthurbm/gambi/main/scripts/migrate-from-gambiarra.sh | bash

Manual CLI Migration

Section titled “Manual CLI Migration”
Terminal window
npm uninstall -g gambiarra
npm install -g gambi

The new gambi package installs a wrapper plus the matching platform binary for the current machine.

SDK Migration

Section titled “SDK Migration”

Replace imports and provider names:

import { createGambi } from "gambi-sdk";


const gambi = createGambi({
  roomCode: "ABC123",
});

What changed:

  • gambiarra-sdk → gambi-sdk
  • createGambiarra → createGambi
  • Gambiarra* types → Gambi* types
  • response metadata key gambiarra → gambi

Local Config Migration

Section titled “Local Config Migration”

The CLI and TUI now use:

~/.gambi/config.json

If you already have ~/.gambiarra/config.json, the migration script copies it into the new location when possible.

Service and Network Names

Section titled “Service and Network Names”

If you run Gambi as a service or rely on discovery, update these names too:

BeforeAfter
gambiarra-hub.servicegambi-hub.service
_gambiarra._tcp.local_gambi._tcp.local
gambiarra-hub-{port}gambi-hub-{port}

Verify

Section titled “Verify”
Terminal window
gambi --version
gambi --help

If you use the SDK, also update your app imports and run your normal build or typecheck.

Next Steps

Section titled “Next Steps”