Skip to content

docs: modernize README - #4677

Closed
Kitenite wants to merge 6 commits into
mainfrom
readme-modernization
Closed

Kitenite wants to merge 6 commits into
mainfrom
readme-modernization

Conversation

@Kitenite

@Kitenite Kitenite commented May 17, 2026 •

Copy link
Copy Markdown
Member

Summary

Cleans up the README, tightens the copy, and reorganizes it to match the layout of widely-used repos.

Changes

Content fixes

  • Fix the demo link to point at the Introducing Superset video; remove leftover TODO placeholders and a duplicated hero image
  • Drop the "native macOS app" wording since the app is built on Electron
  • Make the license section explicit: source-available under ELv2 (not OSI open-source)
  • Split Requirements into what you need to run the app vs. to build from source
  • Add Mastracode to the supported agents (it was missing); list now matches builtin-terminal-agents.ts

New sections

  • "What runs locally" — clarifies that code, worktrees, and agent processes stay on the machine; the backend only holds account and workspace metadata
  • "Why Superset" — short agent-agnostic / local-first / bring-your-own-keys summary

Structure & style

  • Replace the numbered pillar table with plain feature headers
  • Add agent icons to the supported-agents grid (theme-aware for monochrome logos)
  • Add a numbered "How it works" and tighten each section to scan faster
  • Move Getting Started up near the top, ahead of the feature detail
  • Align the headline with superset.sh ("100+ coding agents")

Notes

  • The hero image is still the single marketing banner — a real in-app screenshot or demo GIF would be a worthwhile follow-up.

Restructure the README around a ghostty-style declarative voice with a
concrete headline, an About paragraph, and 5 deep-dive feature
subheadings instead of the previous one-line feature table.

Trim Keyboard Shortcuts and Configuration to one-line pointers to the
docs site. Remove Mastra Dependencies, Private by Default, and the
boilerplate Contributing checklist. Add placeholders for a real product
screenshot and demo video at the top.
@capy-ai

capy-ai Bot commented May 17, 2026

Copy link
Copy Markdown

Capy auto-review is paused for this organization because the monthly auto-review limit has been reached. Increase the limit or turn it off in billing settings to resume automatic reviews.

@ghost

ghost commented May 17, 2026 •

Copy link
Copy Markdown

Ready to review this PR? Stage has broken it down into 4 individual chapters for you:

Title
1 Update hero section and value proposition
2 Revise feature descriptions and agent support
3 Clarify local-first architecture and requirements
4 Streamline community and license information
Open in Stage

Chapters generated by Stage for commit 300fcb9 on May 21, 2026 6:40am UTC.

@coderabbitai

coderabbitai Bot commented May 17, 2026 •

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

README.md reorganizes top-level messaging (hero, What it is, Why, Features), reworks Supported Agents and Getting Started into a macOS-first flow with Requirements, replaces Keyboard Shortcuts with a Configuration section, shortens Contributing/Community, and expands the license paragraph.

Changes

README Marketing and Documentation Restructure

Layer / File(s) Summary
Hero, About, Why & Features
README.md
Top hero tagline and description replaced; added "What it is", "Why Superset", and detailed Features subsections; adjusted primary top links and section flow.
Supported Agents & Getting Started
README.md
Reworked Supported Agents content (includes "Any other CLI agent" wording); consolidated Getting Started to a single macOS download CTA with a Requirements table and a collapsible "Build from source" details block.
Configuration and keyboard shortcuts
README.md
Replaced prior Keyboard Shortcuts section with a "Configuration" section referencing .superset/config.json and pointing to customizable shortcuts via Settings.
Contributing, Community, and contributors block
README.md
Condensed contributing text to link to CONTRIBUTING.md; added a short "Superset is a desktop app built on Electron" line and retained the contributors image block before Community.
License paragraph
README.md
Expanded license text into a longer ELv2 description paragraph and added an explicit LICENSE.md link.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰
I hopped through README lines with cheer,
A new bold hero now appears,
Features, config, a macOS call,
Contributors gathered, license tall,
I nibbled docs and left a tiny cheer 🌙

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'docs: modernize README' directly reflects the main change of the pull request, which is a comprehensive refresh of the README documentation with updated positioning, content structure, and styling.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description check ✅ Passed The pull request description is comprehensive and well-structured, covering content fixes, new sections, structure/style changes, and notes about follow-up work.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch readme-modernization

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

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.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 21-25: Update the placeholder screenshot and demo link in README:
replace the TODO HTML comment and the <img> src
"apps/marketing/public/images/readme-hero.png" with the actual product-screen
image (or its new path) and ensure the alt text reflects the real UI, and
replace the anchor href "https://www.youtube.com/" (and its placeholder comment)
with the real demo video URL; remove the TODO comments so no user-visible
placeholders remain and verify the assets load correctly in the rendered README.
- Around line 44-68: The subsection headings under the "What Superset Does"
section use level-4 headings (e.g., "Parallel agents in isolated git worktrees",
"Notifications when agents need you", "Built-in diff review and inline editing",
"Reproducible workspace setup", "Universal CLI-agent compatibility") but must be
level-3 to follow the main `##` heading; change each leading "####" to "###" for
those headings in README.md so the Markdown heading hierarchy (MD001) is
satisfied.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 26fcd576-bcf0-4b1d-b8af-9c95e4e4cdf2

