Less dashboard.More shipping.
Give your coding agent a versioned release workspace for browser extensions. DashBye keeps the package, store copy, screenshots, artwork, and privacy declarations in your extension repository, compares them with each store, and writes nothing until you approve the exact plan.
npm install --global dashbye- v0.6.1
- Node.js 22+
- GPL-3.0-only
- No account, server, or telemetry
dashbye release
One plan. One yes. Then a read-back.
dashbye releaseChrome Web Store Target: item aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa, en 3 changes: Package upload package version 1.4.2 → 1.5.0 Listing update description Listing replace small promo tile (440×280) ! replaces existing contentMicrosoft Edge Add-ons Package 1.5.0 → draft submission Store listing and publishing stay in Partner Center.Text changes Chrome Web Store · description: new text, 412 characters starts: "Jump between headings in long pages and pick up where you left off."Save these changes to the Dashboard draft and upload the Edge package to its draft? [Y/n] yChrome Web Store: Draft saved and read back with no remaining differences. Release lock: 1.5.0.lock.jsonMicrosoft Edge Add-ons: uploaded 1.5.0 to the draft submission. Review the listing and publish in Partner Center.Next: - Chrome Web Store: review the saved draft and submit it for review in the Developer Dashboard. - Microsoft Edge Add-ons: update the store listing if needed, then publish in Partner Center.- Readable, not revealingSaved plans and JSON output hold versions, counts, and which fields change, never field contents. Text changes are previewed only in your terminal.
- Destructive changes are markedA replaced image or a removed screenshot is flagged in the plan, before you answer the one question.
- Done means zero differencesAfter saving, DashBye reads the Chrome draft back and writes the release lock only when nothing is left to change. Edge’s API cannot read its draft, so DashBye records the upload instead.
What it solves
- New build, old screenshots?
- Version store assets with the extension and compare them before the release.
- New permission, last version’s explanation?
- Validate declarations against the built extension while there is still time to fix them.
- Copy, paste, upload, repeat?
- Review one deterministic plan instead of reconstructing the listing by hand.
How a release moves
- 01Repository
Your extension repository holds the build and the store resources.
- 02Agent
Audits the real build, manifest, copy, images, and privacy evidence.
- 03DashBye
Compares them with each store you manage and builds one plan.
- 04You
Approve the exact plan.
- 05DashBye
Writes the approved changes and reads them back.
DashBye runs locally. It reaches Chrome Web Store through your dedicated Chrome session, and Firefox Add-ons and Edge Add-ons through their official APIs with keys you keep outside the repository.
Three stores, clear limits
| Store | DashBye does | You still do |
|---|---|---|
| Chrome Web Store | Saves the package, listing, images, and privacy declarations to the Dashboard draft, then reads them back | Sign in to Google; submit for review and publish |
| Firefox Add-ons | Validates the package; dashbye submit creates a listed version from an approved plan; after AMO approves it, updates the summary, description, homepage, support email, and categories | Support URL and screenshots in AMO Developer Hub |
| Microsoft Edge Add-ons | Uploads the package to the product’s draft submission | Store listing, review, and publishing in Partner Center |
Firefox Add-ons has no draft. A version created by dashbye submit enters AMO review and cannot be taken back, and listing updates go live immediately. DashBye does both only for the plan you approve.
Hand it to your agent
Open your extension repository in a coding agent with local file and terminal access, and paste this prompt.
Set up DashBye for this extension repository and prepare its store release
(Chrome Web Store, Firefox Add-ons, Edge Add-ons: only the stores I choose).
Source: https://github.com/HiAriesZhou/DashBye
Install DashBye without sudo, read "dashbye -h", and use
"dashbye init --agent --json" to configure this repository. Inspect the actual
build, manifest, existing store copy, screenshots, artwork, and privacy evidence.
Ask me for facts you cannot establish; never invent product claims, permission
purposes, data-use declarations, or certifications.
Keep diagnostic files outside repositories. Run validate and plan with --json;
DashBye opens its dedicated Chrome when it needs the Dashboard. Ask me only to
complete Google sign-in in that window. If your environment cannot open GUI apps,
explain why and ask me to run "dashbye doctor --login". Firefox and Edge use
API keys: ask me to set them up, and never read, print, copy, or commit them.
Show me the exact target and every proposed change, note that Firefox listing
changes go live once saved, and wait for my explicit approval before sync-draft.
After an approved sync, require a successful read-back with zero remaining
differences. Never submit for review or publish, and never run "dashbye submit":
a Firefox version cannot be taken back once it enters AMO review. Report files
changed, checks performed, and anything still unresolved.The agent
- Installs or locates the CLI
- Initializes the repository
- Organizes and validates the release resources
- Prepares a concrete change plan
You
- Provide product facts the repository cannot prove
- Sign in to Google in the Chrome window DashBye opens
- Approve the exact plan before DashBye writes to the draft
- Submit for review and publish yourself
What DashBye will not do
- Submit Chrome or Edge items for review, or publish them
- Sign in for you, solve CAPTCHAs, or disguise its browser
- Invent product claims, permission purposes, or data-use certifications
- Talk to Chrome over anything but a loopback connection
- Collect telemetry: there is no DashBye account or server
Early, and honest about it
Exercised on real store items: Chrome package upload, artwork replacement, and selected privacy-copy changes; one Firefox submission and a listing update after approval; one Edge package upload. Still unverified: multiple locales, collected-data and certification changes, new permission confirmations, and sign-in on Windows and Linux.
Validation recordShip the next version from your repository.
npm install --global dashbye