Launch HN: Superset (YC P26) – IDE for the agents era

Original Article ↗ Hacker News Discussion ↗

Positioning vs Other Agent/IDE Tools

  • Frequently compared to Cursor, Conductor, Antigravity, Orca, Zed, t3, Emdash, Harness, etc.
  • Differentiators claimed:
    • Terminal-first, optimized for CLI agents (Claude Code, Codex, Opencode, etc.) rather than a custom SDK or chat-centric UI.
    • Flexible “bring your own harness” rather than prescribing one agent framework.
    • Worktree-based workflow, with setup/teardown scripts for per-branch environments.
    • Focus on scaling many concurrent agent sessions and treating the tool as an “agent factory.”

User Experience & Workflow

  • Users who like it emphasize:
    • Managing many worktrees and agent sessions (dozens) without losing context.
    • Easier context switching and long-lived task branches that can be resumed later.
    • Terminal-like feel; if it runs in a TUI (including vim), it runs inside the app.
  • Others find it heavy and overwhelming compared to tmux/iTerm2/Zellij/Neovim setups and say their existing Linux/terminal workflow plus an agent is “enough.”

Remote Workspaces & Infrastructure

  • Remote workspaces are a major interest: run agents on remote dev boxes and keep sessions alive without local machines.
  • There’s demand for:
    • Port forwarding / browser access to per-worktree environments.
    • Better latency (suggestions like mosh).
    • Easy scripts to spin up isolated infra (e.g., docker stacks) per worktree and reserve ports.

Stability, Performance, and Licensing

  • Some users report glitches: laggy remote typing, terminal rendering issues (possibly WebGL), freezes, and high resource usage (Electron-heavy, multi-GB).
  • There is an ELv2 license and a cloud backend; sign-in is required for the official builds to enable things like Linear/Slack, multiplayer, and remote workspaces.
  • Monetization is via team features and cloud; some feel $20/month is steep or would prefer one-time purchase.

Skepticism About Multi-Agent “Swarms”

  • Debate over value of multi-agent or “agent swarms”:
    • Supporters use multiple agents for parallel spikes, bug triage, and small tasks, emphasizing human review and supervision.
    • Critics argue multi-agent workflows yield diminishing returns, require constant human oversight, and don’t reflect how robust software is actually built.