LIFEHUBBER
Theme

AI Resources

nanobot

GitHub stars: 48.3K GitHub forks: 8.5K Declared license: MIT: MIT Last pushed September 18, 2026: Pushed today
Stats from GitHub

nanobot is a GitHub project from HKUDS presented as a lightweight, self-hosted personal AI agent that can run through a browser workbench, native terminal client, or connected chat apps.

The v0.3.5 release lets the browser and terminal use the same gateway and saved conversations. It adds resumable terminal sessions, grouped browser conversations, temporary chats, session mentions, clearer automations, and more visible context use. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

Self-hosted personal agent project

nanobot combines a browser workbench, native terminal client, chat-app connections, tools, long-term memory, model routing, scheduled automation, an SDK, and an OpenAI-compatible API around one agent runtime.

Why it stands out

One workspace across several interfaces

The v0.3.5 release makes saved conversations easier to continue across the browser and terminal. Sessions can be resumed, forked, inspected, mentioned from other sessions, or detached from the terminal while the same gateway keeps the runtime together.

Availability

GitHub project with packaged releases

The repository, documentation, and PyPI package cover local and server-side setup. PyPI provides v0.3.5 packages for supported macOS, Linux, and Windows systems and still classifies the project as Alpha.

Why it matters

What makes it useful

nanobot lets readers inspect how one personal-agent runtime can keep conversations and tools available across a browser, terminal, and chat apps while showing context use, file activity, automation runs, and session history.

Notable points

What stands out

HKUDS released v0.3.5 on 15 September 2026. Its notes emphasize a native terminal workbench, shared saved conversations, browser multitasking, clearer automations, visible context use, portable plugins, remote MCP sign-in, mobile improvements, and tighter runtime boundaries.

Before using

What to review

Which providers, channels, model presets, and fallback paths match the intended setup.

What messages, files, credentials, and workspace data each provider or channel can access, where they are stored, and how that access can be removed.

The project's setup requirements, including Python 3.11+, package installation, gateway setup, configuration files, supported terminal packages, and channel-specific dependencies.

The PyPI Alpha classification and project-reported release notes before relying on it for important or sensitive workflows.

The v0.3.5 upgrade notes before replacing an existing install: session storage moves, old and new versions should not write the same workspace together, verified Email needs an explicit receiver trust anchor, and the last attached interactive client can stop an on-demand gateway.

The host-side workspace and access setting for remote projects. The release notes say remote clients require Restricted access and cannot enable Full Access.

Reader fit

Who may find it relevant

Readers comparing lightweight personal-agent projects with WebUI, SDK, provider, and channel work.

People testing how an agent carries saved sessions across interfaces, handles longer work, exposes context use, and connects tools or chat apps.

Less relevant for readers who mainly want a finished consumer-facing assistant with minimal setup.

Editorial note

Why LifeHubber lists it

LifeHubber lists nanobot because one small agent runtime can carry saved work across a browser, terminal, and chat apps while keeping sessions, context use, tools, and automations visible. Readers can decide whether that continuity is worth the provider, channel, credential, and workspace access they must configure.

Source links

Source materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

What to explore next

Decide what should survive beyond one agent session.

nanobot focuses on steadier sessions, runtime controls, tools, and channels. These next steps compare persistent memory, readable learned skills, and project records that remain usable outside the agent.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

See what’s moving