docs(kilo-docs): mark KiloClaw end of life - #13361
Merged
Merged
Conversation
Add a shared kiloclaw-eol partial and render it on every KiloClaw page, and remove the KiloClaw card, hero CTA, quick links, and terminal tab from the docs homepage plus the pointer link in the architecture Related list. The top-level nav entry stays so existing users can still reach the docs.
Drop KiloClaw from the mobile app capabilities and screenshots, the Cloud Agent triggers comparison, and the ChatGPT and xAI cloud-feature notes. Contributor architecture pages keep their KiloClaw entries because that code still exists.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Code Review SummaryStatus: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Fix these issues in Kilo Cloud Files Reviewed (38 files)
Reviewed by grok-4.6 · Input: 230.1K · Output: 16.4K · Cached: 1.2M Review guidance: REVIEW.md from base branch |
arkadiykondrashov
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Marks KiloClaw as end of life across the docs site and stops pointing users at it.
pages/kiloclaw/now renders an EOL warning callout stating that KiloClaw is closed to new users and that support is ending.Why
Signups are closed and we're ending support, so KiloClaw shouldn't appear in promotional surfaces or in stories about other products. The section stays reachable from the top-level nav so existing users can still read the docs, which is why the banner is on every page rather than only the overview.
Notes for reviewers
The banner lives in one Markdoc partial,
markdoc/partials/kiloclaw-eol.md, included from all 31 pages — edit that file to change the wording everywhere. It deliberately carries no shutdown date; add one when it's decided.pages/contributing/architecture/keeps its KiloClaw entries. Those are contributor-facing tables and diagrams describing code that still exists (services/kiloclaw*in the cloud repo,webview-ui/kiloclaw/in this one), not promotion. Removing them would make the architecture docs disagree with the codebase and drop a documented security boundary. They should go when the code does.Still reading as if the product is live, left for a follow-up:
kiloclaw/overview.mdtells readers to sign up and walks through creating an instance, andkiloclaw/faq/pricing.mdreads as an active price list.No changeset: docs-only, nothing user-facing to release.