
Grepai Workspaces
- 575 installs
- 18 repo stars
- Updated February 1, 2026
- yoanbernabeu/grepai-skills
grepai-workspaces is a GrepAI configuration skill that groups monorepo or microservice repositories into one workspace so semantic search and watch indexing span every related project for developers exploring large multi
About
grepai-workspaces is a yoanbernabeu/grepai-skills skill for configuring multi-project GrepAI workspaces. Workspaces let developers group monorepos, microservices, or related repos under one unified semantic search index with shared configuration. Commands like `grepai wo` create workspaces so agents and developers search all projects at once or filter to specific members. Use grepai-workspaces when onboarding to a multi-repo architecture, when watch indexing must cover sibling services, or when semantic code search should not stop at a single repository boundary.
- Create named workspaces with grepai workspace create
- Add multiple project paths via grepai workspace add for monorepos and microservices
- List workspaces and project counts with grepai workspace list
- Unified cross-project search index with optional per-project scoping
- Shared configuration across projects in one workspace
Grepai Workspaces by the numbers
- 575 all-time installs (skills.sh)
- +5 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #1,622 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-workspacesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 575 |
|---|---|
| repo stars | ★ 18 |
| Security audit | 3 / 3 scanners passed |
| Last updated | February 1, 2026 |
| Repository | yoanbernabeu/grepai-skills ↗ |
How do you search code across multiple repos?
Group monorepo or microservice repos into one GrepAI workspace so semantic search and watch indexing span every related project.
Who is it for?
Developers in monorepos or microservice layouts who need one GrepAI semantic index across related repositories.
Skip if: Developers with a single small repo who do not need cross-project workspace grouping.
When should I use this skill?
User mentions GrepAI workspaces, monorepo search, microservices indexing, or searching multiple related projects.
What you get
GrepAI workspace config with unified semantic index across grouped projects
- Workspace configuration
- Unified semantic search index
- Shared cross-repo GrepAI settings
Files
GrepAI Workspaces
This skill covers using GrepAI workspaces to manage multiple related projects with a unified search index.
When to Use This Skill
- Working with monorepos
- Searching across multiple related projects
- Managing microservices architecture
- Organizing large codebases
What are Workspaces?
Workspaces allow you to:
- Group multiple projects together
- Search across all projects at once
- Or search specific projects within the workspace
- Share configuration across projects
Creating a Workspace
grepai workspace create my-workspaceOutput:
✅ Workspace 'my-workspace' created
Location: ~/.grepai/workspaces/my-workspace/
Next: Add projects with 'grepai workspace add'Adding Projects
# Add first project
grepai workspace add my-workspace /path/to/frontend
# Add more projects
grepai workspace add my-workspace /path/to/backend
grepai workspace add my-workspace /path/to/shared-libOutput:
✅ Added '/path/to/frontend' to workspace 'my-workspace'
Projects in workspace:
1. frontend (/path/to/frontend)
Run 'grepai watch --workspace my-workspace' to index all projects.Listing Workspaces
grepai workspace listOutput:
📁 Workspaces
1. my-workspace
- Projects: 3
- Status: Not indexed
2. work-projects
- Projects: 5
- Status: Indexed (updated 2h ago)Viewing Workspace Details
grepai workspace show my-workspaceOutput:
📁 Workspace: my-workspace
Projects:
1. frontend
Path: /path/to/frontend
Files: 450
Last indexed: 2025-01-28 10:30
2. backend
Path: /path/to/backend
Files: 320
Last indexed: 2025-01-28 10:30
3. shared-lib
Path: /path/to/shared-lib
Files: 85
Last indexed: 2025-01-28 10:30
Total: 855 files, 4,200 chunksIndexing a Workspace
# Index all projects in workspace
grepai watch --workspace my-workspaceOutput:
🔍 Indexing workspace 'my-workspace'
[1/3] frontend...
Found 450 files, 2,100 chunks
[2/3] backend...
Found 320 files, 1,500 chunks
[3/3] shared-lib...
Found 85 files, 600 chunks
Total: 855 files, 4,200 chunks indexed
Watching for changes...Background Indexing
grepai watch --workspace my-workspace --backgroundSearching Workspaces
Search All Projects
grepai search --workspace my-workspace "user authentication"Results include project context:
Score: 0.89 | [backend] src/auth/middleware.go:15-45
──────────────────────────────────────────
func AuthMiddleware() ...
Score: 0.85 | [frontend] src/hooks/useAuth.ts:10-30
──────────────────────────────────────────
export function useAuth() ...
Score: 0.78 | [shared-lib] src/types/auth.ts:5-25
──────────────────────────────────────────
export interface AuthState ...Search Specific Project
grepai search --workspace my-workspace --project frontend "form validation"Only searches the frontend project.
Workspace Status
grepai workspace status my-workspaceOutput:
📊 Workspace Status: my-workspace
Projects: 3
Total files: 855
Total chunks: 4,200
Index size: 45 MB
Per-project breakdown:
┌─────────────┬───────┬────────┬──────────┐
│ Project │ Files │ Chunks │ Updated │
├─────────────┼───────┼────────┼──────────┤
│ frontend │ 450 │ 2,100 │ 2h ago │
│ backend │ 320 │ 1,500 │ 2h ago │
│ shared-lib │ 85 │ 600 │ 2h ago │
└─────────────┴───────┴────────┴──────────┘
Daemon: Running (PID 12345)Removing Projects from Workspace
grepai workspace remove my-workspace /path/to/old-projectDeleting a Workspace
grepai workspace delete my-workspaceThis removes the workspace configuration but NOT the project files.
Workspace Configuration
Workspaces store config in ~/.grepai/workspaces/<name>/:
~/.grepai/workspaces/my-workspace/
├── workspace.yaml # Workspace config
├── index.gob # Combined index
└── symbols.gob # Combined symbolsworkspace.yaml
name: my-workspace
created: 2025-01-28T10:00:00Z
projects:
- name: frontend
path: /path/to/frontend
- name: backend
path: /path/to/backend
- name: shared-lib
path: /path/to/shared-lib
# Optional: override global config per workspace
embedder:
provider: ollama
model: nomic-embed-text
ignore:
- node_modules
- distMCP with Workspaces
Use workspaces with MCP servers:
{
"mcpServers": {
"grepai": {
"command": "grepai",
"args": ["mcp-serve", "--workspace", "my-workspace"]
}
}
}Use Cases
Monorepo
# Full monorepo
grepai workspace create monorepo
grepai workspace add monorepo /path/to/monorepo/apps/web
grepai workspace add monorepo /path/to/monorepo/apps/mobile
grepai workspace add monorepo /path/to/monorepo/packages/ui
grepai workspace add monorepo /path/to/monorepo/packages/coreMicroservices
# Related microservices
grepai workspace create services
grepai workspace add services /path/to/user-service
grepai workspace add services /path/to/order-service
grepai workspace add services /path/to/payment-service
grepai workspace add services /path/to/notification-serviceFrontend + Backend
# Full stack
grepai workspace create fullstack
grepai workspace add fullstack /path/to/frontend
grepai workspace add fullstack /path/to/backend
grepai workspace add fullstack /path/to/shared-typesCross-Project Search Examples
Find All API Endpoints
grepai search --workspace services "REST API endpoint handler"Find Shared Type Usage
grepai search --workspace fullstack "User interface definition"Find Cross-Project Dependencies
# What calls the shared auth library?
grepai trace callers --workspace fullstack "validateToken"Best Practices
1. Name descriptively: ecommerce-stack not ws1 2. Group related projects: Only projects that you'd search together 3. One daemon per workspace: Run grepai watch --workspace 4. Use project filter: When you know which project to search 5. Update after major changes: Re-index after adding/removing files
Common Issues
❌ Problem: Workspace not found ✅ Solution: Check workspace exists: grepai workspace list
❌ Problem: Project paths changed ✅ Solution: Remove old path, add new path:
grepai workspace remove my-workspace /old/path
grepai workspace add my-workspace /new/path❌ Problem: Search returns mixed results ✅ Solution: Use --project flag to filter:
grepai search --workspace ws --project backend "query"Output Format
Workspace overview:
📁 Workspace: my-workspace
Configuration:
- Location: ~/.grepai/workspaces/my-workspace/
- Created: 2025-01-28
Projects (3):
┌─────────────┬──────────────────────────┬───────┐
│ Name │ Path │ Files │
├─────────────┼──────────────────────────┼───────┤
│ frontend │ /path/to/frontend │ 450 │
│ backend │ /path/to/backend │ 320 │
│ shared-lib │ /path/to/shared-lib │ 85 │
└─────────────┴──────────────────────────┴───────┘
Commands:
- Index: grepai watch --workspace my-workspace
- Search: grepai search --workspace my-workspace "query"
- Status: grepai workspace status my-workspaceRelated skills
How it compares
Pick grepai-workspaces over single-repo GrepAI setup when code search must cross repository boundaries in one index.
FAQ
What problems do GrepAI workspaces solve?
GrepAI workspaces let developers group monorepos, microservices, or related projects under one semantic search index. grepai-workspaces configures shared settings so watch indexing and queries span every repo in the workspace.
How do you create a GrepAI workspace?
grepai-workspaces uses the grepai CLI—commands starting with `grepai wo`—to create and manage multi-project workspaces. Developers define member repos, then search all projects or scoped subsets from one index.
Is Grepai Workspaces safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.