Noi

Noi implements Electron-based multi-window architecture where each window maintains completely isolated browser sessions, preventing cookie/localStorage/cache bleeding between contexts. Users can spawn parallel browsing contexts (e.g., one window for ChatGPT, another for Claude) without shared state, enabling clean parallel workflows. Session isolation is enforced at the Chromium engine level through separate BrowserContext instances per window.

Noi's NoiAsk system stores all prompts, AI personas, and conversation templates locally in JSON-based configuration files (noi_awesome.json) with real-time synchronization across all open windows via IPC messaging. Prompts are organized hierarchically by AI service and category, with support for template variables and persona definitions. Changes to prompts in one window trigger immediate updates in all other windows through a pub/sub event system.

Noi's proxy configuration system allows users to define global or per-service proxy settings that route HTTP/HTTPS requests through custom endpoints. The proxy configuration is stored in noi.space.json and supports filtering rules for selective request routing. This enables users to monitor, log, or filter AI service requests through intermediary proxies without modifying individual service configurations.

Noi's sidebar provides a customizable navigation interface that displays bookmarked AI services, custom shortcuts, and workspace items. The sidebar is configured through noi.space.json and supports drag-and-drop reordering, custom icons, and grouping of services. Clicking sidebar items opens the corresponding service in the main browsing area, enabling quick context switching between AI services.

Noi implements tab and window management that allows users to open multiple tabs within windows and manage multiple windows simultaneously. Tab state (URL, scroll position, form data) is partially persisted, and window configurations (size, position, open tabs) are saved to enable recovery after application restart. The system tracks open windows and tabs through a state management layer that syncs with local storage.

Noi provides a settings interface for managing application preferences including theme, language, proxy configuration, and workspace settings. Settings are stored in local JSON configuration files (~/.noi/config) and applied immediately without requiring application restart. The settings system supports both UI-based configuration and direct JSON file editing, enabling both GUI and programmatic configuration management.

Noi includes NSH, a native shell terminal integrated directly into the application that executes local commands and scripts without spawning external terminal windows. The terminal is implemented as an Electron child process that captures stdout/stderr and renders output in the UI, supporting shell scripting, environment variable access, and integration with the CLI interface. Commands can be executed in the context of Noi's workspace, enabling automation of AI interactions.

Noi exposes a command-line interface (noi command) that allows external tools and scripts to interact with the application, trigger prompts, and manage workspaces from the shell. The CLI is implemented as an Electron IPC bridge that communicates with the main process, enabling programmatic control of Noi's features without GUI interaction. External tools can invoke AI prompts, manage windows, and access local data through standardized CLI commands.

Noi provides a unified browsing and interaction layer for multiple AI service providers (ChatGPT, Claude, Copilot, Gemini, Deepseek, Qwen, Grok, Perplexity) through pre-configured bookmarks and custom URL support. Rather than implementing native API integrations, Noi acts as a specialized browser that loads each service's web interface in isolated sessions, allowing users to interact with all services through a consistent UI. The application includes service-specific configurations and proxy support for routing requests through custom endpoints.

Noi maintains a local SQLite or JSON-based history database that tracks all browsing activity across windows and sessions, including URLs, timestamps, and page titles. The history system supports full-text search across visited pages, allowing users to quickly find previous AI interactions and conversations. Session recovery functionality enables users to restore previous browsing states, including open windows and tabs, from stored history snapshots.

Noi's configuration system allows users to define custom 'spaces' (workspace configurations) via noi.space.json files that specify which AI services, tools, and URLs are available in each space. Spaces can include custom items (bookmarks, shortcuts) and service configurations, enabling users to organize their workflow into context-specific environments. The configuration is stored locally as JSON and can be version-controlled or shared across machines by copying configuration files.

Noi implements a Chrome extension compatibility layer built on Electron's native extension APIs, allowing users to install and run Chrome extensions within the application. The extension system provides bindings for common extension APIs (tabs, storage, messaging) while maintaining isolation between extensions and the main Noi application. Extensions can access Noi's browsing context but cannot directly access local data or prompt management systems.

Noi implements a comprehensive localization system using JSON-based language files (noi.lang.json registry) that support multiple languages with runtime language switching without application restart. The localization system covers UI strings, error messages, and documentation, with a structured translation file format that enables community contributions. Language selection is persisted in local configuration and applied immediately across all open windows.

Noi provides a theme system that supports light and dark modes with customizable color schemes, implemented through CSS variables and local configuration storage. Theme preferences are persisted in the application settings and applied consistently across all windows and UI components. Users can select from built-in themes or define custom color schemes by editing theme configuration files.