WeSearch

Team-memory – your team's shared brain, auto-built from Claude Code CLI or UI

·3 min read · 0 reactions · 0 comments · 33 views
#collaboration#developer-tools#knowledge-management#ai-integration#version-control#team-memory#Claude Code#GitHub#Andrew Skea#Haiku#Sonnet#Opus#MCP server
Team-memory – your team's shared brain, auto-built from Claude Code CLI or UI
TL;DR · WeSearch summary

team-memory is a tool that creates a shared, version-controlled knowledge base for teams, automatically built from interactions with Claude Code or manual entries via a web interface. It stores all information in a Git repository owned by the team, using Markdown files that support full version control and direct editing. The system runs locally, integrates with GitHub, and emphasizes privacy by binding only to localhost and avoiding external telemetry.

Key facts
Original article
GitHub
Read full at GitHub →
Opening excerpt (first ~120 words) tap to expand

team-memory Shared, version-controlled knowledge base your whole team builds together Locally run in your CLI or UI, backed up to your git knowledge repo automatically Most team knowledge lives in people's heads, scattered Slack threads, or stale wikis nobody trusts. team-memory is different: it lives in a Git repo your team already owns, every entry is a commit, and anyone can open the web UI and jot something down in seconds. Two ways to build it up: Web UI — lightweight note-taking interface at http://team-mem.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub