No VS Code extension for OMP customization

Difficulty adding custom providers to Oh My Posh (OMP) in VS Code requires manual editing of 2 files instead of a simple command or GUI, despite the tool having many settings.

XToolDevSource
0Sign in to voteCopy link

FL score

42

out of 100

Verdict

SKIP

medium confidence

Competition

No competitor data yet

Trend

No signal yet

A VS Code extension that replaces manual JSON editing with a GUI for configuring Oh My Posh custom providers.

The pain

Developers using Oh My Posh want to add custom providers but must manually edit two separate configuration files. This requires knowing the exact file locations, JSON structure, and provider syntax. Users make mistakes, lose time switching between files, and abandon customization attempts.

The gap

Oh My Posh has extensive settings but no integrated configuration UI in VS Code. The extension ecosystem has theme builders and settings managers for other tools, but nothing for OMP's provider system.

Build angle

Start with a form-based UI that maps to the two required files. Let users add providers through dropdowns and text inputs, then auto-generate and save the JSON. Validate syntax before writing. Track which providers users add most to identify patterns.

Strengths

  • Solves a real friction point in an existing workflow
  • Clear technical scope, two files with defined structure
  • OMP is actively maintained and has a growing user base
  • VS Code extension distribution is straightforward

Risks

  • Market size is small, OMP users are a subset of terminal customizers, and not all customize providers
  • OMP updates could change file structure, requiring maintenance
  • Users who need custom providers are often comfortable with JSON editing
  • No clear monetization path for a free extension
  • Competing with OMP's own documentation and community solutions

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “No VS Code extension for OMP customization”.

Open FlyBot