Extensions & SDKs

Install Spendplane where work already happens. Keep the boundary in place.

Use Spendplane from your editor, browser, desktop app, or SDK without rebuilding your workflow. Keep requests OpenAI-compatible while adding sign-in, routing, redaction, and budget policy in the same path.

Download View docs

Installed surfaces

Install surfaces available today.

The VSIX, browser package, desktop app, and `/v1` endpoint are the real integration surfaces available now. Additional environment-specific installs build on the same governed boundary.

VS Code and VSIX-compatible editors

Available

Shipped

Install the VSIX and bring Spendplane sign-in, planning, and synced project capture into VS Code, Cursor, and compatible editors.

VSIXProject syncWorkspace sign-in

Chrome extension

Available

Browser capture

Capture ideas and browser context, sync them into Spendplane, and use the extension package today while the public Chrome Web Store listing is finalized.

MV3 packageZIP installBrowser sync

Windows desktop app

Available

Standalone runtime

Use Spendplane Vault for desktop sign-in, local runtime controls, hardware visibility, and a dedicated workspace surface on Windows.

x64Desktop sign-inLocal runtime

OpenAI-compatible clients

Universal

Universal path

Any tool that supports an OpenAI-style base URL can route through Spendplane with the same policy and budget boundary.

/v1SDK overrideAgents

JetBrains and custom editor setups

Compatible

Compatible now

Where a dedicated extension is not shipped yet, the same route still works through endpoint overrides, proxy settings, and the shared `/v1` contract.

Base URLProxyShared policies

JetBrains, Windsurf, Neovim

Planned

Rolling out

Dedicated setup guides and install surfaces for more coding environments are next, but they all use the same governed endpoint and auth model.

Editor rolloutSame endpointSame auth

Chrome and Google path

Chrome needs a real Google distribution path.

The Chrome extension package already exists as a Manifest V3 build. Public installation goes through Chrome Web Store publishing and review, while beta and managed installs can use the packaged ZIP directly.

MV3 package exists

Spendplane already has a real Manifest V3 extension package with popup, service worker, storage, and sync behavior.

ZIP for beta and managed installs

Teams can load the packaged extension today for testing, internal rollout, or managed browser environments.

Chrome Web Store for public install

Public distribution should move through the Chrome Web Store once the store listing and Google review path are finalized.

Universal endpoint

A drop-in `/v1` interface.

OpenAI-compatible request shapes

Keep your current SDK calls and payload format. Swap the host, keep the contract.

One identity across app, editor, and browser

Keep the same workspace, policy, and routing boundary whether the request starts in the desktop app, a VSIX surface, or a browser package.

Policy headers + budgets

Enforce cost and data rules at the perimeter so enforcement is consistent across teams, tools, and extension surfaces.

SDKs

Keep your existing client. Change the base URL.

Node.js / TypeScript

npm install openai

import OpenAI from "openai"

const client = new OpenAI({
  apiKey: process.env.SPENDPLANE_KEY,
  baseURL: "https://spendplane.com/api/proxy/v1",
})

const res = await client.chat.completions.create({
  model: "gpt-4o-mini",
  messages: [{ role: "user", content: prompt }],
})

Python

pip install openai

from openai import OpenAI

client = OpenAI(
  api_key=os.environ["SPENDPLANE_KEY"],
  base_url="https://spendplane.com/api/proxy/v1",
)

response = client.chat.completions.create(
  model="gpt-4o-mini",
  messages=[{"role": "user", "content": prompt}],
)

Setup path

From install to routed traffic in minutes.

Install the right surface

Use the VSIX, browser package, desktop app, or base URL override that matches how the team actually works.

Sign in once

Reuse the same Spendplane workspace identity across extensions, desktop, and direct client traffic.

Point traffic through Spendplane

Set the OpenAI-compatible base URL or use the packaged extension surface where routing is already wired in.

Verify decisions and costs

Check routing, redaction, captured projects, and spend in the same control plane.

Keep the integration simple. Make the boundary real.

Add Spendplane where you already work and enforce policy at egress without changing how builders build.

Download Docs