rebase setup
Authenticate and select a workspace.
Synopsis
rebase setup
rebase setup --profile <profile>
rebase setup --api-url http://127.0.0.1:8080
rebase setup --provider googleArguments
| Argument | Type | Description |
|---|---|---|
--profile | str | Named local credential profile. |
--api-url | str | Rebase API URL to store for this profile. Use this for local development with a port-forwarded API. |
--provider | google or github | Supabase social auth provider to use during sign-in. |
--force-auth | bool | Ignore any stored Supabase session and authenticate again. |
--callback-port, -c | int | Local Supabase OAuth callback port. Defaults to 17658. |
--auth-timeout | float | Seconds to wait for the Supabase auth callback. Defaults to 300. |
--no-browser | bool | Print auth URLs instead of opening a browser. |
--workspace | str | Workspace ID to use or create. |
--workspace-name | str | Display name when creating a workspace. |
--handle | str | Rebase user handle to claim during setup. |
Flow
The setup wizard has two main steps:
| Step | What happens |
|---|---|
| Authenticate | Sign in with Google or GitHub and store a local auth session. |
| Workspace | Select or create a workspace and store it in the local profile. |
GitHub source backing is configured separately with rebase connect github.
Workspace Resolution
Commands resolve which workspace to address in this order: an explicit
Client(workspace_id=...), then the REBASE_WORKSPACE environment variable (which the
global rebase --workspace/-W option sets), then a checked-in .rebase/config.json
repository marker
found in the working directory or a parent, then the profile written by rebase setup.
Inside a marked repository, the marker wins over the globally active profile.

