Give your AI agents memory that spans across projects.
AI coding agents (Claude Code, Cursor, Windsurf, etc.) are powerful — but they only see one project at a time. When your work involves a shared API contract, a common deploy process, or a monorepo split into microservices, the agent starts every conversation blind to the bigger picture.
AI Workspace fixes that. It's a lightweight CLI + MCP server that lets you share files, directories, and notes across related projects. Your agents get cross-project context automatically — no copy-pasting, no symlinks, no custom prompts.
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ project-api │ │ project-web │ │ project-docs │
│ │ │ │ │ │
│ schema.rs ──┼─┐ │ │ │ │
│ notes ──────┼─┤ │ notes ──────┼─┐ │ guides/ ────┼─┐
└──────────────┘ │ └──────────────┘ │ └──────────────┘ │
│ │ │
└────────┬───────────┘────────────────────┘
│
┌─────▼──────┐
│ "backend" │ ← group
│ group │
└─────┬──────┘
│
┌─────▼──────┐
│ MCP Server │ ← ai-workspace serve
│ (stdio) │
└─────┬──────┘
│
┌─────▼──────┐
│ AI Agent │ sees files, dirs & notes
│ │ from all 3 projects
└────────────┘
Group projects together. Share files and notes. Your agent sees everything.
cargo install --path .Requires Rust 1.85+ (edition 2024). SQLite is bundled — no extra dependencies.
# Register two projects in the same group
cd ~/api
ai-workspace init --group backend
cd ~/web
ai-workspace init --group backendcd ~/api
ai-workspace share src/schema.rs --label "db schema"
ai-workspace note "Deploy: run migrations before release" --group backendNow any agent working in ~/web can read schema.rs and the deploy note from ~/api.
Claude Code:
claude mcp add --scope user ai-workspace -- ai-workspace serveOther MCP clients (Cursor, Windsurf, Claude Desktop, etc.):
{
"mcpServers": {
"ai-workspace": {
"command": "ai-workspace",
"args": ["serve"]
}
}
}That's it. The agent now has access to 7 MCP tools: workspace_context, workspace_read, workspace_search, list_groups, list_projects, project_tree, and project_grep.
Once connected, you can talk to your AI agent naturally. Here are some examples:
Discover context:
- "What shared context do I have from other projects?"
- "Show me all projects and groups in my workspace"
- "What files are shared in the backend group?"
Read shared files:
- "Read the shared database schema from the api project"
- "Show me the deploy guide shared by the infra team"
- "What's in the shared config directory?"
Search notes:
- "Search workspace notes for migration instructions"
- "Are there any shared notes about the deploy process?"
- "Find notes mentioning staging environment"
Navigate project files:
- "Show me the file tree of the api project"
- "List the files under src/ in project 2"
- "Search the api project for any function that mentions 'auth'"
- "Grep the web project for TODO comments"
Cross-project tasks:
- "I'm building a new endpoint — check the shared API schema and follow the same patterns"
- "Before I refactor this model, check if other projects share files that depend on it"
- "Read the shared style guide and apply it to this component"
The agent will automatically call the right MCP tools (workspace_context, workspace_read, workspace_search) to answer these.
| Command | What it does |
|---|---|
init --group <name> |
Register project, join/create a group, auto-share key files |
share <path> --label <label> |
Share a file or directory |
note <text> --group <name> |
Add a group-scoped note |
edit <target> --content/--label/--scope |
Edit a shared item |
rm <target> |
Remove a shared item |
leave <group> |
Remove project from a group |
delete-group <group> |
Delete a group entirely |
destroy |
Remove current project from ai-workspace (keeps files) |
status |
Show project info, groups, and items |
export |
Export project config to .ai-workspace.json |
sync |
Clean up stale files + reconcile .ai-workspace.json |
serve |
Start the MCP server |
update |
Update to the latest version |
Share your workspace config with your team by committing .ai-workspace.json to the repo:
# One-time: export current config
ai-workspace export
# Commit the file
git add .ai-workspace.json
git commit -m "chore: add shared workspace config"When a teammate clones the repo and runs init, they automatically get the same groups, shared files, and notes:
cd ~/cloned-repo
ai-workspace init
# → picks up name, groups, shares, and notes from .ai-workspace.jsonThe --name flag overrides the name from .json, and --group is additive. Running sync also reconciles the database with .ai-workspace.json if present.
| Guide | Description |
|---|---|
| Getting Started | Concepts, scopes, visibility rules, data storage |
| CLI Reference | All commands and options in detail |
| MCP Server | MCP tools, protocol, and integration guide |
macOS (Apple Silicon)
curl -fsSL https://github.com/lee-to/ai-workspace/releases/latest/download/ai-workspace-aarch64-apple-darwin.tar.gz | sudo tar xz -C /usr/local/binmacOS (Intel)
curl -fsSL https://github.com/lee-to/ai-workspace/releases/latest/download/ai-workspace-x86_64-apple-darwin.tar.gz | sudo tar xz -C /usr/local/binLinux (x86_64)
curl -fsSL https://github.com/lee-to/ai-workspace/releases/latest/download/ai-workspace-x86_64-unknown-linux-gnu.tar.gz | sudo tar xz -C /usr/local/binLinux (aarch64)
curl -fsSL https://github.com/lee-to/ai-workspace/releases/latest/download/ai-workspace-aarch64-unknown-linux-gnu.tar.gz | sudo tar xz -C /usr/local/binWindows (x86_64, PowerShell)
Invoke-WebRequest -Uri "https://github.com/lee-to/ai-workspace/releases/latest/download/ai-workspace-x86_64-pc-windows-msvc.zip" -OutFile ai-workspace.zip
Expand-Archive ai-workspace.zip -DestinationPath "$env:USERPROFILE\bin" -ForceAdd %USERPROFILE%\bin to PATH if needed.
Build from source
git clone https://github.com/lee-to/ai-workspace.git
cd ai-workspace
cargo install --path .Requires Rust 1.85+ (edition 2024). SQLite is bundled — no extra dependencies.
ai-workspace updateDownloads the latest release from GitHub and replaces the current binary. No Rust or Cargo required.
MIT