📥 Commits

Reviewing files that changed from the base of the PR and between ca7ad95 and 17baacc.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md Resolved
Comment thread README.md Resolved

@cubic-dev-ai cubic-dev-ai Bot left a comment •

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.

1 issue found across 1 file

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Re-trigger cubic

Comment thread README.md Resolved
@greptile-apps

greptile-apps Bot commented May 17, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR rewrites the README in a declarative, docs-style voice — replacing the marketing feature table with five prose subsections, trimming the keyboard-shortcuts and configuration tables to single-line doc pointers, and removing contributor-only and boilerplate sections.

  • The "What Superset Does" anchor table links resolve correctly against the #### subheadings, but those subheadings skip H3 in the document hierarchy.
  • Two acknowledged TODO placeholders remain: the hero image at line 22 reuses the same readme-hero.png already shown at line 3 (causing a duplicate render), and the demo video link points to the YouTube homepage rather than an actual video URL — both are explicitly flagged in the PR test plan as required fixes before merging.

Confidence Score: 4/5

Safe to merge after the two TODO placeholders are resolved — no functional code is changed.

The prose restructuring is clean and anchor links resolve correctly. The two outstanding items — a duplicate hero image and a YouTube link pointing to the homepage — are present in the diff as-is and would be visible to anyone viewing the README on GitHub today.

README.md — the two TODO blocks at lines 21-24 need real content before this is merged.

Important Files Changed

