Skip to content
This repository was archived by the owner on Sep 21, 2026. It is now read-only.

ChatGPT Business Premium seats: Pricing and what's new - #3161

Merged
atharvadeosthale merged 17 commits into
mainfrom
chatgpt-business-premium-seats-pricing-whats-new
Aug 12, 2026
Merged

atharvadeosthale merged 17 commits into
mainfrom
chatgpt-business-premium-seats-pricing-whats-new

Conversation

@aishwaripahwa12

Copy link
Copy Markdown
Contributor

Latest SEO blog

@appwrite

appwrite Bot commented Aug 11, 2026 •

Copy link
Copy Markdown

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
 website
69d7f2670014e24571ca
Ready Ready View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Queued Queued View Logs Preview URL QR Code


Tip

Storage files get ClamAV malware scanning and encryption by default

@greptile-apps

greptile-apps Bot commented Aug 11, 2026 •

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR adds an unlisted SEO article about ChatGPT Business Premium seats, its optimized cover image, and the corresponding image-cache entry.

  • Adds pricing, seat-mixing, promotional-credit, and API comparison content.
  • Adds the AVIF cover asset and records its optimizer cache metadata.

Confidence Score: 4/5

The 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 unlisted: true hides this article from the blog listing but does not prevent its publication to feed subscribers and API consumers.

Files Needing Attention: src/routes/blog/post/chatgpt-business-premium-seats-pricing-and-whats-new/+page.markdoc

Important Files Changed

Filename Overview
src/routes/blog/post/chatgpt-business-premium-seats-pricing-and-whats-new/+page.markdoc Adds the new unlisted blog article; the previously reported feed-visibility issue remains outstanding.
.optimize-cache.json Adds the cache entry corresponding to the new cover image; the extension difference is intentional under repository rules.
static/images/blog/chatgpt-business-premium-seats-pricing-and-whats-new/cover.avif Adds the optimized cover asset referenced by the article frontmatter.

Reviews (7): Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." | Re-trigger Greptile

timeToRead: 5
author: aishwari
category: ai
featured: false

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 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.

Fix in Claude Code Fix in Codex

| 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 |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Afaik, them removing the 5h limit was temporary, can we double check this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No . No . Maybe we should rephrase

…ium-seats-pricing-whats-new

# Conflicts:
#	.optimize-cache.json
@atharvadeosthale
atharvadeosthale merged commit 73d7756 into main Aug 12, 2026
6 of 7 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants