agentconfig.ing
Amp vs Firebase StudioUpdated 2026-03-16

SUMMARY

Amp (CLI) uses markdown configuration while Firebase Studio (Platform) uses text. They differ on 6 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

FeatureAmpFirebase Studio
Config formatmarkdowntext
Hierarchy support✓✗
Global config✓✗
Project config✓✓
Subdirectory scoping✓✗
File inclusion / imports✗✗
Ignore file✗✗
IDE integrationCLIPlatform
Schema / structureFree-form (Markdown)unknown
Git committed✓✓
EncodingUTF-8UTF-8

FILE MAPPING

PurposeAmpFirebase Studio
Settings / configurationsettings.json.idx/dev.nix

KEY DIFFERENCES

1. Config format

Amp: markdown. Firebase Studio: text.

2. Hierarchy support

Amp: Supported. Firebase Studio: Not supported.

3. Global config

Amp: Supported. Firebase Studio: Not supported.

4. Subdirectory scoping

Amp: Supported. Firebase Studio: Not supported.

5. IDE integration

Amp: CLI. Firebase Studio: Platform.

6. Schema / structure

Amp: Free-form (Markdown). Firebase Studio: unknown.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Amp, configure AGENTS.md. If you use Firebase Studio, configure .idx/dev.nix. Many projects include config files for multiple tools so each team member can use their preferred editor.

PORTABILITY TIP

sync-instructions.sh
bash
# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md

SEE ALSO

File references:
AGENTS.md
agentconfig.ing2026-03-16COMPARE(1)