Add project isolation support for multi-project deployments #5

andrewleech · 2025-11-02T21:18:46Z

Summary

Adds project isolation support to enable a single AutoMem backend to serve multiple projects with completely separate memory spaces.

Changes

AutoMemConfig interface: Add optional field
HTTP client: Send header when project is configured
CLI setup: Add flag with interactive prompting
Environment variables: Support for configuration
MCP server: Load project ID from environment in both main server and recall command

Benefits

Multiple projects can share one AutoMem deployment with isolated memories
Backward compatible - existing clients continue working without changes
Simple configuration via CLI flag or environment variable
Complements the backend project isolation feature

Usage

# Setup with project isolation
npx @verygoodplugins/mcp-automem setup --project-id my-project

# Or via environment variable
export AUTOMEM_PROJECT_ID=my-project
npx @verygoodplugins/mcp-automem setup

This works with the corresponding backend changes that add project_id scoping to Memory nodes and Qdrant collections.

- Add projectId to AutoMemConfig interface for project scoping - Update HTTP client to send X-Project-ID header when project is configured - Add --project-id CLI flag to setup command with interactive prompting - Add AUTOMEM_PROJECT_ID environment variable support - Update both main MCP server and recall command to load project ID from env This enables multiple projects to use the same AutoMem backend with isolated memory spaces via the project_id parameter.

coderabbitai · 2025-11-02T21:18:55Z

📝 Walkthrough

Walkthrough

This PR adds optional projectId configuration support throughout the AutoMem system. The projectId can be specified via environment variables, CLI arguments, or programmatic configuration, is validated and persisted through the setup workflow, and is conditionally injected as an X-Project-ID header in client requests.

Changes

Cohort / File(s)	Change Summary
Type Definitions `src/types.ts`	Added optional `projectId?: string` field to `AutoMemConfig` interface
Client Initialization `src/index.ts`	Updated `AutoMemConfig` to accept `projectId`; passes `projectId` to `AutoMemClient` instantiation alongside existing `endpoint` and `apiKey`
HTTP Client `src/automem-client.ts`	Added conditional header injection: includes `X-Project-ID` header in requests when `config.projectId` is set
CLI Setup Flow `src/cli/setup.ts`	Extended `SetupOptions` interface with optional `projectId` field; added support for reading `AUTOMEM_PROJECT_ID` environment variable, parsing `--project-id` CLI argument, prompting user for projectId input in interactive mode, and persisting projectId to environment file

Sequence Diagram

sequenceDiagram
    participant User
    participant CLI
    participant Config
    participant AutoMemClient
    participant HTTP

    User->>CLI: Run setup with --project-id
    CLI->>CLI: Read AUTOMEM_PROJECT_ID from env
    CLI->>CLI: Parse --project-id argument
    CLI->>User: Prompt for Project ID (if interactive)
    User->>CLI: Provide projectId
    CLI->>Config: Persist projectId to file
    
    Note over User,Config: Later: Using AutoMem with projectId
    User->>Config: Initialize with projectId in config
    Config->>AutoMemClient: Pass endpoint, apiKey, projectId
    User->>AutoMemClient: Make request
    AutoMemClient->>AutoMemClient: Check if projectId is set
    alt projectId set
        AutoMemClient->>HTTP: Add X-Project-ID header
    end
    AutoMemClient->>HTTP: Send request
    HTTP-->>AutoMemClient: Response

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Consistent pattern of adding an optional configuration field across multiple files
No complex business logic or destructive changes
Straightforward header injection in client layer
CLI setup follows existing patterns for environment/argument/persistence handling

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run `@coderabbitai generate docstrings` to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "Add project isolation support for multi-project deployments" clearly and concisely summarizes the main objective of the changeset. The raw_summary confirms that all modifications across four files (automem-client.ts, setup.ts, index.ts, and types.ts) work together to implement project isolation by adding a projectId field to the configuration, injecting an X-Project-ID header in requests, supporting a CLI flag with environment variable, and updating the MCP server to use this project ID. The title directly captures this primary change and would be immediately understood by a teammate reviewing the git history.
Description Check	✅ Passed	The PR description is well-structured and directly related to the changeset. It explicitly documents each modified component: the AutoMemConfig interface extension, HTTP client header injection, CLI setup flag addition, environment variable support, and MCP server integration. Each item in the "Changes" section aligns with the file-level summaries provided in the raw_summary, and the description includes concrete usage examples and explains the backward compatibility aspect. The description provides meaningful context about the feature's purpose and benefits without being vague or off-topic.

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6f0878b and e70d3d8.

