[linushohne]

Problem

The FAQ entry "Why is my Claude 5-hour limit draining so fast?" still says the Agent SDK metering bug is unfixed and that we are "hoping for a fix soon". #28410 fixed it, and the fix shipped in v0.1.7. The tracking issue #24649 is closed as completed. Users who read the FAQ now get the wrong answer.

Change

Rewrote that one FAQ answer:

• It is fixed since v0.1.7.
• Explains what used to happen (about 1.7x on the 5h meter, weekly limits never affected).
• Tells users who still see it to update T3 Code on the machine that runs their agents.
• Keeps the link to Theo's post and adds a link to the tracking issue.

Scope and approval

Docs only. It corrects one FAQ answer that became wrong when #28410 merged. Nothing else changes.

Verification

• GitHub compare of the update the claude entrypoint identifier for accuracy #28410 merge commit against the v0.1.7 tag reports ahead, so v0.1.7 contains the fix.
• Claude 5h limit drains about 1.7x faster in T3 Code than in the Claude Code CLI (Anthropic Agent SDK metering) #24649 is closed as completed. The post-merge measurement by @A5harib in that issue shows the 5h meter draining at the same rate as the interactive TUI with the t3-code entrypoint.
• Checked that the ./updating.md link exists.
• Did not run vp run check:changed. This is a one-paragraph Markdown change with no code.

Written with Claude Opus 5.5 in Claude Code (T3 Code).

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at 0b5eb65

Macroscope's review found this PR approvable — The FAQ now describes the released Claude metering fix and directs affected users to update their agent machine. The linked tracking issue supports the guidance; no runtime behavior or product defaults change.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The FAQ now says Claude usage in T3 Code has matched Claude Code’s 5-hour limit rate since v0.1.7. It describes the previous approximately 1.7× rate, notes that weekly limits were unaffected, and advises users who still see the issue to update T3 Code.

Changes: Claude usage FAQ

Layer / File(s)	Summary
Update Claude usage FAQ docs/user/faq.md	The answer describes the metering rate since v0.1.7, the previous approximately 1.7× rate, and that weekly limits were unaffected. It advises users who still see the issue to update T3 Code and adds a tracking-issue link.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Possibly related issues

• pingdotgg/t3code#24649 — Tracks the Agent SDK metering issue described in the updated FAQ.

Suggested reviewers: t3dotgg, juliusmarminge

Merge Risk: Minimal · up to 0b5eb

The FAQ-only update presents no established risk requiring changes before merge.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: updating the FAQ to state that the Claude 5-hour limit drain issue is fixed.
Description check		The description includes the required Problem, Change, Scope and approval, and Verification sections. It explains the outdated FAQ, documents the correction, identifies the related issues and release,…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description includes the required Problem, Change, Scope and approval, and Verification sections. It explains the outdated FAQ, documents the correction, identifies the related issues and release, and provides specific verification results and limitations.

Finishing Touches

Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

Recent review info

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: 337c585
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: 53e1e6f6-dfbd-476d-9169-62fced331da3

Commits

Reviewing files that changed from the base of the PR and between 337c585 and 0b5eb65.

Files selected for processing: 1

• docs/user/faq.md

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.