Hyperia: an actively maintained continuation addressing Hyper’s long-standing backlog

First, thank you to everyone who created and maintained Hyper.

Hyper proved that a terminal built with web technologies could be beautiful, extensible, cross-platform, and genuinely enjoyable to use. Hyperia exists because that foundation remains worth carrying forward. We are grateful to Hyper's maintainers, contributors, plugin authors, issue reporters, and community members for the years of work that made this possible.

That said, Hyper has been functionally inactive for an extended period. Sustained product development largely ended in 2023, the last canary release was published in July 2023, and the repository has been effectively dormant since April 2024. Hundreds of valid bug reports and feature requests remain open without a realistic path to implementation or release.

We have therefore created Hyperia, an independent, actively maintained continuation based on Hyper's April 18, 2024 canary history. Hyperia is not affiliated with or endorsed by Vercel. It preserves Hyper's license and attribution while continuing development under a new name and repository.

We are carrying forward ten high-value areas drawn directly from Hyper's unresolved backlog:

Native tab and split-pane reordering
Named workspace save, restore, import, and export
Clickable file paths with line and column support
Warnings before terminating active processes
Keyboard, mouse, tmux, and full-screen TUI compatibility
A cross-platform accessibility baseline
Find-in-pane improvements and large-scrollback performance
Startup, focus, tab-switching, and scaling benchmarks
Font, ligature, glyph, cursor, and viewport correctness
Declarative CLI-driven windows, tabs, panes, and workspaces

Beyond the backlog, Hyperia has already shipped active cross-platform releases, custom shell profiles, workspace-oriented pane management, embedded web panes, live CWD and foreground-process tracking, improved split layouts, searchable terminal history, and optional agent-native orchestration through MCP.

We will not advertise Hyperia repeatedly across Hyper's backlog or continue posting updates here. Future development, bug reports, feature requests, releases, and discussion belong in the Hyperia repository.

The original Hyper issues remain valuable historical records, and we will continue linking to and crediting them from corresponding Hyperia work. But an open backlog without active triage, implementation, or releases is not a roadmap. Users who want a maintained continuation now have one.

Thank you again to the Hyper community for building the foundation. We'll take it from here.

This issue identifies no files, tests, or entry points to inspect. Read the linked Hyperia repository and its ten linked backlog issues; there is no single completion criterion here because future work is directed to that repository.