Service Connections

The Service Connections screen is where you check (and re-establish) the links between Mosayic and your three external accounts:

• GitHub — your code lives there
• Google Cloud — your deployed API lives there, and so does your Secret Manager
• Expo — builds your mobile app

Each service shows up as a card with a status badge:

Badge	Meaning
✅ Connected	The CLI for this service is logged in, on your machine
⏳ Checking…	The dashboard is currently probing the extension
⚠️ Idle	Status hasn’t been checked recently — click to refresh
❌ Error	The CLI is missing, or you’re signed out

Status is determined by running each service’s own status command via the extension:

Service	Status check
GitHub	gh auth status
Google Cloud	gcloud auth list
Expo	eas whoami

If any of these fail, the dashboard shows you the actual command output so you can debug.

Re-connecting

Click any service card to open its detail screen. From there you can:

• See your current login (e.g. the GitHub username, the Google account email)
• Click Reconnect to run the login flow again
• Click Sign out to clear the local CLI’s auth (rare — only useful if you want to switch accounts)

Switching accounts

If you want to use a different GitHub account (e.g. for a personal project vs a work one), you can:

1. Run gh auth logout in your terminal
2. Click Reconnect on the GitHub card
3. Sign in with the other account

The new authentication only affects future commands; existing repos are not moved or re-permissioned.

For Google Cloud, you can have multiple accounts logged in simultaneously and switch between them with gcloud config set account <email>. Mosayic uses whichever one is active.

For Expo, you can only be logged in to one account at a time. Use eas logout then Reconnect.

Where these credentials are stored

Mosayic doesn’t store any of these credentials. They live in the standard config locations:

Service	Stored in
GitHub	~/.config/gh/hosts.yml
Google Cloud	~/.config/gcloud/
Expo	~/.expo/state.json

The Mosayic dashboard only ever sees the result of gh auth status etc — never the underlying token.

Note

The same credentials are used outside of Mosayic, by your terminal, your CI scripts, anything else. If you’d already been using these CLIs before installing Mosayic, your existing logins were picked up automatically — you didn’t need to re-authenticate.