Superlogical

A new startup, Superlogical, aims to build a “multiplexer for all work” – essentially a next‑generation terminal multiplexer that unifies local development, remote environments, CI, and AI agents into durable, shareable sessions across devices. Commenters compare the vision to tools like tmux, zellij, herdr, and Kubernetes-backed agent orchestration, with some excited about fixing long‑standing terminal UX and context‑sharing issues, and others unconvinced this solves problems beyond what existing tools and window managers already provide. Funding, investor choices, and the company’s non‑remote hiring policy also draw scrutiny, raising broader questions about VC influence, ethics, and how much ambition is appropriate for core developer tooling.

Overall Reception & Vision

  • Many are excited, seeing this as a “next‑gen tmux” or agent‑centric work environment that unifies local dev, CI, agents, and production operations in one persistent “session” layer.
  • Others find the announcement very vague; phrases like “multiplexer for all work” and “durable session around the work” don’t clearly convey what users will actually do differently day‑to‑day.
  • Some infer a longer‑term goal closer to a remote, multi‑device IDE / agent workspace with shared state, not just a terminal tool.

Comparison to Existing Tools

  • Frequent comparisons to tmux, screen, zellij, herdr, cmux, Orca, agent orchestrators, Emacs, NixOS dev shells, and cloud devboxes.
  • Supporters argue there is room for:
    • Better UX (scrollback, selection, gestures, mouse, notifications).
    • First‑class AI agent workflows (status, coordination, automation).
    • Standardized, modern terminal protocols and extensions.
  • Skeptics say multiplexers plus SSH already work well, and that many “agent multiplexers” add little beyond tmux plus scripting.

Architecture & Implementation Speculation

  • Confirmed: built on libghostty as a public dependency; code in Go, Swift, Zig; Nix mentioned; Tailscale integration noted.
  • Some expect a server‑backed, distributed‑state multiplexer: tmux‑like sessions that can be attached from multiple devices, possibly orchestrating containers/Kubernetes, but details are unclear.
  • Others point out similar personal projects already attempting distributed sessions across machines with shared state.

Funding, Hiring, and Business Model

  • Large roster of investors draws attention; some see it as validation of the space, others as evidence of a cliquey VC ecosystem that can push tools into companies regardless of merit.
  • Debate over why a wealthy founder would take so many investors; suggested reasons include accountability, recruiting, and strategic advice.
  • Company is not remote‑first; hiring is limited to LA, NY, London with in‑office expectations, prompting debate about work–life balance and “lifestyle business” versus hyper‑growth.

Security, Privacy, and Operations Concerns

  • Concerns that a central, powerful multiplexer could become a “super‑root” over infrastructure; countered by arguments that it only operates within existing permissions and RBAC.
  • Questions about whether this becomes a hosted service (subscription, data collection, AI training on user sessions) and how it fits with strict production controls and compliance regimes.

UX & Meta Reactions

  • ssh‑based careers page is widely noted as clever and on‑brand, but criticized for poor accessibility on high‑latency/mobile connections.
  • Design details (gradient, disappearing scrollbar) are polarizing: some praise the aesthetics; others find it unusable.
  • Thread contains side debates about certain investors’ political views and whether that should influence adoption of the tool.