Docs preview

Check off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here.

• docs/ai-coder/agents/licensing-usage.md
• docs/ai-coder/ai-governance.md
• docs/ai-coder/index.md
• docs/reference/glossary.md

I'll open a PR in coder/coder.com to redirect the removed page.

Documentation Check

This is a docs PR, so the findings below are about consistency gaps the change leaves behind, not missing docs for code.

Updates Needed

• docs/reference/glossary.md - Resolved in 5dfa2ad by removing the Agent Workspace Build entry and dropping the "expands Agent Workspace Build allowances" claim from the AI Governance entry, so the glossary no longer points readers to content that was deleted.
• docs/ai-coder/tasks.md - repointed the AWB note (the a2c5304 edit was reverted in 5dfa2ad)

  ⚠️ Reverted. Line 25 again tells readers to "use AI Governance features, [AI Governance]... provides expanded usage pools that grow with your user count," but ai-governance.md no longer documents Agent Workspace Build pools/limits after this PR. Either restore a brief AWB usage note on ai-governance.md or soften this pointer.

• docs/ai-coder/index.md - The dangling "Expanded Agent Workspace Build allowances" bullet pointing to AI Governance was removed. Fixed in a2c5304.
• docs/images/admin/ai-governance-awb-usage.png - Orphaned image deleted. Fixed in a2c5304.

New Documentation Needed

• docs/reference/glossary.md - 5dfa2ad also removed the Coder Tasks glossary entry, but Coder Tasks is a deprecated-yet-still-documented term (dedicated docs/ai-coder/tasks.md page and widespread use across docs/ai-coder/). Per the glossary rule, a deprecated term should keep an entry that says it is deprecated and names Coder Agents as the replacement, rather than being deleted. Consider retaining a deprecation entry.

External follow-up

• docs/ai-coder/usage-data-reporting.md is deleted, so a redirect entry in coder/coder.com:redirects.json is required. The author noted they will open that PR.

  ⚠️ External repo, cannot be verified from this PR.

Automated review via Coder Agents

Replying to the doc-check comment.

All items addressed in commit a2c5304:

• docs/reference/glossary.md: The Agent Workspace Build entry now points to tasks.md instead of ai-governance.md. The AI Governance entry no longer claims it "expands Agent Workspace Build allowances."
• docs/ai-coder/tasks.md: The 1,000-build note now self-contains the scaling explanation and links to ai-governance.md only for AI Governance features, not for AWB limit details.
• docs/ai-coder/index.md: Removed the "Expanded Agent Workspace Build allowances" bullet from the AI Governance feature list, since ai-governance.md no longer documents AWB.
• docs/images/admin/ai-governance-awb-usage.png: Deleted. No remaining references.
• External follow-up: The coder/coder.com redirect for the deleted usage-data-reporting.md page is in coder/coder.com#1015, which should merge after this PR.

PR generated with Coder Agents

Updated approach per feedback (commits a2c5304 and 5dfa2ad):

• docs/reference/glossary.md: Removed the entire Agent Workspace Build entry, the entire Coder Tasks entry, and the Coder Tasks mention from the Coding agent entry. No AWB or Coder Tasks references remain.
• docs/ai-coder/tasks.md: Reverted. The Coder Tasks page removal is handled by a separate open PR, so this page is left unchanged.
• docs/ai-coder/index.md: Removed the "Expanded Agent Workspace Build allowances" bullet from the AI Governance feature list.
• docs/images/admin/ai-governance-awb-usage.png: Deleted. No remaining references.
• External follow-up: The coder/coder.com redirect for the deleted usage-data-reporting.md page is in coder/coder.com#1015, which should merge after this PR.

PR generated with Coder Agents

Two accuracy tweaks for the Agent Time usage reporting section (hb_agent_runtime_v1):

1. Publish cadence. "Coder attempts to publish usage data approximately every 17 minutes" describes the publisher's check interval, but a request is only sent when unpublished events exist. Each hb_agent_runtime_v1 event is generated once per UTC hour, about 5 minutes after the hour closes (plus a few minutes of jitter), then shipped on the next 17-minute check. In steady state that's roughly one request per hour, with an hour's event reaching Tallyman within ~25 minutes of that hour ending. Worth clarifying so readers don't expect the 14:00 event in logs before ~15:05.

2. Backfill. After downtime, Coder regenerates missed hourly events (zero-filled for idle hours) for up to 7 trailing days, so a single publish can contain multiple events (batched up to 100 per request). Hours missing beyond 7 days are not reported.

Suggested wording for the cadence paragraph:

Coder generates one hb_agent_runtime_v1 event for each UTC hour shortly after the hour ends, and checks for unpublished events approximately every 17 minutes, so each hour's usage typically reaches Tallyman within about 25 minutes. If the deployment was offline, Coder backfills missed hours for up to seven days.

Two accuracy tweaks for the Agent Time usage reporting section (hb_agent_runtime_v1):

1. Publish cadence. "Coder attempts to publish usage data approximately every 17 minutes" describes the publisher's check interval, but a request is only sent when unpublished events exist. Each hb_agent_runtime_v1 event is generated once per UTC hour, about 5 minutes after the hour closes (plus a few minutes of jitter), then shipped on the next 17-minute check. In steady state that's roughly one request per hour, with an hour's event reaching Tallyman within ~25 minutes of that hour ending. Worth clarifying so readers don't expect the 14:00 event in logs before ~15:05.
2. Backfill. After downtime, Coder regenerates missed hourly events (zero-filled for idle hours) for up to 7 trailing days, so a single publish can contain multiple events (batched up to 100 per request). Hours missing beyond 7 days are not reported.

Suggested wording for the cadence paragraph:

Coder generates one hb_agent_runtime_v1 event for each UTC hour shortly after the hour ends, and checks for unpublished events approximately every 17 minutes, so each hour's usage typically reaches Tallyman within about 25 minutes. If the deployment was offline, Coder backfills missed hours for up to seven days.

Added 👍