Repository navigation
ChatGPT Business Premium seats: Pricing and what's new - #3161
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Storage files get ClamAV malware scanning and encryption by default |
Greptile SummaryThe PR adds an unlisted SEO article about ChatGPT Business Premium seats, its optimized cover image, and the corresponding image-cache entry.
Confidence Score: 4/5The PR is not yet safe to merge because the unlisted article remains exposed through the public RSS and JSON feeds. The current feed handlers still consume the raw post collection, so Files Needing Attention: src/routes/blog/post/chatgpt-business-premium-seats-pricing-and-whats-new/+page.markdoc Important Files Changed
Reviews (7): Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." | Re-trigger Greptile |
| timeToRead: 5 | ||
| author: aishwari | ||
| category: ai | ||
| featured: false |
There was a problem hiding this comment.
Unlisted post leaks into feeds
When the RSS or JSON feed is generated, this post's unlisted: true flag is bypassed because both endpoints publish the raw posts collection, causing feed subscribers and consumers to receive a post hidden from the blog listing.
Knowledge Base Used: Blog and Changelog
Prompt To Fix With AI
This is a comment left during a code review.
Path: src/routes/blog/post/chatgpt-business-premium-seats-pricing-and-whats-new/+page.markdoc
Line: 10
Comment:
**Unlisted post leaks into feeds**
When the RSS or JSON feed is generated, this post's `unlisted: true` flag is bypassed because both endpoints publish the raw `posts` collection, causing feed subscribers and consumers to receive a post hidden from the blog listing.
**Knowledge Base Used:** [Blog and Changelog](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/website/-/docs/blog-and-changelog.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.| | Annual billing | $20 per user per month | $100 per user per month | | ||
| | Usage allowance | Baseline | 5x Standard | | ||
| | Five-hour usage limit | Applies | Removed | | ||
| | Usage resets | Plan limits apply | Predictable weekly resets | |
There was a problem hiding this comment.
The last three points in table are differentiating the same thing. Maybe we should remove those.
| If a Premium user still runs out, workspace owners can add **shared workspace credits** to the workspace instead of upgrading more seats. Credits are pooled and managed centrally, so the overflow budget is one line item rather than a set of individual upgrades. | ||
|
|
||
| # What removing the five-hour usage limit changes | ||
|
|
There was a problem hiding this comment.
Afaik, them removing the 5h limit was temporary, can we double check this?
There was a problem hiding this comment.
double checked the official announcement, and for premium business seats it explicitly states that premium includes “no five-hour usage limit.”
|
|
||
| Premium seat usage includes: | ||
|
|
||
| * **5x more usage** than a Standard seat. |
There was a problem hiding this comment.
We already talked about this in the table, these bullets are redundant. Also "Predictable weekly usage resets." doesn't really feel like a good point to add
|
|
||
| # How mixing Standard and Premium seats works | ||
|
|
||
| Seat mixing is the part most teams will use immediately. There is no separate subscription, no second workspace, and no split billing. |
There was a problem hiding this comment.
No . No . Maybe we should rephrase
…ium-seats-pricing-whats-new # Conflicts: # .optimize-cache.json


Latest SEO blog