Hosted · /team

Team home

The same cockpit, rolled up across your team. Once you've bound at least one desktop via the linking-code flow, repoops.ai/teamshows every connected developer, their live status, the team-wide spend, and the policy you've pinned for every bound device.

See it in motion

Where to find it

  • Hosted: https://repoops.ai/team (manager/admin only).
  • Sign in: Google OAuth + a team license. The first manager creates the team; invite teammates from this page.
  • Localhost echo: The bound desktop's Settings → Connect to team mirrors the binding state shown here.
  • Linking-code flow: Generate a one-time code here; paste into the desktop's Settings → Connect to team.

What it does for you

One view of every bound developer.Live / stale / revoked status per device, last-seen timestamps, the repos each device tracks. Reconciles what's actually streaming telemetry vs. what claims to be bound.
Server-owned policy, pinned everywhere.Set the capture-mode floor (metadata-only vs. content-redacted) and the sensitive-path watchlist here; every bound desktop applies it on the next tick. Tighten-only.
Budget alerts that fire once per period.Slack webhook + email when a per-tenant or per-team budget crosses its threshold. One notification per breach, never a flood.

Configure

Three things to set up after first sign-in:

  • Invite teammates — by email, with a role (owner / admin / member).
  • Server-owned policy — capture mode + watchlist. The desktop shows 🔒 pinned states for whatever you set.
  • Budget alerts — per-period USD thresholds + Slack webhook + email toggle.

Use it well

  1. Bind your own desktop first.

    Generate a linking code, paste it into your desktop's Settings → Connect to team, confirm consent, watch the device appear in the device list with a green status.

  2. Invite the rest of the team in one batch.

    Bulk-invite by email; each invitee gets a one-time link that creates their account and walks them through binding their desktop.

  3. Set policy before any contractor binds.

    The capture-mode floor and sensitive-path watchlist pin themselves on every desktop on first tick after binding. A contractor who binds with no policy set will stream content-mode telemetry by default.

  4. Wire one Slack webhook for budget alerts.

    One channel, one webhook URL, one notification per breach. Don't fan out to multiple channels — alert fatigue is the failure mode.

Read more