Seamless

- Built for a fleet, not a lone agent.Real coordination primitives: a dependency-aware ready-queue, atomic lease-based task claiming, and plans composed of notes and steps, so agents divide labor instead of colliding.
- Files are the source of truth.Every memory and note is a markdown file with YAML frontmatter under~/.seamless-- git-diffable, greppable, hand-editable. SQLite indexes those files and also stores operational state such as sessions, tasks, trials, and events, so back up the whole data directory.
- Curation proposes, humans dispose.Every gardener pass -- from deduplicating and archiving to flagging dead weight and knowledge gaps -- onlyproposes; applying is an explicit action. Supersession preserves provenance, so nothing is silently rewritten.
- Small, self-contained runtime.A static Go daemon and CLI, no CGO, pure-Go SQLite, no Node, no separate vector engine, no cloud account.

The agent-memory space splits into a few recognizable categories. By category, because categories do not go stale:

Four pairs of real, unedited Claude Code sessions -- identical prompt, identical repo, with and without Seamless:

Not a hosted team knowledge base, not a RAG framework, not a benchmark winner: it is memory and coordination for one owner's fleet of agents, on that owner's machine.

curl -fsSL https://thereisnospoon.org/install | sh

On Windows, the same install in PowerShell:

irm https://thereisnospoon.org/install.ps1 | iex

That is the whole install. It needscurlandtarand nothing else -- no Go, no CGO toolchain, no database, no Node. It fetches the checksum-verified release archive for your platform (macOS, Linux, and Windows; amd64 and arm64), installsseamlessdandseaminto~/.local/bin, generates the bearer key, installs hooks, MCP, and skills for the detected Claude Code/Codex local hosts, and runs the daemon as a per-user service -- launchd on macOS, systemd--useron Linux, an at-logon Scheduled Task on Windows. Upgrade any time withseamlessd update(re-runs the installer for you;--checkreports installed vs latest): your config and~/.seamlessare never touched.

(Whyseam? The CLI keeps the short name of Seam v1, the decommissioned private predecessor Seamless was rebuilt from the ground up to replace.)

Then just start the selected client in a git repo. There is no project to create and no repo to register: the session-start hook resolves your cwd to its git root, derives a project from the repo's directory name, and records the mapping on the spot, so agents inherit project scope without passing it on every call. Reach forseamlessd map-repo --path ~/code/myrepo --project myrepoonly to override the derived slug.

This README is deliberately short. Anything that can drift from the code -- tool counts, config keys, CLI flags -- lives in the docs site, where the reference pages are generated from the code itself andmake checkfails if they go stale.

make build # ./bin/seamlessd + ./bin/seam make test # unit tests make test-race # unit tests under the race detector make bench # hot-path benchmarks (recall, briefing, matcher, event fan-out) make lint # golangci-lint make check # the full gate: build + vet + fmt-check + docs-check + # installer-check + site-check + lint + vulncheck + test-race make doctor # config + database self-checks make run # serve on 127.0.0.1:8081 make docs # regenerate the docs site (docs-src/ -> docs/docs/, committed) make docs-serve # regenerate + serve the site at 127.0.0.1:8899/docs/

Tests are table-driven withtestify/requireagainst fresh or in-memory SQLite. Usemake fmtrather thangofmt -w .: the Make target scopes formatting to git-tracked files, while a baregofmtwalk also rewrites dot-directories that Go's./...pattern excludes.

Persistent memory for AI assistants and coding agents across ChatGPT, Claude, Cursor, and other MCP-compatible tools.

Highly efficient context management for agentic AI: MCP code search, evidence packs, graph context, and memory for large projects.

Connect AI agents to Granoflow for tasks, reviews, and spaced-review memory cards.

Shared memory layer for AI coding agents with dream pipeline distillation, session grounding, and multi-instance coherence.

OpenMemBrain is the intelligent membrane for AI coding memory. It autonomously reads and learns from your coding sessions — you never have to tell it what to save. It selectively absorbs project knowledge, blocks secrets, filters noise, resolves conflicts, and persists only what matters.

Hosted shared memory for coding agents: what one connected agent learns, other connected agents can recall.

Shared memory for coding agents. Stop re-explaining your codebase every session. Hosted MCP at https://teamshared.com/mcp with email/OTP Connect.

Provides AI assistants with advanced task management and memory capabilities using local JSON file storage.

Portable, cloud-hosted AI memory you own - structured memories, tasks, goals, and notes that work across Claude, ChatGPT, Gemini, and any MCP client.