⛔ Files ignored due to path filters (11)

dist/automem-client.d.ts.map is excluded by !**/dist/**, !**/*.map
dist/automem-client.js is excluded by !**/dist/**
dist/automem-client.js.map is excluded by !**/dist/**, !**/*.map
dist/cli/setup.d.ts.map is excluded by !**/dist/**, !**/*.map
dist/cli/setup.js is excluded by !**/dist/**
dist/cli/setup.js.map is excluded by !**/dist/**, !**/*.map
dist/index.js is excluded by !**/dist/**
dist/index.js.map is excluded by !**/dist/**, !**/*.map
dist/types.d.ts is excluded by !**/dist/**
dist/types.d.ts.map is excluded by !**/dist/**, !**/*.map
package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

src/automem-client.ts (2 hunks)
src/cli/setup.ts (6 hunks)
src/index.ts (3 hunks)
src/types.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

src/automem-client.ts

📄 CodeRabbit inference engine (CLAUDE.md)

src/automem-client.ts: Add a corresponding AutoMemClient method for any new tool that needs an API call
Normalize AutoMem API responses: accept memory_id, id, or response.memory_id and map to a single internal field
Normalize timestamps from timestamp, created_at, or updated_at in service responses
When recall is called with tags, merge results from /recall and /memory/by-tag for better coverage

Files:

src/automem-client.ts

src/types.ts

📄 CodeRabbit inference engine (CLAUDE.md)

Update src/types.ts with new argument/result types when adding a tool

Files:

src/types.ts

src/index.ts

📄 CodeRabbit inference engine (CLAUDE.md)

src/index.ts: Define new MCP tool schemas in the tools array in src/index.ts (with inputSchema) when adding a tool
Add a handler for each new tool in the CallToolRequestSchema switch in src/index.ts
Import and register new CLI commands in src/index.ts command routing
Do not expose the removed search_by_tag tool; use recall_memory with tags instead

Files:

src/index.ts

🧠 Learnings (7)

📓 Common learnings

Learnt from: CR
Repo: verygoodplugins/mcp-automem PR: 0
File: .cursor/rules/AGENTS.md:0-0
Timestamp: 2025-10-01T01:12:18.800Z
Learning: Include a <project-name> tag in all memories (auto-detected)

📚 Learning: 2025-10-01T01:11:42.805Z

Learnt from: CR
Repo: verygoodplugins/mcp-automem PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-10-01T01:11:42.805Z
Learning: Applies to src/automem-client.ts : Add a corresponding AutoMemClient method for any new tool that needs an API call

Applied to files:

src/automem-client.ts
src/types.ts
src/index.ts

📚 Learning: 2025-10-01T01:11:42.805Z

Learnt from: CR
Repo: verygoodplugins/mcp-automem PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-10-01T01:11:42.805Z
Learning: Applies to src/automem-client.ts : Normalize AutoMem API responses: accept memory_id, id, or response.memory_id and map to a single internal field

Applied to files:

src/automem-client.ts
src/types.ts
src/index.ts

📚 Learning: 2025-10-01T01:11:42.805Z

Learnt from: CR
Repo: verygoodplugins/mcp-automem PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-10-01T01:11:42.805Z
Learning: Applies to .env : Provide AUTOMEM_ENDPOINT in environment or .env; AUTOMEM_API_KEY is optional

Applied to files:

src/cli/setup.ts
src/index.ts

📚 Learning: 2025-10-01T01:13:48.061Z

Learnt from: CR
Repo: verygoodplugins/mcp-automem PR: 0
File: .cursor/rules/project-assistant.md:0-0
Timestamp: 2025-10-01T01:13:48.061Z
Learning: Automatically detect the current project from, in order: package.json name, Git remote repository name, then current directory name

Applied to files:

src/cli/setup.ts

📚 Learning: 2025-10-01T01:11:42.805Z

