slm-profile

# slm-profile — Workspace Isolation and Profile Switching A profile is a fully isolated memory workspace. Each profile has its own: - Memory facts (nothing bleeds across profiles by default) - Code graph index (separate per repo/project) - Active MCP tool set (determined by profile tier) - Retention policy and decay settings Profiles are the right tool when you have genuinely separate contexts: a personal project, a client engagement, a production vs staging environment. --- ## Available profiles and their tool sets | Profile | Tools | When to use | |---------|-------|-------------| | `core` | 14 tools — remember, recall, search, session, optimize | Minimal footprint, no code tools | | `code` | 24 tools — core + 6 code-graph tools + switch_profile + 3 bounded-loop tools | Default for IDE/coding agents | | `full` | 42 tools — code + all memory ops + mesh + bounded loops | Multi-session, team workflows | | `power` | 54 tools — full + governance + behavioral tools | Enterprise, admin, audit use cases | | `mesh` | 8 tools — mesh coordination only | Lightweight cross-session signalling | The profile is set at MCP server startup via `SLM_MCP_PROFILE` in the MCP config. `switch_profile` lets you change it at runtime without a restart. --- ## Checking the active profile ```bash slm status --json ``` The `profile` field in the output is the currently active profile name. Or via MCP (works in any profile): ```bash slm status ``` --- ## Switching profiles at runtime (v3.8....