diff --git a/apps/marketing/content/blog/history-of-git-worktrees.mdx b/apps/marketing/content/blog/history-of-git-worktrees.mdx new file mode 100644 index 00000000000..2439ec7ae23 --- /dev/null +++ b/apps/marketing/content/blog/history-of-git-worktrees.mdx @@ -0,0 +1,62 @@ +--- +title: The History of Git Worktrees +description: How git worktrees evolved from a niche feature to the foundation of modern parallel development workflows. +author: Avi Peltz +date: 2025-01-18 +category: Research +--- + +Git worktrees have become an essential tool for developers managing multiple tasks simultaneously. But where did they come from, and why are they suddenly so relevant? + +![Git worktrees visualization](/blog/history-of-git-worktrees/worktrees-visualization.png) + +## The Early Days + +Git worktrees were introduced in Git 2.5 (July 2015) as a way to have multiple working directories attached to a single repository. Before worktrees, developers had two options for working on multiple branches simultaneously: + +1. **Stash and switch** - Constantly stashing changes and switching branches +2. **Multiple clones** - Maintaining separate clones of the same repository + +Both approaches had significant drawbacks. Stashing was error-prone and disruptive. Multiple clones wasted disk space and made it difficult to share local commits between workspaces. + +## How Worktrees Work + +A git worktree creates a new working directory that shares the same `.git` directory as your main repository. This means: + +- All branches and commits are instantly available +- No need to push/pull between directories +- Minimal disk space overhead +- Each worktree can have its own branch checked out + +```bash +# Create a new worktree +git worktree add ../feature-branch feature/new-feature + +# List all worktrees +git worktree list + +# Remove a worktree +git worktree remove ../feature-branch +``` + +## The AI Agent Revolution + +With the rise of AI coding agents, worktrees have found a new purpose. When you're running multiple agents in parallel, each one needs: + +- Its own working directory +- Isolation from other agents' changes +- Access to the full repository history + +Worktrees provide all of this out of the box. That's why Superset uses them as the foundation for parallel agent workspaces. + +## Best Practices + +When using worktrees for parallel development: + +- **Use descriptive paths** - Name your worktree directories after the feature or task +- **Clean up regularly** - Remove worktrees when you're done with them +- **Avoid long-lived worktrees** - Merge or rebase frequently to avoid drift + +## Conclusion + +What started as a niche feature for advanced Git users has become essential infrastructure for the age of AI-assisted development. As coding agents become more capable, the ability to run them in parallel—powered by git worktrees—will only become more important. diff --git a/apps/marketing/content/blog/introducing-superset.mdx b/apps/marketing/content/blog/introducing-superset.mdx new file mode 100644 index 00000000000..bc2f6924721 --- /dev/null +++ b/apps/marketing/content/blog/introducing-superset.mdx @@ -0,0 +1,46 @@ +--- +title: Introducing Superset +description: Run 10+ parallel coding agents on your machine. A new way to work with AI coding assistants. +author: Avi Peltz +date: 2025-01-15 +category: Product +--- + +We're excited to introduce Superset - a new way to work with AI coding agents. + +## The Problem + +Modern AI coding assistants are powerful, but they have a fundamental limitation: you can only run one task at a time. When your agent is working on a complex feature, you're stuck waiting. Context switching between different projects means losing your train of thought. + +## The Solution + +Superset lets you run **10+ parallel coding agents** on your machine. Here's what that means for your workflow: + +- **Spin up new tasks** while waiting for your current agent to finish +- **Quickly switch between tasks** as they need your attention +- **Keep your context** across multiple projects and features + +## How It Works + +Superset uses isolated workspaces powered by git worktrees. Each task runs in its own environment, with its own terminal, its own files, and its own agent context. + +![Superset workspace interface](/blog/introducing-superset/workspace-interface.png) + +```bash +# Create a new workspace for a feature +superset create --branch feature/auth + +# Your agent works in isolation +# Meanwhile, start another task... +superset create --branch feature/dashboard +``` + +## What's Next + +We're just getting started. In the coming weeks, we'll be sharing more about: + +- Deep integrations with popular AI coding tools +- Advanced workspace management features +- Team collaboration capabilities + +Stay tuned for updates. diff --git a/apps/marketing/content/blog/parallel-agents-guide.mdx b/apps/marketing/content/blog/parallel-agents-guide.mdx new file mode 100644 index 00000000000..f3e57916476 --- /dev/null +++ b/apps/marketing/content/blog/parallel-agents-guide.mdx @@ -0,0 +1,144 @@ +--- +title: A Guide to Parallel Coding Agents +description: Learn how to maximize your productivity by running multiple AI coding agents simultaneously. +author: Avi Peltz +date: 2025-01-20 +category: Research +--- + +Running multiple AI coding agents in parallel can dramatically boost your productivity. Here's how to make the most of it. + +## Why Parallel Agents? + +Traditional AI coding workflows are sequential. You ask your agent to do something, wait for it to finish, review the results, and move on. But what if you could: + +1. Start a refactoring task +2. While that's running, begin a new feature +3. Review completed tasks as they finish +4. Context switch without losing progress + +## Setting Up Your Workflow + +### Creating Workspaces + +Each parallel agent runs in its own isolated workspace. Here's how to create one: + +```bash +# Create a new workspace for a feature +superset create --branch feature/auth + +# List all active workspaces +superset list + +# Switch to a workspace +superset switch feature/auth +``` + +