Akumi CodePreview
Your coding agent knows the code. Now it knows why.
Akumi Code connects your GitHub and GitLab repositories to Recall, so every pull request, issue, review and decision becomes knowledge an agent can reach through the Akumi MCP server. On the same platform as every other call, with the same record.
In preview. No price announced yet.
GitHub and GitLab
Connect a repository and Recall keeps its history in step from then on.
Any MCP client
Akumi Code is an MCP server. Anything that speaks MCP reaches it, Claude Code and Akumi Chat included.
Every answer cited
The agent names the pull request or issue it read, so you can check the claim.
The code is in the model. The reasoning never was.
A coding agent reads your files and guesses the rest. It brings back a bug you fixed last year and proposes an approach the team already rejected, because the argument that settled it lives in a review thread no model has ever seen.
What Recall indexes
Everything the repository remembers.
Recall indexes the history around the code, the way a long-serving engineer remembers it. Connect a repository once and it keeps up from then on.
Pull requests
Every review comment and every revision, so an agent sees why a change ended up different.
Issues
Bug reports, reproductions and the thread that closed them.
The code itself
The files, so the answer and the argument come back together.
Commit history
Messages and history, so a line of code can be followed back to its origin.
Decision records
Architecture decision records, design notes and anything else the repository keeps.
Discussions
The threads where the team argued it out before anyone wrote a line.
Setup
Three steps, then ask.
Connecting is a standard OAuth flow. There is nothing to run and nothing to host, and the access Akumi holds is read-only.
- 01Connect the repositoryAuthorise GitHub or GitLab and choose which repositories Akumi may read. Recall indexes the history and keeps up from then on.
- 02Add the MCP serverOne command, or one entry in your client config. Claude Code, Akumi Chat, or anything else that speaks MCP.
- 03AskThe agent answers from the repository and names the pull request or issue it read, so you can check the claim.
No special case
Your code stays in the EU.
Handing a repository to an agent is a data decision, not a developer convenience. Code runs on the same platform as every other call, so the answer is on paper before anyone asks.
Read-only and scoped
Akumi reads the repositories you connect and nothing else. It never writes back.
No training on your code
Your repository is knowledge for your agents. It never becomes training material.
Every lookup recorded
Which agent asked, what it read and in which region. The same trail as any other call.
FAQ
Questions people ask about Code.
- Which repositories can I connect?
- GitHub and GitLab. You choose which repositories, and the access Akumi holds is read-only.
- Which agents can reach it?
- Akumi Code is an MCP server, so any client that speaks MCP can reach it. Claude Code and Akumi Chat are two of them.
- Does it index the code, or only the discussion?
- Both. The files, and the pull requests, issues, commits and decision records around them.
- Does our code leave the EU?
- No. Indexing and retrieval run on EU-resident infrastructure, and every lookup records the region it ran in.
- Do we need the platform to use Code?
- Yes. Code runs on Recall and the MCP server, so it sits on a platform subscription.
- When can we use it?
- Akumi Code is in preview. Join the waitlist and we will contact you before it opens.
Give your agents everything the team already decided.
Akumi Code is in preview. Leave your work address and we will contact you before it opens.
In preview. No price announced yet.