Skip to main content

Windsurf Credit Throttle

A Streamlit application for managing Windsurf add-on credit caps.

Features

  • Verify Credit Caps: Check team-level and individual user credit configurations
  • Set Team Cap: Configure organization-wide add-on credit limits
  • Set Individual Caps: Set custom caps for specific users or bulk import from CSV

Installation

Using uvx (recommended)

# Run directly from GitHub
uvx --from git+https://github.com/rappdw/windsurf-throttle windsurf-throttle

# Or from PyPI (when published)
uvx windsurf-throttle

Using pip

pip install windsurf-throttle
windsurf-throttle

From source

git clone https://github.com/rappdw/windsurf-throttle.git
cd windsurf-throttle
uv sync
uv run windsurf-throttle

Configuration

Set your Windsurf service key as an environment variable:

export WINDSURF_SERVICE_KEY=your_service_key_here

Or create a .env file in your working directory:

WINDSURF_SERVICE_KEY=your_service_key_here

Optional Configuration

# Override the API base URL (default: https://server.codeium.com)
export WINDSURF_BASE_URL=https://custom.server.com

Usage

Running the App

# Using the CLI
windsurf-throttle

# Or run Streamlit directly
streamlit run src/windsurf_throttle/app.py

Credit Cap Strategy

The app implements the following strategy:

  1. Base Credits: Each user gets 500 base credits
  2. Organization Cap: Set a default add-on cap for all users (e.g., 1000)
  3. Individual Caps: For high-usage users, set individual caps = current add-on usage + buffer

Example:

  • User with 1200 total credits used → 700 add-on credits used
  • Individual cap = 700 + 500 buffer = 1200 add-on credits
  • Total available = 500 base + 1200 add-on = 1700 credits

Bulk CSV Import

Upload a CSV with these columns:

  • email (required): User email address
  • credits_used (required): Current total credit usage
  • name (optional): User display name

Development

# Clone and install dev dependencies
git clone https://github.com/rappdw/windsurf-throttle.git
cd windsurf-throttle
uv sync --all-extras

# Run tests
uv run pytest

# Run linting
uv run ruff check src tests
uv run mypy src

# Install pre-commit hooks
uv run pre-commit install

License

MIT

Release files for windsurf-throttle 1.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for windsurf-throttle 1.2.0
File Size Uploaded
windsurf_throttle-1.2.0.tar.gz 112.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for windsurf-throttle 1.2.0
File Interpreter ABI Platform
windsurf_throttle-1.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 126.1 kB

Release files / windsurf_throttle-1.2.0.tar.gz

Download URL windsurf_throttle-1.2.0.tar.gz
Size 112.6 kB
Tags Source
SHA-256 checksum
How to use checksums
993a95cbe6b87431ec32e6bf2f19007955c864276dfb1901a4d6bcd1bbb9c612
BLAKE2b-256 checksum
How to use checksums
9739d62b2269f832406350a6a04b871bd33badf413393bc235c3ddef7cf82804
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 10, 2026.

Transparency log

Release files / windsurf_throttle-1.2.0-py3-none-any.whl

Download URL windsurf_throttle-1.2.0-py3-none-any.whl
Size 13.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fb24a04a544505e4a75b3c95427c61032847b1b9e179071e87eacf7da7a42aa1
BLAKE2b-256 checksum
How to use checksums
5b78fabff77ee7503f34353855454a34367f6dac09952f76878124fbea262101
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 10, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.2.0 This release

2 release files

1.0.3

2 release files

1.0.2

2 release files

1.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page