@unifiedmemory/cli 1.0.0 → 1.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unifiedmemory/cli",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "UnifiedMemory CLI - AI code assistant integration",
   "main": "index.js",
   "type": "module",
@@ -31,13 +31,15 @@
   },
   "homepage": "https://unifiedmemory.ai",
   "dependencies": {
+    "@iarna/toml": "^2.2.5",
     "@modelcontextprotocol/sdk": "^1.0.0",
+    "axios": "^1.6.2",
     "chalk": "^5.3.0",
     "commander": "^11.1.0",
+    "dotenv": "^16.6.1",
+    "fs-extra": "^11.2.0",
     "inquirer": "^13.0.1",
-    "open": "^10.0.3",
-    "axios": "^1.6.2",
-    "fs-extra": "^11.2.0"
+    "open": "^10.0.3"
   },
   "devDependencies": {
     "pkg": "^5.8.1"

package/HOOK_SETUP.md

@@ -1,338 +0,0 @@
-# UnifiedMemory CLI Hook Integration
-
-## Overview
-
-This document explains how to set up automatic vault recording using Claude Code hooks with the `um note create` CLI command.
-
-## Background
-
-Claude Code's "prompt" type hooks are not supported outside REPL mode. To work around this limitation, we've implemented a command-style hook that calls the `um note create` CLI command directly.
-
-## Components
-
-### 1. CLI Command: `um note create`
-
-A new CLI command that creates notes in the vault:
-
-```bash
-um note create "<summary text>" [options]
-```
-
-**Options**:
-- `--topic <topic>` - Topic for the note (default: "general")
-- `--source <source>` - Source identifier (default: "um-cli")
-- `--confidence <confidence>` - Confidence score 0-1 (default: "0.7")
-- `--tags <tags>` - Comma-separated tags
-- `--metadata <json>` - Additional metadata as JSON string
-
-**Example**:
-```bash
-um note create "Completed implementation of user authentication" \
-  --topic "development" \
-  --source "manual" \
-  --confidence "0.9" \
-  --tags "auth,feature,completed"
-```
-
-### 2. Hook Script: `.claude/hooks/post-exit-plan-mode.sh`
-
-A shell script that automatically calls `um note create` after exiting plan mode:
-
-**Location**: `<project>/.claude/hooks/post-exit-plan-mode.sh`
-
-**Requirements**:
-- Must be executable (`chmod +x`)
-- Update the `UM_CLI` path to point to your um-cli installation
-
-### 3. Hook Configuration: `.claude/settings.json`
-
-Configure Claude Code to run the hook:
-
-```json
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "ExitPlanMode",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "./.claude/hooks/post-exit-plan-mode.sh 'Plan summary: Completed plan mode session'",
-            "statusMessage": "Recording plan to vault..."
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-## Setup Instructions
-
-### Step 1: Install um-cli
-
-The `um` CLI should be installed and configured:
-
-```bash
-# Authenticate
-um login
-
-# Initialize project
-cd <your-project>
-um init
-```
-
-This creates:
-- `~/.um/auth.json` - User authentication
-- `.um/config.json` - Project configuration (org_id, project_id)
-
-### Step 2: Create Hook Script
-
-Create `.claude/hooks/post-exit-plan-mode.sh` in your project:
-
-```bash
-mkdir -p .claude/hooks
-cat > .claude/hooks/post-exit-plan-mode.sh << 'EOF'
-#!/usr/bin/env bash
-set -e
-
-SUMMARY="$@"
-if [ -z "$SUMMARY" ]; then
-  SUMMARY=$(cat)
-fi
-if [ -z "$SUMMARY" ]; then
-  SUMMARY="Plan completed and exited plan mode"
-fi
-
-# Update this path to your um-cli installation
-UM_CLI="/path/to/vault/um-cli/index.js"
-
-if [ ! -f "$UM_CLI" ]; then
-  echo "Error: um CLI not found at $UM_CLI" >&2
-  exit 1
-fi
-
-node "$UM_CLI" note create "$SUMMARY" \
-  --topic "plans" \
-  --source "claude-code-hook" \
-  --confidence "0.8" \
-  --tags "plan,automated" \
-  2>&1
-
-exit 0
-EOF
-
-chmod +x .claude/hooks/post-exit-plan-mode.sh
-```
-
-### Step 3: Configure Hook in Settings
-
-Update `.claude/settings.json` (or `.claude/settings.local.json`):
-
-```json
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "ExitPlanMode",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "./.claude/hooks/post-exit-plan-mode.sh 'Plan summary: Completed plan mode session'",
-            "statusMessage": "Recording plan to vault..."
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-### Step 4: Test the Setup
-
-Test the CLI command manually:
-
-```bash
-cd <your-project>
-um note create "Test note from CLI" --topic "testing"
-```
-
-Test the hook script:
-
-```bash
-./.claude/hooks/post-exit-plan-mode.sh "Test note from hook"
-```
-
-## How It Works
-
-### Authentication Flow
-
-1. **User Context**: Loaded from `~/.um/auth.json` (created by `um login`)
-   - User ID from JWT `decoded.sub`
-   - Organization ID from `selectedOrg.id` or fallback to user ID
-
-2. **Project Context**: Loaded from `.um/config.json` (created by `um init`)
-   - Organization ID
-   - Project ID
-   - Project name
-
-3. **API Call**: The `um note create` command:
-   - Builds authentication headers (Authorization, X-Org-Id, X-User-Id)
-   - Injects org/proj/user into tool arguments
-   - Calls the MCP gateway's `create_note` tool
-   - Returns success/failure status
-
-### Hook Execution
-
-When you exit plan mode in Claude Code:
-
-1. Claude Code detects `ExitPlanMode` tool usage
-2. Matches the `PostToolUse` hook with `matcher: "ExitPlanMode"`
-3. Executes the command hook: `.claude/hooks/post-exit-plan-mode.sh`
-4. Hook script calls: `node um-cli/index.js note create "..."`
-5. CLI command creates the note in vault
-6. Success/failure status shown in Claude Code
-
-## Troubleshooting
-
-### Error: "Not authenticated"
-
-```bash
-# Re-authenticate
-um login
-```
-
-### Error: "No project configuration found"
-
-```bash
-# Re-initialize project
-cd <your-project>
-um init
-```
-
-### Error: "um CLI not found"
-
-Update the `UM_CLI` path in the hook script to point to your installation:
-
-```bash
-UM_CLI="/absolute/path/to/vault/um-cli/index.js"
-```
-
-### Error: Hook not executing
-
-1. Ensure the hook script is executable:
-   ```bash
-   chmod +x .claude/hooks/post-exit-plan-mode.sh
-   ```
-
-2. Test the hook manually:
-   ```bash
-   ./.claude/hooks/post-exit-plan-mode.sh "Test message"
-   ```
-
-3. Check Claude Code settings are valid JSON
-
-### Error: "Tool execution failed"
-
-Check authentication headers are being set correctly:
-
-```bash
-# Check auth file exists
-cat ~/.um/auth.json | jq .
-
-# Check project config exists
-cat .um/config.json | jq .
-```
-
-## Customization
-
-### Change Hook Trigger
-
-Instead of `PostToolUse:ExitPlanMode`, you can trigger on other events:
-
-```json
-{
-  "hooks": {
-    "SessionEnd": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "./.claude/hooks/record-session.sh 'Session summary'",
-            "statusMessage": "Recording session to vault..."
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-Available hook types:
-- `PreToolUse` - Before any tool execution
-- `PostToolUse` - After any tool execution
-- `PostToolUseFailure` - After tool execution fails
-- `SessionStart` - When session starts
-- `SessionEnd` - When session ends
-- `PreCompact` - Before context summarization
-
-### Customize Note Properties
-
-Edit the hook script to change topic, source, confidence, or tags:
-
-```bash
-node "$UM_CLI" note create "$SUMMARY" \
-  --topic "my-custom-topic" \
-  --source "my-source" \
-  --confidence "0.9" \
-  --tags "custom,tags,here" \
-  2>&1
-```
-
-### Add Metadata
-
-Pass JSON metadata:
-
-```bash
-node "$UM_CLI" note create "$SUMMARY" \
-  --metadata '{"branch":"main","commit":"abc123"}' \
-  2>&1
-```
-
-## Security Notes
-
-- Authentication tokens are stored in `~/.um/auth.json` (user-only permissions)
-- Project config in `.um/config.json` contains no secrets (only IDs)
-- The CLI command inherits user's authentication automatically
-- Hook scripts run with the same permissions as Claude Code
-
-## Alternatives to Hooks
-
-If you don't want automatic recording, you can manually call the CLI:
-
-```bash
-# After exiting plan mode
-um note create "Completed feature X implementation" \
-  --topic "development" \
-  --confidence "0.9"
-```
-
-Or ask Claude Code to record notes explicitly:
-
-```
-User: Record this plan to the vault
-Claude: [Uses mcp__vault__create_note tool directly]
-```
-
-## Files Modified
-
-This implementation required the following changes:
-
-1. **New file**: `um-cli/commands/record.js` - CLI command implementation
-2. **Modified**: `um-cli/index.js` - Added `note create` command registration
-3. **New file**: `.claude/hooks/post-exit-plan-mode.sh` - Hook script (per-project)
-4. **Modified**: `.claude/settings.json` - Hook configuration (per-project)
-
-## Summary
-
-This solution bypasses the "prompt hooks not supported outside REPL" limitation by using command-style hooks to call the `um note create` CLI command directly. All authentication infrastructure (schema transformation, parameter injection, headers) works perfectly - the only issue was with Claude Code's hook mechanism, which we've now resolved.

package/lib/hooks.js

@@ -1,43 +0,0 @@
-export function generateClaudePromptSubmitHook(mcpUrl, accessToken) {
-  return `#!/bin/bash
-# UnifiedMemory Context Recording Hook
-
-HOOK_DATA=$(cat)
-
-# Read project config
-UM_CONFIG=".um/config.json"
-PROJECT_ID=""
-ORG_ID=""
-
-if [ -f "$UM_CONFIG" ]; then
-    PROJECT_ID=$(jq -r '.project_id // empty' "$UM_CONFIG" 2>/dev/null)
-    ORG_ID=$(jq -r '.org_id // empty' "$UM_CONFIG" 2>/dev/null)
-fi
-
-# Extract context
-USER_MESSAGE=$(echo "$HOOK_DATA" | jq -r '.userMessage // empty')
-CONVERSATION_ID=$(echo "$HOOK_DATA" | jq -r '.conversationId // empty')
-WORKING_DIR=$(pwd)
-TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
-
-# Send to UnifiedMemory (if configured)
-if [ -n "$PROJECT_ID" ]; then
-    curl -s -X POST "${mcpUrl}/hooks/pre-submit" \\
-      -H "Content-Type: application/json" \\
-      -H "Authorization: Bearer ${accessToken}" \\
-      -H "X-Project-Id: $PROJECT_ID" \\
-      -H "X-Org-Id: $ORG_ID" \\
-      -d "{
-        \\"event\\": \\"pre_response\\",
-        \\"timestamp\\": \\"$TIMESTAMP\\",
-        \\"conversation_id\\": \\"$CONVERSATION_ID\\",
-        \\"working_directory\\": \\"$WORKING_DIR\\",
-        \\"user_message\\": \\"$USER_MESSAGE\\",
-        \\"project_id\\": \\"$PROJECT_ID\\"
-      }" >/dev/null 2>&1
-fi
-
-# Pass through original data
-echo "$HOOK_DATA"
-`;
-}