sync82
io.github.oito2v1.0.0Updated Oct 6, 2026
Persistent, structured project memory for AI coding agents, stored locally in SQLite.
Overview
Gives an AI coding agent persistent, structured project memory stored locally in SQLite, recalled automatically across sessions.
- What it does
- sync82 stores a software project's goals, architecture, tech stack, decisions and progress in a local SQLite vault and exposes them to the agent through 18 MCP tools. The agent can load a whole project's context in one call, save a session in one call, search the vault, archive old dated entries, and export or import memory as plain Markdown. Six standard memory files per project are supported, plus custom files and subprojects for monorepos. A CLI registers the server in supported MCP clients.
- When to use it
- Useful when an AI coding agent should remember a project's context between sessions instead of being re-briefed each time. Suited to developers working on long-lived codebases, monorepos or plugin ecosystems who want local, private memory rather than a hosted service.
- Requirements
- A local process over stdio; a prebuilt binary for Linux, macOS or Windows needs no runtime, while building from source needs a Go toolchain. An MCP client such as Claude Code, Claude Desktop, Cursor, Zed, Codex, OpenCode, Antigravity or Cline. Claude Desktop users can install the .mcpb extension instead. No accounts, API keys or network service are declared.
Installation
In SourceWeft
- Open sync82 in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
sync82
[sync82 by OITO2 Labs — Persistent and shared memory among AI agents]
[CI] [Go Reference] [Go Version] [Release] [License] [Code: AI-Assisted]
🌐 Language: English · Português
sync82 is a Model Context Protocol (MCP) server that gives an AI coding agent persistent, structured memory of a software project across sessions — goals, architecture, tech stack, decisions, and progress, all stored locally and recalled automatically the next time the agent opens the project.
Table of Contents
- Overview
- Prerequisites & Quick Installation
- Client Setup
- Update & Maintenance
- Documentation
- AI Usage in This Project
- License
Overview
Memory is stored in an embedded SQLite database and ships as a single self-contained binary — no runtime toolchain, no npm package, just sync82 on your PATH. The agent reads and writes it through MCP tools; you talk to the agent in plain language.
- Six standard memory files per project, plus any custom file, for projects and their subprojects (monorepos, plugin ecosystems).
- Automatic project discovery — a
.sync82.jsonin the workspace means the agent never has to name the project again. - 18 MCP tools — load a whole project's context in one call, save a session in one call, search the whole vault, archive old history, export/import plain Markdown.
- One-step client setup —
sync82 installregisters sync82 in Claude Code, Claude Desktop, Antigravity, Codex, OpenCode, Cursor, Zed and Cline;sync82 uninstallremoves it. - Local and private — stdio transport only, no network service, one SQLite file per vault.
- Verifiable releases — SHA-256 checksums, a Sigstore signature and GitHub build provenance attestations; a Claude Desktop extension (
sync82.mcpb) and an MCP Registry entry.
Tools (18)
The AI agent calls these over MCP — it never touches the database directly. Full parameter reference in Tools Reference.
list_projects, list_files, check_project_health and search_memory also return JSON (format: "json"). Not sure what to type to your agent? See Example Prompts.
CLI commands
Full flags, exit codes, and examples for every command: CLI Reference.
Prerequisites & Quick Installation
Prerequisites: Linux, macOS, or Windows (amd64/arm64) — a release binary needs nothing else; building from source needs a Go toolchain matching go.mod (1.26+). You'll also need an MCP client (see Client Setup). Claude Desktop users can skip this section and install the .mcpb extension instead.
Two ways to get the binary on any OS — either works, but don't mix update mechanisms (see CLI Reference — self-update).
Linux
Prebuilt binary (no Go toolchain needed):
From source (requires Go 1.26+ — download it from go.dev/dl; distribution packages such as Debian/Ubuntu's golang-go are usually older):
macOS
Prebuilt binary (no Go toolchain needed):
From source (requires a Go toolchain — brew install go):
Windows
Prebuilt binary (no Go toolchain needed — PowerShell):
From source (requires a Go toolchain — installer):
Every release ships a checksums.txt (verified in the steps above), a Sigstore bundle signing it (checksums.txt.sigstore.json), and a GitHub build provenance attestation for every binary and the .mcpb bundle (gh attestation verify <file> --repo oito2/mcp-sync82) — see the Installation Guide.
go install/go build produces the final binary directly, ready to run — make sure $(go env GOPATH)/bin (or %GOBIN%/$GOBIN) is on your PATH; check with which sync82 (where sync82 on Windows).
Client Setup
Register sync82 in every supported client detected on your machine, in one step:
Targets: claude, claude-desktop, antigravity, codex, opencode, cursor, zed, cline. Each client is registered with the absolute path of the sync82 binary you ran, so run sync82 install again if you move the binary. Each target prints configured. or updated.; a client that isn't detected (its command on PATH or its config directory) is skipped.
Claude Code by hand (user scope, every project):
Claude Desktop — no binary needed: download sync82.mcpb and install it from Claude Desktop's Settings → Extensions → Advanced settings → Extension Developer → Install Extension…. sync82 is also listed in the MCP Registry as io.github.oito2/mcp-sync82.
Per-client guides, with manual configuration and troubleshooting: Claude Code · Claude Desktop · Antigravity · Codex · OpenCode · Cursor · Zed · Cline. Any other client just needs command set to the binary's absolute path — see Installer.
Update & Maintenance
self-update works on a release binary or a go install .../[email protected] build. If you installed with go install, update with go install github.com/oito2/mcp-sync82/cmd/sync82@latest instead — don't mix the two. The Claude Desktop extension is updated by installing a newer sync82.mcpb.
To remove sync82 from every detected client, run sync82 uninstall (add --purge to also delete the default vault and config in ~/.sync82) — see Uninstallation for the complete removal, binary included.
Documentation
The documentation site has the full detail (also in Portuguese):
- Installation · Quickstart · Uninstallation
- Concepts — Architecture and internals
- Reference: Tools · CLI · Configuration
- Example Prompts · Usage Examples
- Troubleshooting
Contributing: see CONTRIBUTING.md for the development workflow, the checks CI runs (go build ./..., go vet ./..., gofmt -l ., golangci-lint, go test ./... -race, govulncheck), and how releases are published. Everyone participating is expected to follow the Code of Conduct.
AI Usage in This Project
This project was developed with the assistance of generative AI tools:
-
Scope: Generation of boilerplate, unit tests and refactoring of helper functions.
-
Oversight: All generated code was manually reviewed, tested and validated before integration.
License
GPL-3.0 — see LICENSE.
Source: README.md at commit f169501
Tools
0Version history
1- v1.0.0LatestOct 6, 2026


