AtMem 2.3.8 is out ๐
Hermes one-command support, source-linked context, typed evidence, bounded retrieval, fail-closed sufficiency checks.
๐ LongMemEval-V2: AtMem: 5/23 vs AgentRunbook-R 4/23 & Mem0 1/23
๐ DolphinBench: AtMem: 9/30 vs Mem0 7/30
> pip install -U atmem==2.3.8
If you like it give us Star and Follow us on GitHub ๐
https://t.co/9kY5jkGlMM
Thanks for the feedback.
AtMem provides persistent memory for AI agents, with governance, audit trails, and activity tracking.
It integrates with OpenClaw, LangChain/LangGraph, Pydantic AI, and custom agents. It stores memories and retrieves relevant information for the agentโs context.
An agent can use AtMemโs MCP tools to explicitly remember or retrieve information. Supported adapters and plugins, such as the OpenClaw integration, automate memory capture and context injection once configured and enabled.
the atmem code will have two direction:
AtMem Structure: โWhat is connected to what in this repository?โ
AtMem Experience: โWhat have we learned while working on it?โ
So AtMem Structure + Experince give a better picture to coding agents
@lostonwww on the otherhand, we are doing more agentic code development, like software factories etc. We also have a lot of open sources, now we can see how things can improve if we add memory or whatever tool in the outcome retrospectively ... it's just idea not done it yet
Exactly itโs hard to penetrate the crowded noisy space of coding agents in particular. I just see we need to bring coding memory to AtMem it is the use case at least for me and my team. We can play with it. There are good solutions out there but Iโm after reinventing the wheel in this case
Donโt overlook Coding agents like Codex/Claude/Github Copilot custom agents: built-in coding tools, multi-agent delegation, MCP support, and orchestration without separate LLM API keys.
sometimes your workflow can sit in cli and use coding agent to achieve your goal, this way your agentic work is integrated in the code. It comes with its limitation but has its place.
We wonโt leave that solely to the agent. The plan is to carry repo/worktree, commit and dirty-state context, then have AtMem check applicability before recall. Branch names alone arenโt enough. Todayโs preview conservatively withholds code-dependent memories after revision changes.
today discussin with a friend, we tried to use atmem for coding memory, I found AtMem in Github Copilot can be use via MCP, it is not seamless but can be used. We discussed about whether we can have a flavour of AtMem coding agent agnostic and instead of MCP passive path uses hooks and can integrate actively in coding agents. So I'm targeting a special release for AtMem on Code, it shall support out of the box with adaptors for Codex, Claude Code, Muse Code, Grok and Github Copilot. I'll keep you posted on that.
Anthropic replaced Git with Scion. Why?
AI agents pushed code merges from 2,500 to 30,000+ per day, making traditional source control a bottleneck.
The result? ~100ร faster checkouts and 200ร less infrastructure overhead.
The next bottleneck in AI coding isn't generating code. It's the infrastructure handling it.
https://t.co/oZTCCQjBXG