Every release of NEXO Brain makes your agent a little more capable. Better memory retrieval, tighter security, smoother install. Incremental gains that compound over time. But v2.6.7 is different. This time, your agent can start giving back.

Two headline features define this release: a new contributor evolution system that lets any NEXO installation propose improvements to the core product, and personal MCP plugins that let you extend NEXO with custom tools that survive updates. Together, they represent a shift in how we think about the relationship between an individual NEXO instance and the project as a whole.

Public Contributor Evolution

Here is the idea: every NEXO installation runs on a real machine, solving real problems, every day. Your agent discovers workarounds, optimizes patterns, and builds up knowledge about what works and what does not. What if that experience could flow back to improve the product for everyone?

That is what contributor evolution does. It turns every NEXO instance into a proposal node — a machine that can think, prepare, and submit improvements, but never deploy them unilaterally.

How it works

Contributor evolution is strictly opt-in. You enable it during install or by running:

nexo contributor on

Once enabled, NEXO can prepare proposals in an isolated checkout of the public repository. This checkout is completely separate from your personal runtime — your data, your prompts, your logs, and your secrets are never part of any proposal. The isolation is enforced at the file-system level, not by convention.

When your agent identifies a potential improvement — a new utility function, a better default, a bug fix it discovered — it prepares the change in the isolated checkout and opens a single Draft Pull Request on GitHub. Then it pauses. No further proposals are submitted until the open one is resolved (merged or rejected).

This is deliberate. The gate is human review, not arbitrary size limits or frequency caps. Every proposal gets a pair of human eyes before it touches the codebase. Your machine can think freely, but a maintainer decides what ships.

What is blocked

The guardrails are explicit. Proposals cannot include:

The philosophy is simple: proposals contain code, not context. Your agent contributes engineering, not surveillance.

Personal MCP Plugins That Survive Updates

This one comes directly from user feedback. People wanted to add custom MCP tools to NEXO — a tool to query their company's internal API, a shortcut for a project-specific workflow, an integration with a niche service. The problem: every time NEXO updated, custom tools in the core directory got overwritten.

The solution is a dedicated plugin system. Run:

nexo_personal_plugin_create

This scaffolds a new plugin inside NEXO_HOME/plugins/ with a standard structure and an optional companion script. Plugins in this directory are loaded automatically at startup and are completely invisible to the update process. They persist across every nexo update, forever.

Personal plugins are intentionally kept separate from core. They never become part of the main NEXO distribution. If you build something that belongs in core, use the contributor evolution system to propose it. Otherwise, your plugin lives in your namespace, under your control, on your schedule.

Example use cases

Smoother Install and Better Memory Continuity

Not every change needs a headline. Some of the best improvements in 2.6.7 are the ones you feel more than you notice.

Install and update progress: Previously, npx nexo-brain and nexo update could look frozen during longer operations. Now both show live progress indicators so you always know what is happening.

Diary time window: nexo_session_diary_read(last_day=true) now returns a ~36-hour window instead of truncating strictly at midnight. If you worked late last night and pick up early this morning, the context carries over seamlessly. No more losing the thread because a calendar day changed.

Auto-close diary promotion: When a session ends without an explicit diary write, the auto-close handler now preserves more context — goals, next steps, and reasoning chains that previously got lost. The promoted diary entry is richer, so the next session starts with a better picture of where things left off.

These are small changes individually. Together, they make daily use noticeably better. The kind of polish that turns a tool you use into a tool you rely on.

Install or update

New install:

npx nexo-brain

Existing installation:

nexo update

Full changelog available on GitHub Releases.