Filename Overview
README.md README restructured with new prose sections, anchor table, and two unresolved TODO placeholders (duplicate hero image and placeholder YouTube URL) that the PR description requires resolving before merge.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[README.md top] --> B[Hero image - readme-hero.png]
    B --> C[Badges & nav links]
    C --> D[TODO placeholder - same readme-hero.png]
    D --> E[TODO YouTube link - youtube.com homepage]
    E --> F[About prose]
    F --> G[What Superset Does - anchor table]
    G --> H1[#### Parallel agents in isolated git worktrees]
    G --> H2[#### Notifications when agents need you]
    G --> H3[#### Built-in diff review and inline editing]
    G --> H4[#### Reproducible workspace setup]
    G --> H5[#### Universal CLI-agent compatibility]
    H1 & H2 & H3 & H4 & H5 --> I[Supported Agents table]
    I --> J[Requirements / Getting Started / Config / Shortcuts]
    J --> K[Tech Stack / Contributing / Community / License]

    style D fill:#ffdddd,stroke:#cc0000
    style E fill:#ffdddd,stroke:#cc0000
Loading
Prompt To Fix All With AI
Fix the following 3 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 3
README.md:3
**Duplicate hero image renders twice**

The same `apps/marketing/public/images/readme-hero.png` is referenced at line 3 (the original hero) and again at line 22 (the TODO placeholder). Until the TODO at line 22 is replaced with a real product screenshot, visitors will see the same image displayed twice at the top of the README. If the intent is for line 22 to eventually hold a different screenshot, line 3 may also need to be removed to avoid duplication.

### Issue 2 of 3
README.md:24
The `href` is currently the YouTube homepage (`https://www.youtube.com/`), so clicking the link sends users to YouTube's front page instead of the demo video. The PR test plan marks this as a required fix before merging — the placeholder URL should be swapped out before landing.

```suggestion
<a href="https://www.youtube.com/YOUR_VIDEO_ID">▶ Watch the 90-second demo</a>
```

### Issue 3 of 3
README.md:44
**Heading hierarchy skips H3 (`###`)**

The feature subheadings (`####`) sit directly under the `## What Superset Does` H2, skipping the H3 level entirely. While GitHub renders this fine visually, WCAG accessibility guidelines and most Markdown linters flag a heading-level skip as a structural error that can confuse screen readers and automated outline parsers. Using `###` for these subheadings would make the document outline consistent.

Reviews (1): Last reviewed commit: "docs: modernize README" | Re-trigger Greptile

Comment thread README.md Outdated
@@ -2,7 +2,9 @@

<img width="full" alt="Superset" src="apps/marketing/public/images/readme-hero.png" />

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.

P2 Duplicate hero image renders twice

The same apps/marketing/public/images/readme-hero.png is referenced at line 3 (the original hero) and again at line 22 (the TODO placeholder). Until the TODO at line 22 is replaced with a real product screenshot, visitors will see the same image displayed twice at the top of the README. If the intent is for line 22 to eventually hold a different screenshot, line 3 may also need to be removed to avoid duplication.

Prompt To Fix With AI
This is a comment left during a code review.
Path: README.md
Line: 3

Comment:
**Duplicate hero image renders twice**

The same `apps/marketing/public/images/readme-hero.png` is referenced at line 3 (the original hero) and again at line 22 (the TODO placeholder). Until the TODO at line 22 is replaced with a real product screenshot, visitors will see the same image displayed twice at the top of the README. If the intent is for line 22 to eventually hold a different screenshot, line 3 may also need to be removed to avoid duplication.

How can I resolve this? If you propose a fix, please make it concise.

Comment thread README.md Outdated
<!-- TODO: replace with real product screenshot of the main UI with multiple workspaces -->
<img width="900" alt="Superset main UI" src="apps/marketing/public/images/readme-hero.png" />

<a href="https://www.youtube.com/"><!-- TODO: replace with actual demo video URL -->▶ Watch the 90-second demo</a>

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.

P2 The href is currently the YouTube homepage (https://www.youtube.com/), so clicking the link sends users to YouTube's front page instead of the demo video. The PR test plan marks this as a required fix before merging — the placeholder URL should be swapped out before landing.

Suggested change
<a href="https://www.youtube.com/"><!-- TODO: replace with actual demo video URL -->▶ Watch the 90-second demo</a>
<a href="https://www.youtube.com/YOUR_VIDEO_ID">▶ Watch the 90-second demo</a>
Prompt To Fix With AI
This is a comment left during a code review.
Path: README.md
Line: 24

Comment:
The `href` is currently the YouTube homepage (`https://www.youtube.com/`), so clicking the link sends users to YouTube's front page instead of the demo video. The PR test plan marks this as a required fix before merging — the placeholder URL should be swapped out before landing.

```suggestion
<a href="https://www.youtube.com/YOUR_VIDEO_ID">▶ Watch the 90-second demo</a>
```

How can I resolve this? If you propose a fix, please make it concise.

Comment thread README.md Outdated
| **Universal Compatibility** | Works with any CLI agent that runs in a terminal |
| **Quick Context Switching** | Jump between tasks as they need your attention |
| **IDE Integration** | Open any workspace in your favorite editor with one click |
#### Parallel agents in isolated git worktrees

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.

P2 Heading hierarchy skips H3 (###)

The feature subheadings (####) sit directly under the ## What Superset Does H2, skipping the H3 level entirely. While GitHub renders this fine visually, WCAG accessibility guidelines and most Markdown linters flag a heading-level skip as a structural error that can confuse screen readers and automated outline parsers. Using ### for these subheadings would make the document outline consistent.

Prompt To Fix With AI
This is a comment left during a code review.
Path: README.md
Line: 44

Comment:
**Heading hierarchy skips H3 (`###`)**

The feature subheadings (`####`) sit directly under the `## What Superset Does` H2, skipping the H3 level entirely. While GitHub renders this fine visually, WCAG accessibility guidelines and most Markdown linters flag a heading-level skip as a structural error that can confuse screen readers and automated outline parsers. Using `###` for these subheadings would make the document outline consistent.

How can I resolve this? If you propose a fix, please make it concise.

@github-actions

github-actions Bot commented May 17, 2026 •

Copy link
Copy Markdown
Contributor

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

  • ⚠️ Neon database branch

Thank you for your contribution! 🎉

- Replace broken demo link with the official Introducing Superset video
- Remove TODO placeholders and duplicate hero image
- Drop 'native' claim that contradicted the Electron stack
- Make license framing explicit (source-available, not OSI open-source)
- Add 'What runs locally' section clarifying local execution vs backend
- Split Requirements: runtime deps vs build-from-source deps
- Replace 'Pillar' table with plain feature headers
- Add 'Why Superset' section leading with agent-agnosticism
- Align headline with superset.sh (100+ agents)

@coderabbitai coderabbitai Bot left a comment

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.

♻️ Duplicate comments (1)
README.md (1)

33-33: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use ### for feature subsection headings under ## Features.

Line 33 (and the same pattern at Lines 39, 47, and 53) skips heading depth (## → ####), which violates MD001 and hurts doc structure/linting.

Suggested diff
-#### Parallel agents in isolated git worktrees
+### Parallel agents in isolated git worktrees

-#### Works with any CLI agent
+### Works with any CLI agent

-#### Notifications when agents need you
+### Notifications when agents need you

-#### Built-in diff review and inline editing
+### Built-in diff review and inline editing

-#### Reproducible workspace setup
+### Reproducible workspace setup

Also applies to: 39-39, 47-47, 53-53

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 33, The subsection headings under "## Features" (e.g., the
heading "Parallel agents in isolated git worktrees" currently using "####")
should use "###" instead of "####" to preserve proper heading depth and satisfy
MD001; update each affected headings (the ones at lines with texts like
"Parallel agents in isolated git worktrees" and the similar headings at the
other noted locations) to use "###" so they are direct subsections of "##
Features" and fix the linting/doc structure issue.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Duplicate comments:
In `@README.md`:
- Line 33: The subsection headings under "## Features" (e.g., the heading
"Parallel agents in isolated git worktrees" currently using "####") should use
"###" instead of "####" to preserve proper heading depth and satisfy MD001;
update each affected headings (the ones at lines with texts like "Parallel
agents in isolated git worktrees" and the similar headings at the other noted
locations) to use "###" so they are direct subsections of "## Features" and fix
the linting/doc structure issue.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 51dd829b-6534-4bde-8cf2-b55e2df7371e

📥 Commits

Reviewing files that changed from the base of the PR and between 17baacc and 0b3c0ee.

📒 Files selected for processing (1)
  • README.md

@coderabbitai coderabbitai Bot left a comment

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.

Actionable comments posted: 1

♻️ Duplicate comments (1)
README.md (1)

33-51: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix heading hierarchy to satisfy MD001.

These feature subsection headings still use h4 (####) after an h2 (##) parent. Per Markdown best practices and the prior review comment, they should be h3 (###).

Suggested fix
-#### Parallel agents in isolated git worktrees
+### Parallel agents in isolated git worktrees
 
 Each task runs in its own git worktree...
 
-#### Works with any CLI agent
+### Works with any CLI agent
 
 Claude Code, Codex, Cursor Agent...
 
-#### Notifications when agents need you
+### Notifications when agents need you
 
 Superset watches every workspace...
 
-#### Built-in diff review and inline editing
+### Built-in diff review and inline editing
 
 Every workspace has a diff view...
 
-#### Reproducible workspace setup
+### Reproducible workspace setup
 
 A `.superset/config.json` at your repo root...
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 33 - 51, Change the subsection headings that
currently use h4 (lines starting with "#### Parallel agents in isolated git
worktrees", "#### Works with any CLI agent", "#### Notifications when agents
need you", "#### Built-in diff review and inline editing", and "####
Reproducible workspace setup") to h3 (use "###") so they are proper children of
the surrounding h2 and satisfy MD001; update each heading token and ensure no
other heading levels nearby are inadvertently altered.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 57-64: The icon <img> elements in README.md (e.g., the <img> tags
referencing packages/ui/src/assets/icons/preset-icons/*.svg and the <img> inside
<picture> elements such as codex.svg, copilot.svg, opencode.svg, pi.svg) are
missing alt attributes; add empty alt attributes (alt="") to each decorative
<img> so screen readers ignore them (do not modify <source> tags inside
<picture>, only add alt="" to the corresponding <img> tags).

---

Duplicate comments:
In `@README.md`:
- Around line 33-51: Change the subsection headings that currently use h4 (lines
starting with "#### Parallel agents in isolated git worktrees", "#### Works with
any CLI agent", "#### Notifications when agents need you", "#### Built-in diff
review and inline editing", and "#### Reproducible workspace setup") to h3 (use
"###") so they are proper children of the surrounding h2 and satisfy MD001;
update each heading token and ensure no other heading levels nearby are
inadvertently altered.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d7333612-b505-438b-86cb-4f9a2ce27ecf

📥 Commits

Reviewing files that changed from the base of the PR and between 0b3c0ee and dfac87f.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md Resolved

@coderabbitai coderabbitai Bot left a comment

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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 65: The new table row's <img> element (the inline image showing the
Mastracode icon) is missing an empty decorative alt attribute which triggers
MD045; update that <img> tag to include alt="" so screen readers ignore the
decorative icon and the Markdown linter stops flagging it, keeping the
surrounding picture/source elements unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2e726269-48b4-438d-a5b1-2822cd3e9dc7

📥 Commits

Reviewing files that changed from the base of the PR and between dfac87f and 957808b.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md Resolved

This branch was previously deployed

1 inactive deployment
preview — 300fcb99 Deployed May 21, 2026 by Kitenite via Deploy Docs #5645
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.

1 participant