Nosis

Nosis is a lightweight personal agent runtime: per-session execution boundaries with OS-level sandboxing, computer use, a full built-in toolset, Skill / Plugin…

LLM Mart 2 views 2.4k listing impressions

Nosis is an open-source, lightweight personal agent application. It provides local workspace operations, human approval, session persistence, context management, long-term memory, plans, subagents, scheduled tasks, and Skill / Plugin / MCP extensibility — with a TUI, a GUI, and Feishu messaging access.

TUI ───────────────────────── Bridge ── agent_runtime ── agent_core
nosis-server
├─ HTTP / WebSocket (optional) ── GUI
├─ IM (Feishu)
└─ Session Host ── Bridge ── agent_runtime ── agent_core
  • agent_core provides frontend-agnostic agent mechanisms.
  • agent_runtime reads application configuration and assembles the Core into a runnable instance.
  • Bridge runs as a standalone process and is the only channel through which a frontend drives the Runtime.
  • The TUI, GUI, and messaging hosts share execution state and interaction semantics through the Bridge protocol; the Bridge subprocess channel uses newline-delimited JSON.

Key capabilities

  • Controlled local execution: A session supports three permission presets — Ask for approval, Workspace Access, and Full Access. Shell enters the workspace sandbox or the host environment according to scope, while file tools are always confined to the current workspace.
  • Desktop automation: The main agent can observe and operate the visible desktop through computer_screenshot and computer_action, covering screenshots, clicks, drags, scrolling, key presses, and text input. Both tools are on by default and visible only to the main agent, and each call is confirmed according to the current permission preset. Actions return a screenshot by default and can skip it with screenshot: false. On Windows the tools also support visible-window crops and window-relative input. Pass the latest screenshot path as observation and use its hwnd:<decimal> for a window-scoped action.
  • Web research: web_fetch reads public pages directly or via DeepSeek; web_search, when enabled, queries DuckDuckGo by default and can switch to Exa or DeepSeek.
  • A complete agent loop: streaming responses, tool batches, context compaction, steer, cancel, plans, and background jobs.
  • Resumable sessions: conversation and execution events are written to an append-only JSONL journal, and the TUI and GUI can read the same kind of session.
  • Memory and scheduled tasks: global and workspace-scoped long-term memory, plus one-shot, interval, and cron tasks.
  • Models and media: OpenAI-compatible endpoints use the native OpenAI SDK; other routes and image generation use LiteLLM. Providers can be routed independently for the main agent, vision, image generation, auxiliary model calls, and each subagent role.
  • Extension system: standalone skills, skills / agents / MCP / command hooks provided by plugins, and standalone MCP servers.
  • Multiple frontends: the TUI suits terminal workflows; the GUI offers multi-session management, attachments, a file tree, settings, memory, and scheduled tasks; Feishu supports workspace and session selection, streaming text, questions, and approval cards.

Quick start

Requirements: Python >= 3.11, Node.js >= 22, and uv.

git clone https://github.com/EvannZhongg/Nosis.git
cd Nosis
npm install
npm run build
uv tool install --editable ".[server]"

To enable HTTP / WebSocket access in the project environment, install the server extra:

uv sync --extra server

Start the TUI once in the current directory:

nosis

The first launch initializes ~/.nosis/. After quitting the TUI, create ~/.nosis/.env and fill in the environment variables required by the default provider, for example:

OPENAI_KEY=your-api-key

Then restart the TUI:

nosis

Or start the shared GUI / IM server:

nosis-server

The GUI listens on http://127.0.0.1:8737 by default.

From the project's README.

Comments (0)

Sign in to join the conversation.

No comments yet.