Connect Your Services

Before Mosayic can scaffold your project, it needs to be able to talk to three external accounts on your behalf:

• GitHub — to create your two private repos and push code to them
• Google Cloud — to deploy your API and store your secrets
• Expo — to build your mobile app via EAS (Expo Application Services)

This step requires the VS Code extension to be installed and connected, because every login command runs in your local terminal — not on Mosayic’s servers.

How each connection works

Mosayic does not collect your passwords. Each service uses its own official sign-in flow:

Service	Mechanism	What runs
GitHub	Browser-based device flow	gh auth login --web
Google Cloud	Browser OAuth	gcloud auth login
Expo	Username/password (Expo’s accounts don’t have OAuth)	eas login (entered in your terminal)

The credentials end up in the standard config files that each CLI uses (~/.config/gh/, ~/.config/gcloud/, ~/.expo/). Mosayic doesn’t read or store them — it just knows whether you’re logged in by running each tool’s status check (gh auth status, gcloud auth list, eas whoami).

Caution

If you don’t already have these CLIs installed, the dashboard will tell you. The next step (Set Up Your Machine) covers installation, but you can also install them now using each project’s official docs:

• GitHub CLI — cli.github.com
• Google Cloud CLI — cloud.google.com/sdk/docs/install
• Expo / EAS CLI — npm install -g eas-cli

GitHub

1. Click Connect GitHub in the dashboard.

2. The dashboard tells the extension to run gh auth login --web. Your browser opens a GitHub device-flow page with a one-time code.

3. Enter the code, choose the account, grant the requested permissions (repo, workflow, admin:public_key).

4. The extension waits for the CLI to confirm success, then reports back. The dashboard shows a green “Connected” badge.

The permissions are needed because Mosayic will:

• Create private repos on your behalf (repo)
• Set up GitHub Actions for CI/CD (workflow)
• Register an SSH key so your machine can push without typing a password (admin:public_key)

Google Cloud

1. Click Connect Google Cloud.

2. The extension runs gcloud auth login. Your browser opens a Google consent screen.

3. Sign in with the Google account you want to use for hosting your API and storing secrets. You can use a different account from the one you signed in to Mosayic with if you’d prefer to keep work and personal accounts separated.

4. Once the consent flow finishes, the dashboard shows “Connected”.

You don’t need to create a Google Cloud project yet — the Configure Your Project step handles that. You just need to be logged in.

Note

Billing. You’ll be prompted to set up a Google Cloud billing account before you can deploy your API. The free tier is generous — Mosayic’s typical workload runs at a few cents per month — but a billing account is required even when you’re inside the free tier. New Google Cloud accounts get $300 of free credit for the first 90 days.

Expo

1. Click Connect Expo.

2. The dashboard prompts you for your Expo email and password (or asks you to sign up at expo.dev if you don’t have an account). Expo doesn’t support OAuth for the CLI, so this is the one place you’ll enter a password.

3. The extension runs eas login and pipes your credentials to it. The credentials never leave your machine — they go straight from the dashboard to your terminal via the WebSocket relay.

4. Once eas whoami confirms success, the dashboard shows “Connected”.

Expo’s free tier lets you run a limited number of EAS builds per month. For most solo projects, this is enough. If you start hitting the limit, EAS plans start around $19/month.

What this step unlocks

Once all three are green, the Continue button activates and the guide moves on to Installing the VS Code Extension. (If you’re reading along: yes, you needed the extension already to do this step. The dashboard treats this step’s gating leniently — you can skip ahead to install the extension, then come back here.)