Learnt from: CR
Repo: verygoodplugins/mcp-automem PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-10-01T01:11:42.805Z
Learning: Applies to src/automem-client.ts : When recall is called with tags, merge results from /recall and /memory/by-tag for better coverage

Applied to files:

src/index.ts

📚 Learning: 2025-10-01T01:12:18.800Z

Learnt from: CR
Repo: verygoodplugins/mcp-automem PR: 0
File: .cursor/rules/AGENTS.md:0-0
Timestamp: 2025-10-01T01:12:18.800Z
Learning: Include a <project-name> tag in all memories (auto-detected)

Applied to files:

src/index.ts

🧬 Code graph analysis (2)

src/cli/setup.ts (1)

dist/cli/setup.js (20)

ENV_PROJECT_ID_KEY (10-10)

options (12-12)

options (54-54)

options (143-143)

options (230-230)

i (13-13)

i (55-55)

defaultProjectId (154-157)

existingValues (145-145)

projectId (175-175)

rl (132-132)

rl (162-162)

rl (177-177)

rl (191-191)

promptSuffix (164-164)

promptSuffix (179-179)

answer (134-134)

answer (165-165)

answer (180-180)

updates (204-206)

src/index.ts (2)

dist/cli/queue.js (1)

client (63-66)

src/automem-client.ts (1)

AutoMemClient (15-251)

🔇 Additional comments (12)

src/types.ts (1)

4-4: LGTM!

The optional projectId field is properly typed and aligns well with the existing optional apiKey field.

src/cli/setup.ts (6)

13-13: LGTM!

The projectId field is appropriately added to SetupOptions as optional, maintaining consistency with other optional fields.

26-26: LGTM!

The environment variable key follows the existing naming convention (AUTOMEM_ prefix).

46-49: LGTM!

The --project-id argument parsing is correctly implemented and follows the same pattern as --endpoint and --api-key.

181-184: LGTM!

The default value resolution logic correctly prioritizes CLI options, then existing values from the env file, then process environment, and finally defaults to an empty string. This matches the pattern used for endpoint and API key.

204-217: LGTM!

The interactive prompt for projectId is well-implemented. The prompt suffix clearly indicates that the field is optional and explains its purpose ("for project isolation"), which improves user experience.

239-241: LGTM!

The persistence logic correctly filters out sentinel values and only writes valid projectId values to the environment file, consistent with the apiKey handling.

src/index.ts (4)

171-171: LGTM!

The AUTOMEM_PROJECT_ID environment variable is correctly read in the recall command flow, maintaining consistency with AUTOMEM_ENDPOINT and AUTOMEM_API_KEY.

178-178: LGTM!

The projectId is properly passed to the AutoMemClient constructor in the recall command, ensuring project isolation is applied when configured.

208-208: LGTM!

The AUTOMEM_PROJECT_ID environment variable is correctly read for the main MCP server configuration.

214-218: LGTM!

The projectId is properly included in the clientConfig object, completing the configuration flow for project isolation support.

src/automem-client.ts (1)

37-39: Header name is correct per commit specifications.

The actual commit message for "Add project isolation support" explicitly states: "Update HTTP client to send X-Project-ID header when project is configured." The code at line 38 correctly implements this with headers['X-Project-ID']. The review comment's claim that the PR description specifies X-AutoMem-Project cannot be verified, and there are no references to that header name anywhere in the codebase. The implementation matches the documented intent of the commit.

Likely an incorrect or invalid review comment.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

andrewleech marked this pull request as draft November 3, 2025 00:05

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add project isolation support for multi-project deployments #5

Add project isolation support for multi-project deployments #5

Uh oh!

andrewleech commented Nov 2, 2025

Uh oh!

coderabbitai bot commented Nov 2, 2025 •

edited

Loading

Walkthrough

Changes

Sequence Diagram

Estimated code review effort

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Add project isolation support for multi-project deployments #5

Are you sure you want to change the base?

Add project isolation support for multi-project deployments #5

Uh oh!

Conversation

andrewleech commented Nov 2, 2025

Summary

Changes

Benefits

Usage

Uh oh!

coderabbitai bot commented Nov 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Sequence Diagram

Estimated code review effort

Pre-merge checks and finishing touches

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

coderabbitai bot commented Nov 2, 2025 •

edited

Loading