Browse / General-purpose / mercury-go
mercury-go
Accenture
agent-memory — vendor-neutral shared AI memory + cognitive loop for human–AI collaboration (Mercury family)
Open Accenture/mercury-go → On the boundary of the four rules.
Works with any agent
ships AGENTS.md, the cross-tool instruction file.
In its own words
A no-code AI memory system, AI-enablement tool, and migration tool — all in one repo. Markdown only. No code to run. No API keys.
- A memory system — clone it, open with your agent, work normally.
Context persists across sessions and across different AI agents — and it evolves: frequently-used facts strengthen, unused ones fade to an archive, and the live continuity.md stays lean (see "Evolving Memory" below).
- An enablement tool — point your agent at any existing repo and it
gets a tailored memory system set up automatically.
- A migration tool — if the target repo already uses vendor AI files
(Cursor, Aider, Continue, Cline, Roo, Windsurf, Copilot, etc.), they get migrated into the unified format. Steering files folded in, chat history converted to dated session logs, originals preserved under legacy/.
Part of the Mercury family — Accenture's advanced software foundations for human–AI collaboration — since September 10, 2026, having proven itself across multiple field installations (see The Mercury Family below). Official home: github.com/Accenture/mercury-go · documentation: accenture.github.io/mercury-go · Apache-2.0. The tool kept its name and its version at graduation (v4.39.2 at the time) — graduation recognized the tool's state, it did not change it; enabled repositories needed no action for it.
Quoting 12% of the README. Read the rest on GitHub ↗
What came from it 1
Read from the repository's git tree on 2026-08-17.