Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Measure & Report AI Governance Seat Usage

Abierto
#1,228 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@zenithwolf1000 ya está trabajando en esto.

Desde el 8/1/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

[!NOTE]
This issue is a part of our larger AI Governance Add-On: PRD. See the GitHub Project for all related issues.

Our AI Governance Add-On (released in February) includes a number of seats, which can be a subset of the number of users within a Coder deployment. In the March release, we want to begin measuring and reporting to admins (and to tallyman) the number of seats consumed using AI Governance features (Bridge, Boundaries, Tasks).

Measurement
  • AI Governance Seats: Similar to our agent-ready workspace starts measurement, our collector and Tallyman should measure AI Governance seats as users who have done 1 of the following activities:
    • Authenticated to AI Bridge and sent at least 1 request
    • Created an AI Task
    • Leveraged a workspace with Boundaries (not in scope to be measured yet)
Collection & Display
  • This should be displayed in the licensing page under Agent-Ready Workspace starts as "AI Governance Users."
  • This should also be sent as a tallyman metric
Enforcement & Warnings
  • Warning banner: When an overage occurs (# of users > # entitled AI governance seats), a warning should show only to admins and an overage should be reported via Metronome/Tallyman.
Out of scope
  • Fine-grained controls: Controls for admins to specify which users/seats can see/use AI governance features is out of scope for this specific issue.
Lenguaje dominante
Sin datos de lenguaje
Estrellas
3
Forks
0
Métricas de merge de PR
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de coder/internal

Todos los issues de coder/internal

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.