# lencx/Noi: a multi-window AI browser with session isolation and a built-in terminal

> Noi is a TypeScript desktop application that puts ChatGPT, Claude, Gemini and other AI chats into isolated windows, keeps prompts and history on-device, and adds a CLI that other coding agents can drive.

**lencx/Noi** — 🚀 Less chaos. More flow.

- Repository: https://github.com/lencx/Noi
- Website: https://noib.app
- Stars: 9,060 · Forks: 711
- Language: TypeScript
- License: not declared
- Published: 2026-09-14 · Updated: 2026-09-14 · Language: en
- Canonical page: https://hysenlabs.com/projects/lencx-noi

## What Noi is for: many AI chats, one workspace

The README opens with a positioning line, "Less chaos. More flow", and the feature list explains what that means in practice. Noi is a desktop application that hosts AI chat services as windows rather than browser tabs. The topics attached to the repository name the services it targets: ChatGPT, Claude, Copilot, DeepSeek, Gemini, Grok, Perplexity and Qwen. The audience is anyone who already juggles several of those at once and has felt the cost of doing it in one browser profile.

The problem it addresses is context bleed. When several assistants live in the same browser, they share cookies, logins and history, and a prompt you wrote for one is buried in a tab you closed an hour ago. Noi's answer is structural: multi-window management so workspaces sit side by side, session isolation so each context stays separate, and local-first storage so history, prompts and settings stay on the device. That is a different bet from the aggregator approach, which routes every model through one API key and one interface. Noi keeps the original web interfaces and separates them instead of merging them.

## Multi-window management and session isolation

The two features do different jobs. Multi-window management is about screen layout: run parallel workspaces side by side instead of switching tabs. Session isolation is about state: keep contexts clean, separated and predictable, in the README's wording. The combination is what makes the window count useful rather than noisy. If two windows shared a login, running them side by side would create the same confusion as tabs.

The trade-off is worth naming. Session isolation typically means separate storage per context, so a login you perform in one workspace does not carry into another. That is the point, but it also means signing in repeatedly when you add a workspace, and it means your history is scattered across those contexts rather than searchable in one place. The README does not describe how to export a session, move one between machines, or reset one. Anyone who needs a single auditable log of every prompt they have sent should treat that silence as a real limit, not an oversight to work around later.

## Prompt management, themes and the built-in terminal

Prompt management for AI chats is described as organizing, reusing and iterating on workflows. The repository has a top-level prompts/ directory, which suggests the shipped prompts are files in the project rather than entries in a database, though the README does not document a format. Multiple themes and visual styles are listed as a feature, and the repository carries a locales/ directory, so the interface is localized. The README includes a section for Chinese users pointing to a WeChat account for discussion, which is consistent with that localization.

The built-in terminal is the feature that changes the character of the application. It is described as being for fast local commands, scripts and tooling, which means Noi is not only a viewer for chat pages. You can run something in the same window where you are reading the output of an assistant. That is convenient, and it is also a larger trust surface: a terminal embedded in an application is a terminal, and the README does not describe a sandbox or a permission model around it.

## Installing Noi and running a first session

The README does not give a package-manager install. It points to the releases page, with a link to the v1.1.0 tag, and says "Download...". The releases list shows v1.1.0 published on 2026-01-15, v1.0.0 on 2026-01-06, and v0.4.0 back on 2024-03-25. So the first step is to open the release for your platform and install the build from there. The repository topics include both macos and windows, and the related searches include a query for an exe, so Windows builds are what people look for.

After installing, the first useful thing is to open two workspaces and sign in to a different service in each, which is the session isolation behaviour in action. The second is the CLI. The README describes a `noi` CLI command that lets tools like Claude Code, Codex and Gemini CLI control Noi, and notes that more commands are coming. That phrasing matters: the command set is explicitly incomplete, so check the release notes for what the current version actually exposes before building anything around it. The README does not list the available subcommands or flags, so check the release notes for the command surface your build ships with. If the binary is not on your PATH after installation, look in the application's resources directory, which is where the repository keeps bundled assets.

