CLI: support project visibility when creating projects in a teams workspace

[groksrc]

Problem

When creating a project in a teams workspace via the CLI (bm project add), there is no way to set the project visibility. The web app supports three visibility levels:

• workspace ("Everyone — all workspace members") — default, visible to all
• shared ("Invite Only — selected members") — only creator + explicitly invited members
• private — auto-created "My Notes", only visible to the creator

The CLI currently creates all projects with the default workspace visibility. There is no --visibility flag or interactive prompt.

Expected Behavior

The CLI should support setting visibility when creating a project in a teams workspace:

# Create a project visible to all team members (default)
bm project add research --cloud

# Create a project visible only to invited members
bm project add research --cloud --visibility shared

# Interactive: prompt for visibility when multiple workspaces exist
bm project add research --cloud --workspace "Basic Memory"

For shared projects, member management would still happen through the web app (or a future bm project share command).

Context

The cloud API already supports this via POST /api/projects with visibility control. The web app's "Add New Project" dialog exposes the visibility dropdown. The CLI just needs to pass the visibility through when creating cloud projects.

Related cloud endpoints:

• POST /api/projects — create shared project with visibility
• POST /api/projects/{id}/members — add members to shared project
• PATCH /api/projects/{id}/members/{share_id} — update member access level
• DELETE /api/projects/{id}/members/{user_id} — remove member

[claude]

Claude finished @groksrc's task in 2m 0s —— View job

---

Issue Triage

• Gather context and read issue
• Explore codebase to understand current implementation
• Classify issue type, priority, and complexity
• Add appropriate labels
• Check for duplicates
• Provide triage summary

---

Triage Summary

Type: Feature Request — Enhancement to existing CLI functionality

Priority: Medium — Missing feature for teams workspace users; not a critical bug but impacts usability for multi-user setups

Component: CLI + Cloud

Complexity: Medium — Requires changes across multiple layers but no architectural changes

---

Codebase Analysis

The feature is well-scoped. Here's what's needed:

1. ProjectInfoRequest schema (src/basic_memory/schemas/project_info.py:130-136) — needs a visibility field added
2. CloudProjectCreateRequest schema (src/basic_memory/schemas/cloud.py:33-38) — needs a visibility field
3. CLI add_project command (src/basic_memory/cli/commands/project.py:251-351) — needs --visibility option with validation (workspace/shared/private)
4. API router (src/basic_memory/api/v2/routers/project_router.py:70-140) — needs to pass visibility through to cloud API

Notably, ProjectItem already has is_private: bool = False as a placeholder injected by the cloud layer (src/basic_memory/schemas/project_info.py), suggesting visibility was planned from the start.

No database migration needed — visibility is handled entirely by the cloud layer, not stored locally.

---

No Duplicates Found

No existing issues cover this exact feature.

---

Labels added: enhancement, cloud

Note: Labels cli, medium, feature don't exist in this repo — adding enhancement and cloud which were available.