neomjs/neo

Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link,...

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 21st, 2026
Created on November 10th, 2019
Open Issues & Pull Requests: 159 (-4)
GitHub issues: Enabled
Number of forks: 242
Total Stargazers: 3,282 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 2.3 days
90th percentile: 9.2 hours
Tracked items: 8,241

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 59% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Almost all tracked open issues have seen activity in the last three months. 99% of issues opened in the past year have since been closed. Three people close 97% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 156
New in 7 days: 174
Closed in 7 days: 155
Avg open age: 165 days
Stale 30+ days: 83
Stale 90+ days: 21

Recent activity

Opened in 7 days: 165
Closed in 7 days: 144
Comments in 7 days: 22
Events in 7 days: 209

Top labels

  • ai (6,602)
  • enhancement (5,173)
  • bug (2,354)
  • architecture (2,204)
  • documentation (1,007)
  • testing (942)
  • model-experience (833)
  • refactoring (576)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Neo.mjs is a framework for building AI-driven applications where multiple language models collaborate through shared memory and reasoning systems to inhabit and autonomously improve live applications.

The project addresses the limitation of single-agent AI systems by orchestrating a swarm of models from different providers—Claude, Gemini, GPT—that share reasoning through Active Hybrid GraphRAG and long-term memory. Rather than treating AI as a chat interface, Neo.mjs embeds agents directly into running applications through its Neural Link interface, allowing them to inspect semantic runtime state, mutate UI and data in real time, and operate as collaborators within the application itself. The swarm autonomously executes the full engineering lifecycle: ideating features, building implementations, cross-reviewing code, running DreamService cycles to adjust priorities, and closing self-healing loops where runtime failures and architectural issues feed back into memory and graph topology for continuous improvement.

Adoption suits teams building production applications that need autonomous AI engineering capabilities beyond conversational interfaces. The framework is designed to work with existing codebases regardless of the training data of the underlying models. The project explicitly positions itself against the industry pattern of deploying single agents, arguing that a coordinated swarm catches problems no individual model can identify in itself.

The project maintains an active development pace with substantial throughput in merged contributions and closed issues. The codebase is self-maintained by the swarm itself, demonstrating the framework's core capability in practice. Development spans multiple AI integration patterns including agent memory systems, knowledge graphs, semantic search, and multi-agent coordination through web workers and MCP server implementations.