SuperPenguin Docs
Company Setup

Set up AI Coding and PR Costs

Understand the shared team setup, optional provider connections, and the extra GitHub step for pull-request attribution.

AI Coding and PR Costs share one team-onboarding flow, but they do not have identical requirements.

Requirements at a glance

AI Coding

The organization dashboard requires:

  1. A Pro workspace, or an Enterprise workspace with the AI Coding entitlement enabled.
  2. Engineers invited to the company workspace.
  3. SuperPenguin Desktop connected by the engineers whose activity should appear.

GitHub is not required for AI Coding. Cursor, Anthropic, and OpenAI billing connections are also optional.

PR Costs

PR Costs requires everything above, plus a GitHub connection. GitHub supplies repository, commit, and pull-request data so SuperPenguin can match Desktop activity to pull requests.

What the setup checklist shows

The AI Coding and PR Costs pages use live workspace status:

  1. Use Pro or Enterprise confirms the workspace entitlement.
  2. Connect Cursor billing is optional. It adds provider-billed Cursor dollars and enables Cursor-specific dashboard information.
  3. Onboard your team shows how many engineers were invited, accepted, and connected to Desktop. Owners can email the app to accepted engineers who have not connected it.
  4. Connect GitHub appears only on PR Costs.

The AI Coding checklist disappears after the plan and Desktop requirements are complete. If Cursor remains disconnected, a smaller optional Cursor connection prompt appears in the completed dashboard instead.

Provider connections

  • Cursor billing: Optional. Connect a Cursor Admin API key to add provider-billed Cursor costs and Cursor-specific reporting.
  • Anthropic billing: Not required. Claude Code activity comes from SuperPenguin Desktop.
  • OpenAI billing: Not required. Codex activity comes from SuperPenguin Desktop.
  • GitHub: Required only for PR Costs.

The provider billing connections can still be useful elsewhere in SuperPenguin for reconciliation and organization-wide provider spend. They are not prerequisites for Claude Code or Codex AI Coding reporting.

Team coverage

The checklist can become ready after the workspace has its first supported Desktop reporting signal. For complete team coverage, every participating engineer should:

  1. Accept the company workspace invitation.
  2. Install SuperPenguin Desktop on macOS 12 or later.
  3. Sign in and select the company workspace.
  4. Use Cursor, Claude Code, or Codex normally.

Workspace owners can send Desktop download emails directly from the setup checklist. Invitations and the full installation roster remain available in Settings.

Visibility

Ordinary members see their own AI Coding information. Workspace owners, Viewers, and Policy administrators can see organization-wide AI Coding information when the workspace is entitled.

See Workspace roles and AI Coding visibility for the complete access model.