## Where Noi is the wrong tool

Noi is the wrong choice if you need a stable programmatic interface. The CLI is described as having more commands coming, which is a statement about an unfinished surface, not a guarantee. Anything you script against it today may need rewriting.

It is also the wrong choice if you need to know the licence before you deploy it. The repository metadata does not identify one, and the README does not discuss licensing at all. For personal desktop use that may not matter. For anything inside a company, it is a blocker until someone resolves it, because a project with no stated licence does not grant the permissions a company typically needs.

A third case: if your workflow is one assistant and one browser tab, Noi adds windows, a terminal and a session model you will not use. The multi-window design is the product, and without a reason to run several contexts at once there is nothing here that a normal browser does not already do.

## How Noi differs from an API aggregator like Chatbox

The obvious comparison is an aggregator such as Chatbox, which puts many models behind one interface. The difference is architectural, not cosmetic. An aggregator asks you for API keys and sends requests itself, so every conversation lands in one store and one UI, and the model list is whatever the aggregator supports. Noi does the opposite: it keeps the vendors' own web interfaces and separates them into isolated windows. You get the full product each vendor ships, including features that never appear in an API, and you give up the single unified history.

That choice also moves where your data lives. With an aggregator, the request path runs through the aggregator's process. With Noi, the chat happens in the vendor's own page inside Noi's window, and Noi's local-first claim covers history, prompts and settings rather than the conversations themselves. If your reason for using a desktop client is to keep conversations off a vendor's servers, Noi does not do that, and the README does not claim it does.

## Maintenance, releases and what to verify before adopting

The repository is not archived, and the last push was on 2026-08-21. The release history is uneven: two releases in January 2026, then nothing in the list until this article's window. The gap between v0.4.0 in March 2024 and v1.0.0 in January 2026 is the more useful signal, because it shows the project can go a long time between tagged versions. Code activity and release cadence are not the same thing here, and a user planning an upgrade path has to read both.

Upgrade cost is hard to estimate from the README. It does not document a migration path, a data directory, or a backup procedure for the local history and prompts. Session isolation makes that worse rather than better, because state is deliberately spread across contexts. Before relying on Noi, find out where it stores its data on your platform and confirm you can copy that directory. On the licence question, the repository does not state one, and the website at noib.app is the place to check whether that has changed; do not assume a permissive default.

## Conclusion

Noi fits people who keep several AI chats open at once and want each one in its own window with its own session, plus a terminal in the same application. It does not fit anyone who needs a documented data format, a published licence, or a stable CLI surface, because the README does not describe those. Before adopting it, check the licence situation yourself, confirm the v1.1.0 release has a build for your operating system, and try the noi CLI against one of your existing tools to see whether the command set covers what you need.

## FAQ

### What is lencx/Noi?

It is a desktop application that runs AI chat services in separate windows with isolated sessions and local-first storage for history, prompts and settings. The README describes it as an interaction-first workspace with multi-window management, a built-in terminal and a `noi` CLI.

### How do I install Noi?

The README does not give a package-manager command. It links to the releases page, currently the v1.1.0 tag published on 2026-01-15, and says to download from there. Choose the build for your platform; the repository topics list both macos and windows.

### Does Noi have a command line interface?

Yes. The README describes a `noi` CLI command that lets tools like Claude Code, Codex and Gemini CLI control Noi, and states that more commands are coming. The README does not list the available subcommands or flags, so check the release notes for what your build exposes.

## Sources

- [Issues](https://github.com/lencx/Noi/issues)
- [lencx/Noi on GitHub](https://github.com/lencx/Noi)
- [Project website](https://noib.app)
- [README](https://github.com/lencx/Noi/blob/main/README.md)
- [Releases](https://github.com/lencx/Noi/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/lencx-noi