Local-first terminal · macOS + Linux

v0.8.1MIT · 0.8.1 ↗

Why this terminal?
Your tools, built in.

A terminal with a secrets vault, SSH connection manager and API client built in, using your system WebView instead of bundling a browser engine: WKWebView on macOS and WebKitGTK on Linux.

macOS universal · Linux x86_64 · MIT

vm-demo: nocx   ~▦   Keyboard → vm-demo: nocx
claude234+
DEMO SESSION

Your working context, in one window.

  1. Tabs and connections. Your local shell and SSH sessions side by side.
  2. Files. The tree on the right follows the active tab’s directory.
  3. History. Printed output is available after a restart.

Demo project:

– README.md
– examples/
– docs/

Pick up where you left off.

Commands, notes and files stay in the context of your work.

This is an interface model with example content.
No commands are executed here.

›Continue working
A static HTML model of nocx. Demo data; no commands are executed.Try the tabs and the file filter.

Built for the whole workflow

One terminal. Vault, SSH manager and API client included.

System WebView

nocx uses your operating system’s WebView, not a bundled browser engine.

Use the browser engine your platform already provides, without bundling another one.

Secrets vault

Use saved secrets in commands without leaving their values in history.

Keep the secret in the vault; history retains its named reference.

SSH connection manager

Organize hosts into groups and connect with credentials held in your vault.

Find a host by group and connect without copying its credential.

API client

Keep requests, environments and responses together in your workspace.

See the request setup and response at a glance.

No accountNo product telemetryOpen sourceNo cloud service of its own

01 / Close at hand

One tab.
All its context.

Local or over SSH, the sidebar follows your active tab. Files, Git, ports and transfers belong to the machine you are working on.

Run cd and the file tree moves with you. No extra clicks or switching windows to find the directory you are already in.

FILES · /workspace/demo

Your active tab’s files, right beside the terminal.

02 / Pick up where you left off

Close it. Open it.
Keep working.

Your day should not start with rebuilding your windows. nocx restores your tabs, their printed output and your interface layout.

Open tabs✓   restored
Command output✓   readable again
Active tab✓   same place
Window and sidebar✓   as you left them
Running processes—   not resumed

The output comes back, not the running program. You can disable restoration in Settings.

03 / Local by design

Secrets stay
as references.

Store a secret in the vault. Command history keeps a reference in place of its value; when you use the command, nocx resolves the reference after the vault is unlocked.

You typed
TOKEN=<value> ./deploy.sh
↓
nocx keeps
TOKEN=[vault reference] ./deploy.sh
Connection passwords and key passphrases live in the same vault.
↳   No cloud service of its own↳   No cloud sync↳   Encrypted history

04 / Fewer context switches

An assistant where
the work happens.

Ask right in the scrollback. Text, tools and commands stay together in one entry, with every step readable after a restart.

UNDER YOUR CONTROL
You select context → approve → stop
Exact command · machine · tab

You configure the model endpoint. Data retention is your provider’s policy.

An API client.
Your ordinary files.

Import a Postman collection. Each request becomes a separate JSON file in your own folder. Run locally or through an open SSH connection.

COLLECTION /
├── health.json
├── users.json
└── environments/

Request, folder and environment variables. Secrets in fields are stored as opaque references.

A prompt that is an editor.

CodeMirror 6, syntax highlighting, command and path completion, and saved snippets.

❯   cd internal/session/Tab ↹

05 / Get started

Your next
terminal.

No sign-up. Download nocx for your system and keep working with your existing hosts.

v0.8.1, released 2026-11-12 · MIT

Early release. No formal support.

macOS · Homebrew

Install the cask from the third-party tap. It clears macOS quarantine after installation. Read the tap README before installing.

brew install --cask shady2k/nocx/nocx

Direct GitHub downloads still need the manual quarantine step in the README.

Open release↗

Linux · x86_64

Install with the nocx installer, which supports x86_64 Linux. It refuses macOS and unsupported architectures; macOS users should use Homebrew.

curl -fsSL https://nocx.dev/install.sh | sh

Or install manually from the AppImage:

chmod +x nocx-*-linux-amd64.AppImage
./nocx-*-linux-amd64.AppImage

x86_64, glibc 2.35+. Ubuntu 22.04+, Debian 12+, Fedora 39+, RHEL 9+ and Arch.

Open release↗

Updates use an Ed25519-signed manifest. This checks integrity; it is not Apple notarization. Why this approach ↗   Rollback instructions ↗

Before your first launch

Can I bring my SSH connections?

Yes. nocx imports profiles and groups from Tabby. It can resolve aliases from ~/.ssh/config when connecting, but does not import that file. Passwords and key passphrases can be linked from the vault.

What leaves my machine?

nocx connects to your hosts, your configured assistant endpoint and its own update checks. It has no cloud service of its own, product telemetry or cloud sync.

What is it built with?

Go for PTY, SSH and sessions; a backend-painted cell renderer for the terminal; CodeMirror 6 for input; SolidJS for the interface; Wails v3 for the desktop shell.

Does the API client have limits?

Responses are read up to 2 MiB. Bytes matching a stored secret are removed before display. A collection cannot access the password behind an SSH profile.