superlogical
main 00:00:00
superlogical — session “main” — attached
visitor@sl:~$
[main] 1 pane type help — or don’t, scrolling works too utf-8 · zsh

this terminal works. type , split it with , leave with and come back — it will still be here. that’s the whole idea.

$ sl status --all

One job. Three silos.
Zero shared memory.

interactive
$ ssh prod-box-7
$ vim deploy.yaml
$ connection lost.

Interactive tools assume a person at an interface. Close the lid and the state evaporates — scrollback, context, the half-finished thought.

automatic
job #4812 … FAILED
log rotated away
context: none

Automatic work disappears into jobs and logs. CI, cron, agents working in parallel — running blind, reporting to no one.

production
$ kubectl exec …
permission: separate system
history: elsewhere

As work moves to production it lives behind separate systems and controls, observed through dashboards that forget everything.

Building and operating software today spans local machines, remote hosts, sandboxes, services, and production systems. This work is all related — yet today’s tools divide it into separate systems.

AI makes this fragmentation more visible and costly, but it did not create it. System administration, continuous integration, remote development and collaboration have strained the same boundaries for decades.

$ man superlogical

The missing layer is a
durable session around the work itself.

● interactive ● automatic ● production ■ one durable session

A multiplexer brings multiple independent streams together through a common interface. For us, that means interactive work, automatic work, and production work sharing one well-crafted underlying system — instead of living in separate tools.

One that can span applications and environments, provide relevant context by default, expose structured data and actions, preserve history, and be driven by software while remaining visible and controllable by people.

$ git log --oneline --plan

The plan, shipped like software.

v0.1.0 a1e9c04 building ●

Build an incredible multiplexer.

  • long-lived sessions: close the app, reconnect from another device, pick up exactly where you left off
  • web + native macOS/iOS access from day one
  • live session sharing built in, not bolted on
  • scrollback, selection and scrolling that work natively — the classic papercuts, fixed
v0.2.0 7b3f1d8 planned

Make everything in it composable.

  • structured data and actions over every block of work
  • sessions scriptable by software, observable by people
v0.3.0 c08dd2f planned

Make it safe and operable in production.

  • controls, audit and history that survive the incident review
  • the same session, from laptop to fleet

A terminal multiplexer may sound like a narrow place to start a company. Our vision is much larger — but terminals connect developers, agents, tools, and infrastructure, so it is the right foundation for everything that follows. It will remain excellent at that job, even as it grows to support the second and third parts of the plan.

$ sl share --live

First: a terminal multiplexer
with multiplayer in its bones.

$ man -k founders

People who have shipped
the tools you already trust.

SL-TEAM(1)Contributor ManualSL-TEAM(1)
Portrait of Mitchell Hashimoto

NAME

mitchell — creator of Ghostty, co-founder of HashiCorp

SYNOPSIS

mitchell [ghostty] [hashicorp] [vagrant] [terraform] [vault]

DESCRIPTION

Co-founded HashiCorp and created Vagrant, Terraform, Vault, and more. Spent more than a decade as CEO and CTO from its earliest days through its IPO.

SEE ALSO

mitchellh.com

SL-TEAM(1)Contributor ManualSL-TEAM(1)
Portrait of Jack Pearkes

NAME

jack — first employee, VP of Engineering & R&D at HashiCorp

SYNOPSIS

jack [hashicorp#1] [eng] [r&d]

DESCRIPTION

Helped to create HashiCorp’s first products and hired and led the original engineering team.

SEE ALSO

jackpearkes.com

SL-TEAM(1)Contributor ManualSL-TEAM(1)
Portrait of Alasdair Monk

NAME

alasdair — Head of Experience at Poolside, VP of Design at Vercel

SYNOPSIS

alasdair [poolside] [vercel] [hashicorp] [heroku]

DESCRIPTION

Two decades spent designing and building interfaces for developers, as a senior design leader at HashiCorp and Heroku.

SL-TEAM(1)Contributor ManualSL-TEAM(1)
Portrait of Hector Simpson

NAME

hector — designed apps, services, and agentic experiences at Poolside

SYNOPSIS

hector [poolside] [heroku] [hashicorp] [clearbit] [vercel]

DESCRIPTION

An interface designer and builder who has shipped developer-first products at Heroku, HashiCorp, Clearbit, and Vercel.

The Superlogical founding team seated together outdoors
$ last --founders  ·  four people, ~50 years of developer tools, still logged in

$ sl funders --list

Backed by people who know
what this layer is worth.

beta — waitlist

$ sl join --beta

The beta opens in small batches. Leave an email and we’ll attach you to a session when it’s your turn.

stored on this device for the demo — the real list lives at superlogical.com.

Get $10 off Kimi K3