← ClaudeAtlas

memforge-setuplisted

Inspect and configure MemForge workspace routing for Git repositories, ordinary directories, and automatic hooks. Use when the user asks to bind a local project to a workspace, change or remove that binding, configure the hook fallback, or diagnose workspace selection.
shno-labs/mem-forge · ★ 4 · AI & Automation · score 58
Install: claude install-skill shno-labs/mem-forge
# MemForge Workspace Setup Use the bundled `scripts/workspace_config.py` helper. It owns only `~/.memforge/workspace-bindings.json`; never ask the user to edit the file by hand. ## Routing model - A Git checkout with an `origin` is stored in `repository_bindings` using the normalized origin, so its worktrees and moved checkouts share a binding. - Any ordinary non-Git directory is stored in `directory_bindings` by absolute path. Descendants inherit it and the most-specific directory wins. - An explicit tool `workspace_id` overrides either binding for that call. - `hook_workspace_id` is only a fallback for automatic hooks. Interactive MCP tools never use it. - API URL and credentials remain in the client's existing configuration. This skill never writes or displays credentials and never edits MCP registration. ## Commands Resolve the helper relative to this skill, then use: ```bash python3 "<skill-dir>/scripts/workspace_config.py" --client CLIENT inspect --path "$PWD" python3 "<skill-dir>/scripts/workspace_config.py" --client CLIENT bind --path "$PWD" --workspace WORKSPACE python3 "<skill-dir>/scripts/workspace_config.py" --client CLIENT unbind --path "$PWD" python3 "<skill-dir>/scripts/workspace_config.py" --client CLIENT set-hook-workspace --workspace WORKSPACE python3 "<skill-dir>/scripts/workspace_config.py" --client CLIENT clear-hook-workspace ``` `CLIENT` is `codex` or `claude-code`. Binding commands validate the workspace against the live configured target