Skip to content

Straude for teams

Log the work.
Review the week together.

Give your team one private view of Claude Code and Codex usage. See what changed, understand missing data, and take the same figures into a CSV.

Personal use stays free. Public profiles are optional.

Fictional example · completed week

Harbor Workshop — weekly review

October 19–25, 2026 · Monday–Sunday, UTC. All names and figures in this sample are invented.

People contributing data
8 of 10 members

7 contributed in the previous week.

Estimated value at API prices
$240

+$60 from the previous week’s $180.

Same 7 contributors
+$20

The new contributor accounts for the other $40.

What changed by tool

Claude Code
$120 → $150 (+$30)
Codex
$60 → $90 (+$30)

Model contributions: Claude Sonnet +$30; GPT-5.3-Codex +$30.

How complete is the week?

45 of 56 possible contributor-days received. One connected source has not synced for more than 48 hours. Two members have no data received. Missing days are unknown; a received day with zero tokens is recorded zero usage.

Dollar figures are estimated value at API prices. Actual billed charges are unknown without a billing source. Tokens and spending are usage measures, not employee productivity scores.

Get on the same page

Three steps to a shared week.

  1. 1. Review your own week

    Start with your personal recap, then create a private workspace. Existing personal usage does not move into it.

  2. 2. Invite colleagues deliberately

    Create invitation links for specific email addresses. Each person reviews what will be shared and connects a work-only device or operating-system account. Collection starts the next UTC day.

  3. 3. Confirm sync, then review together

    Use the Straude CLI to sync Claude Code and Codex. Check who has joined, whose first sync arrived, and when data was last received. Review weekly totals, changes in participation, tools, models, and gaps; export the same report as CSV.

A private workspace with clear boundaries.

Members see combined usage reports, the roster, and source sync status. The owner manages invitations and access. Prompts and code are not uploaded. Workspace contributions stay off public feeds, profiles, recaps, and leaderboards.

Daily aggregates cannot distinguish work and personal accounts on a mixed device. Connect only a work-only device or OS account. Earlier dates are excluded even on retries. Removing someone stops access and future sharing; their prior contributions remain in the totals.

Bring a clear proposal.

Copy this note to start a conversation with your team.

Proposal: a private weekly usage review

Let’s try a private Straude workspace for our team’s Claude Code and Codex usage. Each engineer chooses a work-only source. We’ll review the weekly tool and model mix, compare changes without confusing new contributors with changed behavior, and check gaps before exporting the figures.

We will use the report to understand usage, not rank employee productivity. It contains no prompts or code, and estimated API value is separate from actual bills. After a few weekly reviews, we can decide whether it saves enough reporting work to continue.

Discuss team setup with Straude · Read the CLI guide