content: evergreen agent context-switching post and Orca vs Conductor compare page

Merged
KI
3mo ago
+226-0

Summary

  • New blog post switching-between-ai-coding-agents.mdx: how to move a session between AI coding agents, what context is made of, and the fork/resume flags for six agent CLIs.
  • New compare page orca-vs-conductor.mdx, targeting a competitor query cluster that currently has no dedicated page.

Why / Context

This started as "should we turn changelog entries into blog posts?" Search Console says no, so this does the version the data supports instead.

Over the last 3 months on sc-domain:superset.sh:

BucketClicksImpressionsPagesClicks/page
Compare pages5,689230K7180
Blog71638K7102
Changelog entries43417K2716

Changelog entries average 16 clicks and 616 impressions each, because nobody searches for a release announcement. The blog's 102 average is carried by one post (git-worktrees-history-deep-dive, 430 of 716 clicks) that ranks because "when was git worktree introduced" is a real recurring query. The two announcement-shaped blog posts flopped despite being six months old: agent-orchestration-not-another-agent has 1 click on 811 impressions, how-to-get-hit has 0 on 6.

So the lever is demand, not format. Both pages here target queries that already exist.

How It Works

Blog post. Splits context into conversation, working state, instructions, and reasoning, and shows that two of the four travel on their own. Includes a fork/resume reference table for Claude Code, Codex, OpenCode, Grok, Pi, and Droid, which is not compiled anywhere else, and the alt-screen scrollback measurement from #6962 (visible buffer returns 23 history lines where the raw pty stream returns 253; after a pager exits the buffer holds none of 300 lines). Superset appears only in the last section.

Compare page. orca vs conductor already draws 331 impressions and 32 clicks with no dedicated page, and the competitor-vs-competitor pattern already exists (conductor-vs-crystal, warp-vs-conductor). The page also carries conductor competitors as a keyword, a query sitting at 1,883 impressions and 0 clicks.

Manual QA Checklist

  • Both pages render 200 on a local marketing server (next dev, dummy env per the compare-pages recipe)
  • Compare page emits the At a Glance table and auto-generated FAQ JSON-LD (FAQPage)
  • Both appear on their index pages (/compare, /blog) and in the sitemap
  • Frontmatter matches existing convention for each content type
  • No em dashes; no literal { or bare <lowercase that would break MDX
  • Competitor facts checked against current sources on 2026-08-30

Testing

  • bun run lint (exit 0)
  • bun run --cwd apps/marketing lint:prose (Vale: 0 errors, 0 warnings; 3 advisory suggestions kept deliberately, including alex.ProfanityMaybe firing on "trap" in "The scrollback trap")
  • Render check over HTTP as above

Design Decisions

  • Blog post leads with the problem, not the feature. The evidence above says announcement-shaped writing does not earn clicks regardless of which directory it sits in, so the Superset section is last and the fork table is useful even to someone who never installs it.
  • No star count for Orca. Sources disagree (one says 20k, our own note from 2026-08-24 says 52.6k), so the page cites neither rather than printing a number that may be wrong.
  • Conductor is given the win on coordination. Its named team roles, four coordination patterns, and context reinjection on compaction are real advantages, and per our rule about competitor contrasts an invented differentiator would be worse than none.

Known Limitations

  • Neither page has a hero image. The blog index does show cover images, so this post will render without one until someone supplies it.
  • Droid's fork flag is documented but unverified, and the post says so.

Follow-ups

  • The single largest untapped item from the same data is conductor competitors at 1,883 impressions and 0 clicks. conductor-alternative.mdx already targets that keyword and was last updated 2026-07-13, so it ranks but does not convert. Worth a refresh pass separately.

https://claude.ai/code/session_011zKUF9njL63tLUpHmCaGPv


Summary by cubic

Adds two content pages targeting search queries that already draw impressions: an evergreen blog post on switching between AI coding agents and an Orca vs Conductor compare page.

  • The post splits context into conversation, working state, instructions, and reasoning, and compiles fork/resume commands for six agent CLIs into a table not assembled anywhere else.
  • It measures the alternate-screen scrollback trap: 23 history lines from the visible buffer versus 253 from the raw pty stream.
  • The compare page targets orca vs conductor (331 impressions) and carries conductor competitors (1,883 impressions, 0 clicks).
  • Review passes fixed Conductor facts against its docs and blog claims on portability, forking, and scrollback; the Orca pass rewrote the Superset positioning after Orca's docs showed it already covers PR review, design mode, remote hosts, mobile, and custom CLI agents.
  • The surviving contrast against Orca is an exposed MCP server plus TypeScript SDK, Slack dispatch, and the enterprise track.
  • Orca's star count is omitted because sources disagree (20k vs 52.6k); Droid's fork flag is documented but unverified, and the post says so.
  • Neither page has a hero image; the blog post renders without one until supplied.

Summary by CodeRabbit

  • Documentation
    • Expanded the guide for switching between AI coding agents, covering CLI forking, portable files and instructions, transcript replay, terminal buffering, vendor-specific imports, and credential-safety considerations.
    • Updated the Orca versus Conductor comparison with platform support, licensing, agent coverage, pricing, coordination models, mobile app availability, workspace isolation, subscription scope, and Superset’s positioning.