Skip to content

New comparison blog#2946

Merged
atharvadeosthale merged 6 commits intomainfrom
comparisonblogai/5
May 1, 2026
Merged

New comparison blog#2946
atharvadeosthale merged 6 commits intomainfrom
comparisonblogai/5

Conversation

@aishwaripahwa12
Copy link
Copy Markdown
Contributor

Claude vs ChatGPT vs Gemini

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 30, 2026

Greptile Summary

This PR adds a new developer-focused comparison blog post for Claude, GPT, and Gemini, along with its cover image and cache entry. The cache key and image path are now consistent, and the previously truncated Gemini sentence is complete.

  • The SWE-bench section (lines 33–35) cites specific percentages for Claude Opus 4.7, GPT-5.5, and Gemini 3.1 Pro without linking to any source leaderboard or test configuration. These numbers are the most share-worthy part of the post and will be treated as authoritative Appwrite claims — a source link is needed before publishing.

Confidence Score: 4/5

Safe to merge once the unsourced SWE-bench figures are linked to a verifiable source.

One P1 finding: specific benchmark percentages published without citation pose a real credibility risk if inaccurate. All other aspects (cache key, image path, prose completeness) look correct.

The blog markdoc file — specifically the SWE-bench figures at lines 33–35.

Important Files Changed

Filename Overview
src/routes/blog/post/claude-vs-gpt-vs-gemini-for-developers-who-wins-in-2026/+page.markdoc New comparison blog post; specific SWE-bench percentages are cited without any source link, which is a credibility risk if the numbers are inaccurate or outdated.
.optimize-cache.json Cache key added matches the actual image path (claude-vs-gpt-vs-gemini-.../cover.png); no issues.
static/images/blog/claude-vs-gpt-vs-gemini-for-developers-who-wins-in-2026/cover.png Binary cover image added at the path referenced by frontmatter and cache; no issues.

Reviews (5): Last reviewed commit: "Add SWE-bench scores section to comparis..." | Re-trigger Greptile

Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>
@atharvadeosthale
Copy link
Copy Markdown
Member

@copilot change all chatgpt references in this blog to be the GPT model. Same for file name and title.

Agent-Logs-Url: https://github.com/appwrite/website/sessions/47abe400-e502-4621-86cb-2a6224a936f1

Co-authored-by: atharvadeosthale <11805367+atharvadeosthale@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI commented May 1, 2026

@copilot change all chatgpt references in this blog to be the GPT model. Same for file name and title.

Done in commit 90987d6. All "ChatGPT" references have been replaced with "GPT" throughout the blog post, and the file/directory names have been updated to claude-vs-gpt-vs-gemini-for-developers-who-wins-in-2026. The title is now "Claude vs GPT vs Gemini for developers: Who wins in 2026?"

@atharvadeosthale
Copy link
Copy Markdown
Member

@copilot add a section that compares swe bench scores for the models

Claude Opus 4.7 — 64.3%
GPT-5.5 — 58.6%
Gemini 3.1 Pro — 54.2%

Comment thread .optimize-cache.json Outdated
atharvadeosthale and others added 2 commits May 1, 2026 21:06
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Agent-Logs-Url: https://github.com/appwrite/website/sessions/a9a0e8c6-bbd5-43ef-a243-0a02c9749357

Co-authored-by: atharvadeosthale <11805367+atharvadeosthale@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI commented May 1, 2026

@copilot add a section that compares swe bench scores for the models

Claude Opus 4.7 — 64.3%
...

Added in commit d47b5c5. A new "SWE-bench: what the numbers say" section now appears after the summary with the three scores. Also updated the intro paragraph to no longer dismiss benchmarks since the post now includes them.

@atharvadeosthale atharvadeosthale merged commit e5af375 into main May 1, 2026
6 checks passed
@atharvadeosthale atharvadeosthale deleted the comparisonblogai/5 branch May 1, 2026 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants