Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Modulus

Cross-repository knowledge orchestration for coding agents

Details

External ID
47327351
Source
HN
Company
—
Product
Modulus
Website domain
modulus.so
Launched
March 10, 2026
Cohort
—
Upvotes
15
Upvotes percentile
0.6845018450184502
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Hello HN, we're Jeet and Husain from Modulus (https://modulus.so) - a desktop app that lets you run multiple coding agents with shared project memory. We built it to solve two problems we kept running into:- Cross-repo context is broken. When working across multiple repositories, agents don't understand dependencies between them. Even if we open two repos in separate Cursor windows, we still have to manually explain the backend API schema while making changes in the frontend repo.- Agents lose context. Switching between coding agents often means losing context and repeating the same instructions again.Modulus shares memory across agents and repositories so they can understand your entire system.It's an alternative to tools like Conductor for orchestrating AI coding agents to build product, but we focused specifically on multi-repo workflows (e.g., backend repo + client repo + shared library repo + AI agents repo). We built our own Memory and Context Engine from the ground up specifically for coding agents.Why build another agent orchestration tool? It came from our own problem. While working on our last startup, Husain and I were working across two different repositories. Working across repos meant manually pasting API schemas between Cursor windows — telling the frontend agent what the backend API looked like again and again. So we built a small context engine to share knowledge across repos and hooked it up to Cursor via MCP. This later became Modulus.Soon, Modulus will allow teams to share knowledge with others to improve their workflows with AI coding agents - enabling team collaboration in the era of AI coding. Our API will allow developers to switch between coding agents or IDEs without losing any context.If you wanna see a quick demo before trying out, here is our launch post - https://x.com/subhajitsh/status/2024202076293841208We'd greatly appreciate any feedback you have and hope you get the chance to try out Modulus.

Enrichment

Theme
AI agent frameworks and developer tools
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
AI-native
Project type
Commercial product
Normalized one-liner
knowledge orchestration for coding agents
Manually corrected
False

Could you build this?

Partial A multi-agent desktop UI can be vibe-coded, but indexing and synchronizing cross-repository dependency graphs and semantic memory across concurrent coding agents is complex.

What it would actually take: The architecture requires a desktop shell (Tauri or Electron) that orchestrates local CLI processes, connected to a daemon running tree-sitter AST parsers, language server protocol (LSP) multiplexers, and a localized vector graph database. The hard challenge is resolving inter-repository code references, cross-boundary type definitions, and keeping semantic memory synchronized across concurrent agent edits without drift. This requires advanced knowledge of static code analysis, AST parsing, and distributed context management.

Discussion

4 comments analyzed.

Concerns raised: Memory controller bottleneck on lower-end ARM v8 cores, Whether SIMD approach is tuned for ARM or just x86/high-end silicon

Competitors

Other products that read as similar to this one — 362 launches clear the similarity bar, closest 8 shown.

Attention rank: #131 of 363 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 130 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.