Rhei

Rhei makes agents aware of your team's code, decisions, and prior work, then learns what matters as you ship.

[Rhei @rheiteam]

Introducing Rhei.

The first code intelligence that grows with you and gets better on every task as shared context graph.

Local. Private. Works with any coding agent via MCP.

[Rhei @rheiteam]

@kevinkern @pvncher How about getting the right files, reuse components and memory? We got inspired by the work of @RepoPrompt

[Rhei @rheiteam]

@luabagg @corbin_braun @cursor_ai It does not include memory, while it provides likely what files are needed it does not say what files are right.
At Rhei, we learn from activity and provide the right files without agent to guess.

[Rhei @rheiteam]

@corbin_braun @cursor_ai We reduce token spend and provide the right files and meteorites with the given task or goal. What is different from all solutions is to get memory, file and reuse components per task not just some files, it learns from your usage

[Rhei @rheiteam]

@dexhorthy We store them them task-aware with memory. They are feeded when its needed, and are decaying when are not relevant anymore. While Rhei is able to display stale docs in repo. Try it out.

[Rhei @rheiteam]

Start in one line.

curl -fsS https://t.co/TkHcmT8cQJ | bash

or visit:

https://t.co/vrVYjU86CY

[Rhei @rheiteam]

Introducing Rhei.

The first code intelligence that grows with you and gets better on every task as shared context graph.

Local. Private. Works with any coding agent via MCP.

[Rhei @rheiteam]

The shared operational layer which follows while you scale and learns.

The right files & memory for the task, what your team already decided, what to reuse, what a change will break, what is dead code, and which docs went stale.

Get daily pulse for agents; what has been done and where to focus next. Automatically.

Across many repos.

[Rhei @rheiteam]

The intelligence rises, but nobody is trying to provide agents the right awareness in this bloating environments.

[Rhei @rheiteam]

Hallo Welt!