Add blog posts to marketing site#1044
Conversation
- Add 4 blog posts: git worktrees for AI, worktrees history deep dive, terminal daemon architecture, and getting to 100 coding agents - Move content from repo root to apps/marketing/content/blog/ - Remove placeholder coming-soon post - Set author to avi for all posts
📝 WalkthroughWalkthroughThis PR removes a placeholder "coming soon" blog post and adds multiple new blog articles covering git worktrees for AI-assisted development, terminal daemon architecture design, scaling coding agents to 100 parallel instances, and Reddit posts for various developer communities discussing terminal session persistence. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Comment |
🚀 Preview Deployment🔗 Preview Links
Preview updates automatically with new commits |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 12
🤖 Fix all issues with AI agents
In `@apps/marketing/content/blog/git-worktrees-for-ai-era.mdx`:
- Around line 382-386: Replace the current references and wording about
worktrees: remove the Pro Git Book - Worktrees bullet entirely, keep the
official Git Worktree documentation link and the `man git-worktree` note, and
change the sentence "The feature has been stable since Git 2.5 (2015). If you
have git, you have worktrees." to a tightened requirement such as "Worktrees
were introduced in Git 2.5 (July 2015); Git >= 2.5 is required to use
worktrees." Ensure the list contains only the official docs and manpage and that
the version requirement explicitly states Git 2.5 or newer.
In `@apps/marketing/content/blog/git-worktrees-history-deep-dive.mdx`:
- Around line 67-75: Update the release date in the section titled "### July
2015: The Feature Arrives" to state the actual Git 2.5.0 release date of July
27, 2015 (instead of July 29), and add a clarifying sentence that the GitHub
blog announcement was published on July 29, 2015; include the GitHub blog URL
(https://github.blog/open-source/git/git-2-5-including-multiple-worktrees-and-triangular-workflows/)
as the source for the quoted text to make the distinction clear.
In `@apps/marketing/content/blog/terminal-daemon-deep-dive.mdx`:
- Around line 73-75: Update the wording that currently reads "Unix Domain Socket
(NDJSON protocol)" to explicitly mention Windows named pipes as an alternative
transport (e.g., "Unix domain sockets or Windows named pipes (NDJSON protocol)")
and make the same change at the other occurrence of the phrase later in the
document so the post clearly indicates cross-platform support.
- Line 388: The markdown link text "Superset desktop source" currently points to
the wrong repo URL "https://github.com/anthropics/superset"; update that URL to
the canonical repository "https://github.com/superset-sh/superset" by replacing
the href in the link on the line containing "*Want to dive deeper? Check out the
[Superset desktop source](https://github.com/anthropics/superset) for the full
implementation.*" so the link text stays the same but the target points to
superset-sh/superset.
In `@reddit/reddit-antigravity-post.md`:
- Line 43: Replace the "[video]" placeholder in reddit-antigravity-post.md with
the actual video URL (e.g., a full https://... link or Reddit-compatible embed
URL) so the post displays the intended video; locate the placeholder token
"[video]" in the file and substitute it with the real video link string.
- Line 27: Replace the placeholder "[video demo]" with an actual,
fully-qualified video URL (e.g., https:// or https://youtu.be/...) ensuring the
link is public and playable; update the reddit post content where the
placeholder appears so the final markdown contains the real video link and
optionally a brief caption describing the demo for context.
In `@reddit/reddit-claudecode-post.md`:
- Line 25: Replace the placeholder text "[video demo — closing app completely,
reopening, session still running]" in the reddit/reddit-claudecode-post.md
content with the actual hosted video URL (e.g., https://...) showing the demo;
ensure the link is a full URL and retains Markdown link syntax if needed (or
plain URL), and confirm it points to the final published video before merging.
- Line 41: Replace the placeholder "[video]" in the reddit-claudecode-post.md
content with the actual video URL to be shared; locate the placeholder token
"[video]" in the post text and substitute it with the final video link
(including the full https://... URL) ensuring the link is correct and clickable
before publishing.
In `@reddit/reddit-geminicli-post.md`:
- Line 16: Replace the placeholder text "[video demo]" in
reddit-geminicli-post.md with the actual video URL (preferably a full https://
link) using Markdown link syntax (e.g., [video demo](https://...)) or an inline
URL so readers can access the demo; ensure the link is valid and points to the
intended demo before publishing.
In `@reddit/reddit-google-antigravity-post.md`:
- Line 16: Replace the placeholder text "[video demo]" in the Reddit post (look
for the exact token "[video demo]" in reddit-google-antigravity-post.md) with
the actual video URL you intend to share; ensure the link is a full, canonical
URL (including https://) and that it is pasted in place of the placeholder so
the post displays the video link correctly.
In `@reddit/reddit-tmux-post.md`:
- Line 10: Update the phrase "open source terminal" to the hyphenated form
"open-source terminal" in the reddit-tmux-post.md content (look for the string
"open source terminal" in the text and change it to "open-source terminal") to
correct the compound adjective grammar.
In `@reddit/reddit-vibecoding-post.md`:
- Line 18: Replace the placeholder "[video demo]" in the reddit post content
with the real video URL using proper Markdown link syntax (e.g., [Video
Demo](https://your.video.url)) so the post displays a clickable demo; locate the
placeholder string "[video demo]" in the reddit/reddit-vibecoding-post.md
content and substitute it with the actual URL and an appropriate label.
| - [Git Worktree Documentation](https://git-scm.com/docs/git-worktree) | ||
| - [Pro Git Book - Worktrees](https://git-scm.com/book/en/v2/Git-Tools-Worktrees) (if it exists in your version) | ||
| - `man git-worktree` | ||
|
|
||
| The feature has been stable since Git 2.5 (2015). If you have git, you have worktrees. |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Git 2.5 release date worktrees introduced
💡 Result:
- Git 2.5.0 release date: July 27, 2015 (official release announcement). [1]
- Worktrees introduced: The
git worktreefeature was introduced as a new (then experimental) command in Git 2.5. [2][3]
Sources: [1] [2] [3]
🌐 Web query:
Pro Git Book Worktrees chapter section
💡 Result:
The Pro Git (2nd Edition) book on git-scm.com doesn’t appear to have a dedicated “Worktrees” chapter/section (no matching book section shows up when searching the Pro Git content on the official site/repo). The Pro Git source repo is here, and it points readers to the online book at git-scm.com/book. [1]
For Git worktrees, the canonical references are the official Git docs instead:
git worktreemanual page:git-worktree - Manage multiple working trees[2]- Git User Manual glossary entry for “worktree” [3]
Sources: [1] [2] [3]
Tighten the Git version requirement and remove the invalid Pro Git reference.
Worktrees arrived in Git 2.5 (July 2015) and the original wording "If you have git, you have worktrees" implies any version will work. The Pro Git book does not have a dedicated "Worktrees" section. Update the references to rely on the official Git documentation and specify the version requirement:
Suggested changes
- [Git Worktree Documentation](https://git-scm.com/docs/git-worktree)
- [Pro Git Book - Worktrees](https://git-scm.com/book/en/v2/Git-Tools-Worktrees) (if it exists in your version)
- `man git-worktree`
-The feature has been stable since Git 2.5 (2015). If you have git, you have worktrees.
+The feature has been stable since Git 2.5 (2015). If you have Git 2.5 or later, you have worktrees.And remove the Pro Git Book reference entirely:
- [Git Worktree Documentation](https://git-scm.com/docs/git-worktree)
- [Pro Git Book - Worktrees](https://git-scm.com/book/en/v2/Git-Tools-Worktrees) (if it exists in your version)
- `man git-worktree`🤖 Prompt for AI Agents
In `@apps/marketing/content/blog/git-worktrees-for-ai-era.mdx` around lines 382 -
386, Replace the current references and wording about worktrees: remove the Pro
Git Book - Worktrees bullet entirely, keep the official Git Worktree
documentation link and the `man git-worktree` note, and change the sentence "The
feature has been stable since Git 2.5 (2015). If you have git, you have
worktrees." to a tightened requirement such as "Worktrees were introduced in Git
2.5 (July 2015); Git >= 2.5 is required to use worktrees." Ensure the list
contains only the official docs and manpage and that the version requirement
explicitly states Git 2.5 or newer.
| ### July 2015: The Feature Arrives | ||
|
|
||
| Git 2.5, released on July 29, 2015, introduced `git worktree` as a first-class feature. The primary author was Nguyễn Thái Ngọc Duy, who had been working on the concept for years. | ||
|
|
||
| The [GitHub blog announcement](https://github.blog/open-source/git/git-2-5-including-multiple-worktrees-and-triangular-workflows/) described the new capability: | ||
|
|
||
| > "Each *linked working tree* is a pseudo-repository with its own checked-out working copy. Its `.git` is actually a file that refers to the history and references from the main repository." | ||
|
|
||
| Notably, the feature shipped with a warning: it was labeled **experimental**, with caveats about potential bugs and a recommendation against using it with submodules. A decade later, these rough edges have been smoothed out. |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Git 2.5 release date July 2015
💡 Result:
Git 2.5.0 was released on July 27, 2015 (the official source tarballs on kernel.org are dated 27-Jul-2015 21:18). [1]
🌐 Web query:
GitHub blog git 2.5 multiple worktrees announcement
💡 Result:
The GitHub Blog announcement you’re looking for is:
- Title: “Git 2.5, including multiple worktrees and triangular workflows”
- Author: Michael Haggerty
- Originally published: July 29, 2015 (later updated December 20, 2021)
- What it announced: Git 2.5 and highlighted the new
git worktreesubcommand for maintaining multiple working trees from a single repository, plus improvements for triangular workflows (including the new@{push}notation). [1]
Source:
[1] GitHub Blog post: “Git 2.5, including multiple worktrees and triangular workflows” https://github.blog/open-source/git/git-2-5-including-multiple-worktrees-and-triangular-workflows/
🌐 Web query:
Nguyễn Thái Ngọc Duy git worktree author
💡 Result:
Nguyễn Thái Ngọc Duy (pclouds@gmail.com) is a principal author of Git’s multiple worktree (“linked checkouts”) implementation—the feature that later became the git worktree workflow—contributing core enabling commits such as “checkout: support checking out into a new working directory” (2014-11-30) and subsequent worktree infrastructure changes (e.g., shared vs per-worktree storage rules in 2018). [1][2]
Sources:
[1] https://git.lorimer.id.au/gitweb.git/log/18b22dbed8e106cfc7899d1c606c1f7c12de6404
[2] https://git.powerel.org/kernel/git/commits/commit/b4ceeef96221b026ea707416dff3480b3e3caf52/Documentation/gitrepository-layout.txt
Correct the Git 2.5 release date from July 29 to July 27, 2015.
The actual Git 2.5.0 release was on July 27, 2015. The July 29, 2015 date in the section header appears to conflate the release with the GitHub blog announcement, which was indeed published on July 29, 2015. Consider clarifying this distinction and adding the source link: https://github.blog/open-source/git/git-2-5-including-multiple-worktrees-and-triangular-workflows/ to allow readers to verify the quoted text.
🤖 Prompt for AI Agents
In `@apps/marketing/content/blog/git-worktrees-history-deep-dive.mdx` around lines
67 - 75, Update the release date in the section titled "### July 2015: The
Feature Arrives" to state the actual Git 2.5.0 release date of July 27, 2015
(instead of July 29), and add a clarifying sentence that the GitHub blog
announcement was published on July 29, 2015; include the GitHub blog URL
(https://github.blog/open-source/git/git-2-5-including-multiple-worktrees-and-triangular-workflows/)
as the source for the quoted text to make the distinction clear.
| │ Unix Domain Socket | ||
| │ (NDJSON protocol) | ||
| ┌──────────────────────────▼──────────────────────────────────────┐ |
There was a problem hiding this comment.
Clarify Windows transport vs Unix sockets.
Since the post calls out Windows support, the “Unix socket” wording can read as *nix-only. Consider naming Windows named pipes explicitly to avoid confusion.
✏️ Suggested wording tweak
- │ Unix Domain Socket
+ │ Unix domain socket / Windows named pipe
│ (NDJSON protocol)
@@
-**Why Unix sockets?** They're fast (no TCP overhead), secure (file permissions), and support backpressure natively through kernel buffers.
+**Why domain sockets/pipes?** They're fast (no TCP overhead), secure (file permissions), and support backpressure natively through kernel buffers.Also applies to: 132-132
🤖 Prompt for AI Agents
In `@apps/marketing/content/blog/terminal-daemon-deep-dive.mdx` around lines 73 -
75, Update the wording that currently reads "Unix Domain Socket (NDJSON
protocol)" to explicitly mention Windows named pipes as an alternative transport
(e.g., "Unix domain sockets or Windows named pipes (NDJSON protocol)") and make
the same change at the other occurrence of the phrase later in the document so
the post clearly indicates cross-platform support.
|
|
||
| --- | ||
|
|
||
| *Want to dive deeper? Check out the [Superset desktop source](https://github.com/anthropics/superset) for the full implementation.* |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Superset desktop repository canonical source anthropics superset-sh
💡 Result:
The canonical (upstream) source repository for the Superset desktop app branded “@superset_sh” (the terminal/orchestrator for CLI coding agents like Claude Code) is:
- GitHub:
superset-sh/superset(this is the repo linked from the official Superset site, and its README shows build-from-source steps for the desktop app). [1][2]
If you meant Apache Superset (the BI/data visualization project), that’s a different project entirely (Apache Software Foundation) and not related to superset-sh. [1]
Sources: [1] [2]
Update repository link to point to canonical Superset source.
The link currently points to anthropics/superset, but the canonical repository for Superset desktop is superset-sh/superset.
Link update
-*Want to dive deeper? Check out the [Superset desktop source](https://github.com/anthropics/superset) for the full implementation.*
+*Want to dive deeper? Check out the [Superset desktop source](https://github.com/superset-sh/superset) for the full implementation.*📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| *Want to dive deeper? Check out the [Superset desktop source](https://github.com/anthropics/superset) for the full implementation.* | |
| *Want to dive deeper? Check out the [Superset desktop source](https://github.com/superset-sh/superset) for the full implementation.* |
🤖 Prompt for AI Agents
In `@apps/marketing/content/blog/terminal-daemon-deep-dive.mdx` at line 388, The
markdown link text "Superset desktop source" currently points to the wrong repo
URL "https://github.com/anthropics/superset"; update that URL to the canonical
repository "https://github.com/superset-sh/superset" by replacing the href in
the link on the line containing "*Want to dive deeper? Check out the [Superset
desktop source](https://github.com/anthropics/superset) for the full
implementation.*" so the link text stays the same but the target points to
superset-sh/superset.
| - spin up isolated workspaces (git worktrees) for different agent tasks | ||
| - crash recovery — at minimum you get your scrollback back | ||
|
|
||
| [video demo] |
There was a problem hiding this comment.
Replace placeholder with actual video link.
The placeholder "[video demo]" should be replaced with an actual video URL before publishing this Reddit post.
🤖 Prompt for AI Agents
In `@reddit/reddit-antigravity-post.md` at line 27, Replace the placeholder
"[video demo]" with an actual, fully-qualified video URL (e.g., https:// or
https://youtu.be/...) ensuring the link is public and playable; update the
reddit post content where the placeholder appears so the final markdown contains
the real video link and optionally a brief caption describing the demo for
context.
|
|
||
| no tmux. no config. just works. | ||
|
|
||
| [video] |
There was a problem hiding this comment.
Replace placeholder with actual video link.
The placeholder "[video]" should be replaced with an actual video URL before publishing this Reddit post.
🤖 Prompt for AI Agents
In `@reddit/reddit-claudecode-post.md` at line 41, Replace the placeholder
"[video]" in the reddit-claudecode-post.md content with the actual video URL to
be shared; locate the placeholder token "[video]" in the post text and
substitute it with the final video link (including the full https://... URL)
ensuring the link is correct and clickable before publishing.
|
|
||
| no tmux, no config, just works. | ||
|
|
||
| [video demo] |
There was a problem hiding this comment.
Replace placeholder with actual video link.
The placeholder "[video demo]" should be replaced with an actual video URL before publishing this Reddit post.
🤖 Prompt for AI Agents
In `@reddit/reddit-geminicli-post.md` at line 16, Replace the placeholder text
"[video demo]" in reddit-geminicli-post.md with the actual video URL (preferably
a full https:// link) using Markdown link syntax (e.g., [video
demo](https://...)) or an inline URL so readers can access the demo; ensure the
link is valid and points to the intended demo before publishing.
|
|
||
| useful for long-running agent tasks where you don't want to babysit the window. | ||
|
|
||
| [video demo] |
There was a problem hiding this comment.
Replace placeholder with actual video link.
The placeholder "[video demo]" should be replaced with an actual video URL before publishing this Reddit post.
🤖 Prompt for AI Agents
In `@reddit/reddit-google-antigravity-post.md` at line 16, Replace the placeholder
text "[video demo]" in the Reddit post (look for the exact token "[video demo]"
in reddit-google-antigravity-post.md) with the actual video URL you intend to
share; ensure the link is a full, canonical URL (including https://) and that it
is pasted in place of the placeholder so the post displays the video link
correctly.
|
|
||
| ## Post | ||
|
|
||
| we're working on an open source terminal ([github.com/superset-sh/superset](https://github.com/superset-sh/superset)) and wanted sessions to survive app restarts by default. no config, just works. |
There was a problem hiding this comment.
Hyphenate “open-source” in the opener.
Small grammar fix for a compound adjective.
✏️ Suggested edit
-we're working on an open source terminal ([github.com/superset-sh/superset](https://github.com/superset-sh/superset)) and wanted sessions to survive app restarts by default. no config, just works.
+we're working on an open-source terminal ([github.com/superset-sh/superset](https://github.com/superset-sh/superset)) and wanted sessions to survive app restarts by default. no config, just works.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| we're working on an open source terminal ([github.com/superset-sh/superset](https://github.com/superset-sh/superset)) and wanted sessions to survive app restarts by default. no config, just works. | |
| we're working on an open-source terminal ([github.com/superset-sh/superset](https://github.com/superset-sh/superset)) and wanted sessions to survive app restarts by default. no config, just works. |
🧰 Tools
🪛 LanguageTool
[grammar] ~10-~10: Use a hyphen to join words.
Context: ... --- ## Post we're working on an open source terminal ([github.com/superset-sh...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
In `@reddit/reddit-tmux-post.md` at line 10, Update the phrase "open source
terminal" to the hyphenated form "open-source terminal" in the
reddit-tmux-post.md content (look for the string "open source terminal" in the
text and change it to "open-source terminal") to correct the compound adjective
grammar.
|
|
||
| also has isolated workspaces — each one is a separate git branch with its own files, so you can have multiple agents working on different features without them conflicting. | ||
|
|
||
| [video demo] |
There was a problem hiding this comment.
Replace placeholder with actual video link.
The placeholder "[video demo]" should be replaced with an actual video URL before publishing this Reddit post.
🤖 Prompt for AI Agents
In `@reddit/reddit-vibecoding-post.md` at line 18, Replace the placeholder "[video
demo]" in the reddit post content with the real video URL using proper Markdown
link syntax (e.g., [Video Demo](https://your.video.url)) so the post displays a
clickable demo; locate the placeholder string "[video demo]" in the
reddit/reddit-vibecoding-post.md content and substitute it with the actual URL
and an appropriate label.
2 participants
Summary
apps/marketing/content/blog/Blog Posts
Test plan
/blogon marketing siteSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.