Skip to content

Terminal frontend landscape and NMSh product boundary #179

Description

@raiseCatError

Write a concise product/architecture research note comparing adjacent categories: Warp, Wave, Fish/Nushell/Xonsh, tmux/Zellij/TUIOS, Charm ecosystem, OpenTUI/Ink/Ratatui/Textual, prompt tools and history tools.

Document what overlaps with NMSh, what does not, and why NMSh's boundary remains useful: a terminal-agnostic frontend over an existing real shell, with an owned composer, semantic transcript, provider ecosystem, deep customization, persistent/resumable sessions and integration rather than replacement.

This is not a winner-ranking or marketing table. References inform interaction patterns; they are not runtime dependencies or code to copy. NMSh stays TypeScript-first and is not a terminal emulator, replacement shell language or full multiplexer.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:compatibilityCompatibility with CLI/TUI toolstype:researchResearch or investigation task

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions