JanDeDobbeleer/oh-my-posh · warning

NO ACTIVE CONFIG FOUND

Error message

NO ACTIVE CONFIG FOUND

What it means

The firebase segment reads the Firebase CLI's active project from ~/.config/configstore/firebase-tools.json. If that file is missing or empty, getActiveConfig() returns the FIREBASENOACTIVECONFIG error ('NO ACTIVE CONFIG FOUND'), and the segment disables itself.

Source

Thrown at src/segments/firebase.go:63

	// of the path to the project and the project name

	// Test if the current directory is a project path
	// and if it is, return the project name
	for key, value := range data.ActiveProject {
		if strings.HasPrefix(f.env.Pwd(), key) {
			f.Project = value
			return true
		}
	}

	return false
}

func (f *Firebase) getActiveConfig(cfgDir string) (string, error) {
	activeConfigFile := filepath.Join(cfgDir, "firebase-tools.json")
	activeConfigData := f.env.FileContent(activeConfigFile)
	if activeConfigData == "" {
		return "", errors.New(FIREBASENOACTIVECONFIG)
	}
	return activeConfigData, nil
}

func (f *Firebase) getFirebaseData(configFile string) (*FirebaseData, error) {
	var data FirebaseData

	err := json.Unmarshal([]byte(configFile), &data)
	if err != nil {
		return nil, err
	}

	return &data, nil
}

View on GitHub (pinned to 0976794618)

Solutions

1. Run `firebase use --add` (or `firebase use <project>`) in a Firebase project to create the active config.
2. Log in with `firebase login` first if the configstore doesn't exist at all.
3. Disable the firebase segment in your theme if you don't work with Firebase in that shell.

test -s ~/.config/configstore/firebase-tools.json && echo ok || echo 'run: firebase use <project>'

When it happens

Trigger: Enabled() runs while firebase-tools.json does not exist or contains nothing — Firebase CLI installed but `firebase use` never run, or a non-default config directory passed in.

Common situations: Fresh machine where firebase-tools was installed but no project selected; projects without .firebaserc; running inside a container where the Firebase CLI config was never created.

Related errors

• NO ACTIVE CONFIG FOUND
• invalid yaml
• no current context
• azure config dir not found

AI-assisted analysis of JanDeDobbeleer/oh-my-posh@0976794618 (2026-08-31). Data as JSON: /api/errors/9576b4a55c5923e3. Report an issue: GitHub.