teamem

Teamem

English | 한국어

Tired of merge conflicts on every PR, even with coding agents?

With Teamem, no more "my Claude Code edited that first," "can I edit this file now?", "how did you fix that?", or "wait, are we skipping the user page implementation? I never heard of that!"

Teamem is team memory for humans and their coding agents. It is built to help teammates using Claude Code in the same repository share work context, coordinate code-editing scope, record important decisions, and keep work moving safely without conflicts.

Teamem is useful when:

• multiple teammates are using Claude Code in one codebase or repository;
• you want every teammate and agent session to know the current direction, decisions, and troubleshooting history;
• you need file claims that release automatically when work is committed;
• you want team knowledge to live outside one chat transcript.

Quick Start

Teamem requires a shared server. Set that up first. Use a server your team already runs, or clone this repository and self-host it.

With Docker Compose:

git clone https://github.com/RubiYH/teamem.git
cd teamem
cp .env.example .env
# Set TEAMEM_JWT_SECRET in .env. For local testing:
#   openssl rand -hex 32
docker compose up --build -d

Or directly with Bun:

git clone https://github.com/RubiYH/teamem.git
cd teamem
bun install
cp .env.example .env
# Set TEAMEM_JWT_SECRET in .env. For local testing:
#   openssl rand -hex 32
mkdir -p data
bun run server

After the server is available, install Bun on each teammate machine if it is not already available:

curl -fsSL https://bun.sh/install | bash

Then install the bootstrapper CLI and run the guided Claude Code setup:

npm install -g @rubiyh05/teamem
teamem init
teamem cc

teamem init checks prerequisites, adds or refreshes the teamem-alpha Claude Code marketplace, installs the teamem@teamem-alpha plugin, runs the space create or join setup flow, and can install Teamem git hooks. teamem cc launches Claude Code with the Teamem development channel enabled.

[!WARNING] Teamem currently uses Claude Code's experimental Channels feature for live delivery. Channel behavior may change, be unavailable in some environments, or require fallback to /teamem-briefing, /teamem-status, and unread notifications.

Inside Claude Code:

/teamem-on
/teamem-on --persist
/teamem-briefing

Use /teamem-on --persist when this repository should default to Teamem being on in future Claude Code sessions. From there, edit normally. Teamem hooks claim paths before edits, release on_commit claims after commits, and surface conflicts or queued work through the plugin.

How it works

flowchart LR
  subgraph Clients[" "]
    direction TB
    TA["Teammate A<br/>Claude Code<br/>plugin + bridge + git hooks"]
    TB["Teammate B<br/>Claude Code<br/>plugin + bridge + git hooks"]
    TC["Teammate C<br/>Claude Code<br/>plugin + bridge + git hooks"]
  end

  S["Teamem server"]
  DB["SQLite event store"]

  TA <-->|tools / events| S
  TB <-->|tools / events| S
  TC <-->|tools / events| S
  S <--> DB

  style Clients fill:transparent,stroke:transparent

Claude Code plugin + git hooks
  -> local Teamem bridge
  -> shared Teamem HTTP server
  -> SQLite event store and projections

The main tool is teamem.get_briefing, which agents should call at session start and before non-trivial edits. Write coordination flows through teamem.claim_scope, teamem.release_scope, decisions, findings, discussions, and space-management tools.

What You Get

Feature	What it does
Briefings	Shows the current plan, active claims, recent decisions, risks, and progress.
Scope claims	Lets agents reserve files or modules before editing them.
Git handoffs	Releases normal claims on commit and pauses or resumes claims on branch checkout.
Decisions and gotchas	Captures durable team knowledge through /teamem-decide and /teamem-gotcha.
Discussions	Sends direct or broadcast coordination messages with /teamem-discuss.
Space rules	Exports team rules into a local TEAMEM.md cache for agent prompts.

Common Commands