Aelyx
Engineering intelligence for a codebase: Git-aware context, durable project memory and architecture knowledge, exposed to AI tools over MCP.
- Ownership
- Personally owned by me. Used every day by the Red Sentra engineering team.
- Availability
- Internal engineering tool, not a generally available product. Source is private.
- Stack
- Rust / MCP / Git / Developer tooling
The problem
AI coding tools forget. Every session starts from nothing, rereads the same files and rebuilds the same approximate mental model of a repository it has already seen many times. On a large codebase that is slow, expensive and unreliable.
The system
Aelyx is a Rust service that keeps a durable, Git-aware model of a project: how it is structured, how the parts depend on each other, and what has changed since it last looked. That knowledge is exposed to AI tools over MCP, so an assistant asks the project questions instead of inferring answers from a handful of file reads.
My role
I own it end to end: architecture, the Rust implementation, the MCP surface, and the judgement calls about what is actually worth remembering.
The hard part
Keeping the model correct while the repository keeps moving. Code changes constantly, and a stale answer about architecture is worse than no answer, because it is confidently wrong and gets acted on.
Architecture decisions
- Git is the source of truth. State is anchored to commits, so the system always knows which version of reality an answer belongs to, and what has to be invalidated.
- Incremental analysis over full reanalysis. Recomputing a large repository on every change does not scale, so work is scoped to what actually moved.
- MCP as the only integration surface. One protocol boundary instead of a bespoke plugin per tool keeps the client side thin and replaceable.
Where it stands
In active internal use inside Red Sentra and under continuous development. The public showcase describes what it does; the repository stays private.