Blog: Grok Build is now open source

[atharva-appwrite]

Summary

• Covers SpaceXAI open-sourcing the Grok Build CLI, TUI, and agent runtime under Apache 2.0
• Explains custom and local inference support, the contribution-policy limitation, and the new privacy defaults
• Adds an unlisted Appwrite blog post with an API-generated cover and developer guidance for AGENTS.md and MCP workflows

Source announcement: https://x.com/SpaceXAI/status/2077494535387828644

Validation

• bun format && bun optimize
• bun run format:check
• bun run check attempted; blocked by 37 existing missing environment-variable exports in the local checkout

[appwrite]

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)

Site	Status	Logs	Preview	QR
website 69d7f2670014e24571ca	Ready	View Logs	Preview URL

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)

Site	Status	Logs	Preview	QR
website 68496a17000f03d62013	Queued	View Logs	Preview URL

---

Tip

Build commands execute in runtime containers during deployment

[greptile-apps]

Greptile Summary

This PR adds a new Appwrite blog post covering SpaceXAI's open-sourcing of Grok Build (CLI, TUI, and agent runtime) under Apache 2.0, along with the accompanying cover image and optimize-cache entry.

• The markdoc frontmatter is complete and valid: author: aishwari matches an existing author file, date is present, and the cover path (/images/blog/grok-build-open-source/cover.avif) resolves correctly to the committed AVIF asset.
• The .optimize-cache.json entry uses the project's .png-key convention for a committed .avif file, which is consistent with how other recent blog covers are tracked in the cache.
• The post is unlisted: false, so it will appear in the blog listing, RSS feed, and JSON feed as expected.

Confidence Score: 5/5

This PR is safe to merge — it adds a new blog post, a binary cover image, and one cache entry with no logic changes.

All three changed files are additive content: a markdoc blog post with valid frontmatter (existing author, date present, cover path correct), a static AVIF image, and a cache entry that follows the repo's established .png-key convention. There are no code changes and no risk of regressions.

No files require special attention.

Important Files Changed

Filename	Overview
src/routes/blog/post/grok-build-open-source/+page.markdoc	New blog post covering Grok Build open-sourcing; frontmatter is complete and valid (author aishwari exists, date present, cover path matches committed AVIF), content is well-structured with no broken internal links
.optimize-cache.json	Adds cache entry for the new blog cover image; uses .png key per repo convention even though the committed file is .avif — extension mismatch is intentional per project rules
static/images/blog/grok-build-open-source/cover.avif	New AVIF cover image for the blog post; binary asset, no issues

_{Reviews (6): Last reviewed commit: "chore: list Grok Build blog post" | Re-trigger Greptile}

[atharvadeosthale]

@copilot use relative links instead of appwrite.io. except for discord, that remains absolute.

[atharvadeosthale]

@copilot run bun optimize and push

[Copilot]

@copilot use relative links instead of appwrite.io. except for discord, that remains absolute.

Updated in 3eeeb84: Appwrite docs links in the post now use relative paths (/docs/...), and no Discord link was changed.

[Copilot]

@copilot run bun optimize and push

Done in c244aaf. I ran bun optimize and pushed the resulting asset updates.