ChromeShip Studio

The Studio keeps the entire extension workflow visible: projects, runtimes, logs, backend, configuration, and production builds.

Projects

Create, import, search, and open projects from one workspace. Each project keeps its own code, configuration, Chromium profile, and local backend data.

Overview

Start or stop managed Chromium and, when Supabase is enabled, the local backend. Starting a runtime takes you directly to its live startup logs.

Logs

Read build output, runtime events, function output, and console logs from every extension surface. Filter by source or level instead of opening several DevTools windows.

Build

Choose a valid extension version and create a store-ready ZIP. ChromeShip validates the Manifest V3 output and keeps one artifact per version.

Functions

Create functions, run them locally, inspect their logs, and expose webhooks through ngrok. With the backend running, Open Supabase Studio gives you a visual interface for the local database; Deploy database applies its versioned schema changes to your remote Supabase project.

Integrations

Enable Supabase, Stripe, or AI when the project needs them. ChromeShip adds the matching helpers and backend functions while keeping secret values out of the extension bundle.

Auth

Configure email/password auth and OAuth providers without guessing redirect URLs. Local and production values stay separate.

Localization

Add locales, organize keys into groups, and edit translations in a table. English is the fallback. Chrome Web Store _locales output is automatic.

Settings

Update project identity, surfaces, Chrome permissions, host access, and environment values. ChromeShip validates changes before synchronizing the generated project.

Launch the Studio

Run:

chromeship dev

The Studio opens at http://127.0.0.1:43111. Use --port when you need a different Core API port; the Studio follows on the next port.