devnexus: Shared AI brain across repos, sessions, and engineers

devnexus addresses a critical gap in current AI-assisted development workflows by creating persistent memory systems for engineering teams. The tool establishes a Git-integrated Obsidian vault that serves as a persistent knowledge base for AI agents, ensuring that architectural decisions, API contracts, and failure modes survive beyond individual development sessions. This implementation allows teams to maintain continuity between engineers and across multiple project lifecycles without requiring manual documentation rituals or coordination meetings.

The architecture leverages Git for versioning and synchronization while using Obsidian's graph-based markdown ecosystem to store and visualize decisions. Engineers initialize a devnexus workspace which automatically maps repositories and creates a structural index of the codebase. The system maintains append-only decision records that AI agents reference before writing new code, preventing redundant attempts to repeat failed approaches. This creates an emergent pattern of institutional memory that compounds over time.

Key innovations include automated code graph analysis identifying 'god nodes' (high-impact modules), community detection in code structure, and bridge identification between systems. These features help agents make context-aware recommendations. The implementation uses Git hooks to maintain contract drift detection, ensuring API commitments are reflected in documentation. For teams, this creates a lightweight but persistent collaboration layer that works within existing workflows without requiring new practices or platforms.

This approach represents a shift in how engineering teams handle knowledge retention across AI-assisted development. By treating the vault as a central knowledge artifact, devnexus enables teams to build on each other’s discoveries without additional overhead. The tool is particularly valuable for organizations with high engineer turnover or complex, long-term systems where institutional knowledge is critical to maintain system integrity. The CLI-based design ensures minimal friction for adoption while providing technically sophisticated collaboration capabilities.