Team memory for AI coding agents
What one developer's agent learns about the codebase, every teammate's agent inherits — through your git repo, with a review queue for what comes in and an audit trail of every admin change.
Every feature on this page runs free at 1 seat, so you can evaluate it before you buy. The Team license ($29/user/mo, 5–50 seats, annual) adds seats and priority support. See pricing →
How team memory works
No relay, no hosted service, no server of ours in the path. The shared memory is a file in your repository, so it travels with git clone and inherits your existing review and access controls.
- 1
Learn locally
Each developer’s synapse layer learns from their own work — which files get opened, edited and queried together. It stays in the project’s local .neuralmind/ store until someone publishes it.
- 2
Publish through git
neuralmind memory publish writes the project’s learned associations — weights between files, never source code — to .neuralmind-team-memory.json at the repo root. You commit it like any other file, so it goes through code review.
- 3
Inherit on the next session
Teammates’ agents import the bundle automatically at session start or build, once per content hash. Each association is quality-scored: strong ones enter shared memory, borderline ones wait for review, weak ones are dropped. Shared weights decay, so a stale bundle cannot permanently skew recall.
Governance: what is enforced today
Shared memory steers every teammate's agent, so what enters it is screened, what leaves a machine follows the admin's policy, and every change is on the record. Here is exactly what runs today.
Publishing follows your policy
Admins choose whether memory publish shares nothing (personal), only the team baseline (shared) or personal plus shared (both), and the minimum weight an association needs. Publish enforces both and records the policy in the bundle.
Review queue for imported memory
When a teammate’s bundle is imported, every association is quality-scored. Borderline ones wait in a queue until someone approves or rejects them; conflicts with what you already have are resolved by quality, not by whoever published last.
Retract an association
Removing an association deletes it from shared memory and retracts it in the committed bundle, so each teammate’s next session drops it and no later publish re-adds it. Admin-only, and on the audit record like every publish, import and review.
An audit trail you can verify
Every governance change and admin action — and every team-memory publish, import, review decision and retraction — is recorded with the acting user in an append-only log where each entry carries the SHA-256 of the one before it, so an edited or deleted entry breaks the chain.
Query-level events export as JSONL or CEF for your SIEM with neuralmind audit export.
# Walk the hash chain
$ neuralmind team audit verify
# Hand it to your auditors
$ neuralmind team audit export --format csv --output audit.csv
Seat management
Seats are managed from the CLI and every change is logged, and adding a seat past your license limit fails instead of silently over-provisioning. Syncing a roster from a signed seat manifest is not available yet: the CLI can verify one, but nothing issues them.
# Add a teammate (admin only)
$ neuralmind team seats add [email protected] --admin [email protected]
# List seats
$ neuralmind team seats list --json
# Deactivate a seat — the audit trail is kept
$ neuralmind team seats remove [email protected] --admin [email protected]
Free, Team and Enterprise
The product features are not gated. The license buys seats beyond one, support and procurement-friendly billing.
| Feature | Free (1 seat) | Team | Enterprise |
|---|---|---|---|
| Team memory through git (memory publish) | ✓ | ✓ | ✓ |
| Governance: publish policy, retraction, review queue | ✓ | ✓ | ✓ |
| Hash-chained audit log, verify and export | ✓ | ✓ | ✓ |
| Self-hosted deployment | ✓ | With deployment support | ✓ |
| Seats | 1 | 5–50 | Custom |
| Support | Community (GitHub) | Priority | Custom SLA |
| Billing | — | Annual invoice | Custom |
| Onboarding | Self-serve | Self-serve | Dedicated |
On the roadmap, not available on any tier today: SSO / SAML, and real-time cross-machine sync. Team memory syncs by commit and pull.
Evaluate it free, then talk to us about seats
Install the open-source core (v4.19.0), run it on one repo with the free 1-seat license, and contact us when the team wants more seats. There is no self-serve checkout and no trial clock.