Thanks for your interest in improving Chutes Usage Monitor.
- Node.js 22 or newer
npm- Visual Studio Code
- Install dependencies:
npm install- Build the extension:
npm run compile- Run the test suite:
npm test- Open the repository in VS Code.
- Run
npm installif dependencies are not installed yet. - Press
F5to launch an Extension Development Host window. - In the new window, run
Chutes Usage Monitor: Set API Keyto test the extension manually.
If you are editing both extension-host code and webview assets, run npm run compile again before reloading the Extension Development Host.
- Keep changes focused and minimal.
- Prefer small fixes over broad refactors.
- Add or update tests for parser and state behavior changes.
- Preserve user privacy. Do not log API keys or sensitive account data.
- Use
npmso local development matches the checked-in lockfile and CI workflow. - Update documentation when user-facing behavior changes.
Before opening a pull request:
- Run
npm test. - Run
npm run package. - Update
CHANGELOG.mdwhen the change is user-visible. - Update
README.mdor files indocs/when setup, behavior, or support guidance changes.
If Chutes changes the shape of an endpoint response, include a redacted sample payload in the issue when possible. Remove secrets and personal data, but keep field names and numeric values intact.