Hello, Cursor.
Three simple ways to make every accepted suggestion accountable.
You ship the most-used coding agent in the world. Every accept, every cmd-K, every Cloud Agent run carries a real per-token carbon and water cost. We've built the meter for it. This page is three concrete shapes a partnership could take. Pick the one that fits your roadmap.
No regulatory pressure, no doomy chart deck. Just three examples of what an integration could look like, with mockups you can show internally.
A “Connect Cursor” button, on both sides.
Integrations
Connect external tools to extend your team's workflow.
Source Control
Connected as jakehandy to repositories in organizations: cmac13, jakehandy, rvsrvs
Connect GitLab for Cloud Agents, Bugbot and enhanced codebase context
Integrations
Meter Cursor token usage, price its environmental footprint, and route the offset to a climate fund of your choice.
Work with Cloud Agents from Slack
Work with Cloud Agents from Microsoft Teams
Connected: once
Connect a Jira site to delegate issues to Cloud Agents
A “Connect Cursor” button, on both sides.
Inside Token Offset, a user clicks a single Connect Cursor button. That's the entire surface. It hands them off to your existing OAuth-style integrations flow, where Token Offset sits as a first-class option alongside Slack, Linear, and Jira. From there, anyone who lives in the Cursor dashboard can connect their account to Token Offset without ever leaving cursor.com. Usage flows to us; offsets and a per-developer footprint dashboard flow back into Token Offset.
- One button on our side. One row on yours.
- OAuth-style, read-only token-usage scope. No code touches your billing.
- Token Offset surfaces a per-developer impact dashboard; nothing rendered inside Cursor.
A Token Offset toggle, native to your subscription.
Subscribe to Pro
Unlimited completions and Cloud Agents for one developer.
Adds 100% coverage for a typical Pro seat (~15M tokens / month).
≈ 9 kg CO₂e · routed to vetted projects
Add Token Offset to make your usage carbon-accounted.
A Token Offset toggle, native to your subscription.
When a developer subscribes to (or renews) Cursor Pro, a single Token-Offset-branded switch lets them pay the average environmental cost of a Pro seat in the same invoice. No second checkout, no third-party redirect. Toggle off and the price is unchanged; toggle on and a small line item routes monthly to the climate destination of record. Zero churn risk: purely additive, framed as a developer benefit.
- One toggle, added to the existing Pro / Business checkout.
- Default-off; visibly priced; obvious upgrade path for teams.
- Funds route through Token Offset to durable removal, watershed/grid work, verification, and open methodology research.
Cursor, the company, offsets its own developers.
Cursor, the company, offsets its own developers.
Cursor signs up to Token Offset as an organization and pays the per-token environmental cost of every internal seat, every Cloud Agent run, every shipped product build. The same way ONCE already does for its team. An org dashboard rolls up usage and footprint across every developer, every project, every model, and routes a single monthly offset payment to the climate destination of record. No per-developer billing, no procurement friction.
- One org account. One monthly invoice. All Cursor employees covered.
- Roll-up dashboard: tokens, energy, water, carbon, by team and project.
- Quarterly attestations sized to SOC 2, CDP, and SB 253 disclosure packs.
Let's pick the one that fits.
Any of the three ships in weeks, not quarters. We're happy to start with whichever needs less of your engineering time, or to demo all three against a sandbox Cursor account. Reach out and we'll send a one-page spec for whichever shape interests you.
partnerships@tokenoffset.comReplies within one business day.