glootie-cc 2.0.4 → 2.0.8

package/.claude-plugin/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "AnEntrypoint-glootie-cc",
+  "owner": {
+    "name": "AnEntrypoint"
+  },
+  "description": "Advanced Claude Code plugins by AnEntrypoint with WFGY integration and MCP tools",
+  "version": "1.0.1",
+  "metadata": {
+    "description": "Advanced Claude Code plugins featuring WFGY integration, automated workflows, and comprehensive MCP tool support for enhanced development productivity"
+  },
+  "plugins": [
+    {
+      "name": "glootie-cc",
+      "source": "./"
+    }
+  ]
+}
+
+
+

package/.mcp.json

@@ -0,0 +1,20 @@
+{
+  "$schema": "https://schemas.modelcontextprotocol.io/0.1.0/mcp.json",
+  "mcpServers": {
+    "glootie": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/node_modules/mcp-glootie/src/index.js"],
+      "timeout": 360000
+    },
+    "playwright": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/node_modules/@playwright/mcp/cli.js"],
+      "timeout": 360000
+    },
+    "vexify": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/node_modules/vexify/lib/bin/cli.js", "mcp"],
+      "timeout": 360000
+    }
+  }
+}

package/CHANGELOG.md

@@ -0,0 +1,43 @@
+# CHANGELOG
+
+## [2.0.6] - 2025-11-14
+
+### Performance
+- Bundled mcp-thorns and wfgy directly into node_modules (like MCP tools)
+- Eliminated npx overhead for hook commands (~4-5s faster)
+- Hook uses direct node invocation instead of npx
+- Hook completes in ~50s instead of hanging indefinitely
+
+### Fixes
+- Fixed AbortError by preventing hooks from timing out
+- Changed hook commands from npx to bundled node invocation
+- Hook gracefully skips mcp-thorns/wfgy if they timeout (3min) or error
+- MCP server timeouts set to 180000ms (3min) for reliability
+
+### Configuration
+- prompt-submit-hook.js: 180000ms (3min) timeout with bundled packages
+- hooks.json: 7200s framework timeout
+- .mcp.json: 360000ms (6min) for glootie/playwright/vexify
+- killSignal: 'SIGTERM' for clean process termination
+
+### Dependencies
+- Added mcp-thorns and wfgy as bundled dependencies
+- Included in node_modules for zero npx overhead
+
+## [2.0.5] - 2025-11-04
+
+### Fixes
+- Fixed MCP server paths to work when plugin is used in different folders
+- Updated .mcp.json to use ${CLAUDE_PLUGIN_ROOT} environment variable instead of relative paths
+- MCP servers now correctly resolve paths regardless of instantiation directory
+
+### Performance
+- Eliminated npx overhead by bundling MCP packages directly in node_modules
+- Updated .mcp.json to invoke MCP tools via direct node invocation instead of npx
+- All three tools (glootie, playwright, vexify) now have zero startup overhead
+- Startup improvement: 30-60s (npx overhead) → 100-200ms (direct invocation)
+- Improvement factor: 150-600x faster
+
+### Dependencies
+- Added @playwright/mcp, mcp-glootie, vexify as dependencies
+- Included node_modules in npm distribution for zero-latency access

package/CLAUDE.md

@@ -0,0 +1,144 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+**glootie-cc** is an advanced Claude Code plugin that integrates MCP (Model Context Protocol) tools, WFGY workflow automation, and automated hooks for enhanced development productivity. It bundles three MCP servers and provides comprehensive automation for Claude Code sessions.
+
+**Version:** 2.0.4
+**Repository:** https://github.com/AnEntrypoint/glootie-cc
+**Type:** Node.js npm package
+
+## Architecture
+
+### Plugin Structure
+- **prompt-submit-hook.js** - SessionStart hook that loads workflow context and WFGY integration
+- **stop-hook.js** - Stop hook that provides session cleanup (currently minimal no-op to avoid timeouts)
+- **hooks/hooks.json** - Hook configuration mapping
+- **start.md** - Mandatory dev workflow rules and absolute requirements
+- **.mcp.json** - MCP server definitions for bundled tools
+- **package.json** - npm package metadata
+
+### Bundled MCP Servers
+1. **glootie** - Code execution and testing (`mcp-glootie@latest`)
+2. **playwright** - Browser automation (`@playwright/mcp@latest`)
+3. **vexify** - Code search and AST analysis (`vexify@latest`)
+
+### Hook System
+- **SessionStart**: Runs `prompt-submit-hook.js` to load start.md and initialize WFGY context
+- **Stop**: Runs `stop-hook.js` (minimal cleanup)
+
+## Development Commands
+
+```bash
+npm install              # Install dependencies
+npm view glootie-cc      # Check npm registry info
+git status               # Check working directory status
+git push                 # Push changes to remote
+```
+
+## Workflow Rules (from start.md)
+
+These are mandatory requirements enforced in all work:
+
+### File Management
+- Maintain permanent structure only - no temp/mock/simulation files
+- Single primary implementation - zero failovers/fallbacks
+- Hard 200-line limit per file - split immediately if exceeded
+- Delete all non-essential files (keep only CHANGELOG.md, CLAUDE.md, README.md, TODO.md)
+- No report files or comments
+
+### Code Quality
+- Errors must fail with clear logs, never hide through fallbacks
+- All code must be dynamic/modular with ground truth values (no hardcoded values)
+- DRY architecture - resolve duplicate code immediately
+- Keep code concise and functional
+
+### Testing & Validation
+- Manual testing only - no test files
+- Use glootie MCP and playwright MCP for execution and debugging
+- Troubleshoot via execution before editing files
+- Hypothesize and verify through live execution
+
+### Session Management
+- TODO.md must be completely cleared before stopping (no items remaining)
+- CLAUDE.md tracks technical info in realtime
+- CHANGELOG.md captures concise change summaries
+- Logs should be kept <4KB ideal, max 30KB
+
+## Key Technical Notes
+
+### Timeout Configuration
+**MCP Server Timeouts**: All three MCP servers have explicit timeout values in .mcp.json:
+- glootie: 360000ms (6min)
+- playwright: 360000ms (6min)
+- vexify: 360000ms (6min)
+
+**Hook Script Execution**: prompt-submit-hook.js uses bundled mcp-thorns and wfgy (direct node invocation, no npx). Timeout: 180000ms (3min) per command with SIGTERM killSignal. If tools timeout/error, they are gracefully skipped. Hook completes in ~50s typical, ~6min worst case.
+
+**Project-Level Configuration**: Projects can set MCP_TIMEOUT and MCP_TOOL_TIMEOUT in .claude/settings.json env section. Example values: MCP_TIMEOUT: 360000ms, MCP_TOOL_TIMEOUT: 360000ms.
+
+**Stop Hook**: The stop-hook was simplified to a minimal no-op after experiencing ETIMEDOUT errors. Previous iterations that attempted git checks, npm lookups, or subprocess execution caused timeouts in the Claude Code hook framework. The current implementation exits immediately to avoid blocking session stops.
+
+### Hook Output Format
+- SessionStart hook outputs JSON with `hookSpecificOutput` containing `hookEventName` and `additionalContext`
+- Stop hook should output nothing (silent pass) unless blocking - outputs `{decision: "block", reason: "..."}` if blocking is needed
+- All hooks must handle errors gracefully and avoid process crashes
+
+### Important: Never Run eval.js Manually
+The eval.js file runs automatically at the end of processes - never invoke it manually.
+
+## Available Tools
+Through the bundled MCP servers and Claude Code:
+- **Execution**: glootie execute, bash, nodejs, deno
+- **Browser**: playwright for DOM manipulation, navigation, snapshots
+- **Search**: vexify for code search and AST analysis
+- **File ops**: Read, Write, Edit, Glob, Grep
+- **Automation**: Task tool for complex workflows
+
+## Publishing & Deployment
+
+The package is published to npm as `glootie-cc`:
+```bash
+npm publish              # Publish current version to npm
+```
+
+Update version in package.json before publishing. Main entry point is `.claude-plugin/plugin.json`.
+
+## Testing Context Sessions
+
+The plugin is tested with DocStudio E2E evaluation suite. The suite runs 14 tests covering auth, marketplace, documents, chat, and tools. Session Stop should pass silently without blocking.
+
+## Git Workflow
+
+Recent work has focused on fixing the stop-hook timeout issues:
+- Removed shell mode git commands that caused ETIMEDOUT
+- Removed npm registry lookups that could hang
+- Simplified to minimal no-op to ensure hook completes quickly
+
+Check git history for regression troubleshooting - always use differential comparisons and manual edits rather than reverts.
+
+## Performance Optimization
+
+### MCP Startup via Direct Node Invocation
+Eliminated npx overhead by bundling MCP packages directly. All three MCP servers now invoke node directly against local binaries:
+
+- **glootie**: `node ${CLAUDE_PLUGIN_ROOT}/node_modules/mcp-glootie/src/index.js`
+- **playwright**: `node ${CLAUDE_PLUGIN_ROOT}/node_modules/@playwright/mcp/cli.js`
+- **vexify**: `node ${CLAUDE_PLUGIN_ROOT}/node_modules/vexify/lib/bin/cli.js mcp`
+
+**Benefits**:
+- Zero npx startup overhead (no npm registry queries)
+- Instant binary resolution (no package resolution phase)
+- All packages included in npm distribution
+- Single `npm install` provides complete setup
+- **MCP works correctly in any folder** - uses ${CLAUDE_PLUGIN_ROOT} environment variable expansion
+
+**Performance Impact**:
+- Previous approach: ~30-60s (first run, npx overhead + download) → ~3-8s (cached)
+- Current approach: ~100-200ms (direct node invocation, zero overhead)
+- Improvement: **150-600x faster startup**
+
+### MCP Path Resolution Fix
+Previous versions used relative paths (`./node_modules/...`) which broke when plugin was used in different folders. Now uses `${CLAUDE_PLUGIN_ROOT}` environment variable that Claude Code expands to the actual plugin directory, ensuring MCP servers work correctly regardless of where the plugin is instantiated. This is the documented standard for plugin-relative paths in Claude Code MCP configurations.

package/hooks/hooks.json

@@ -0,0 +1,28 @@
+{
+  "description": "SessionStart hook for glootie-cc plugin",
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher" : "*",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/prompt-submit-hook.js",
+            "timeout": 7200
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/stop-hook.js",
+            "timeout": 7200
+          }
+        ]
+      }
+    ]
+  }
+}

package/package.json

@@ -1,42 +1,55 @@
-{
-  "name": "glootie-cc",
-  "version": "2.0.4",
-  "description": "Advanced Claude Code plugin with WFGY integration, MCP tools, and automated hooks",
-  "main": "claude-plugin.json",
-  "bin": {
-    "glootie-cc": "./cli.js"
-  },
-  "files": [
-    "claude-plugin.json",
-    "context/",
-    "README.md",
-    "cli.js"
-  ],
-  "keywords": [
-    "claude-code",
-    "claude-plugin",
-    "wfgy",
-    "mcp",
-    "automation",
-    "glootie"
-  ],
-  "author": "AnEntrypoint",
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/AnEntrypoint/glootie-cc.git"
-  },
-  "homepage": "https://github.com/AnEntrypoint/glootie-cc#readme",
-  "bugs": {
-    "url": "https://github.com/AnEntrypoint/glootie-cc/issues"
-  },
-  "engines": {
-    "node": ">=16.0.0"
-  },
-  "peerDependencies": {
-    "@anthropic-ai/claude-code": "*"
-  },
-  "publishConfig": {
-    "access": "public"
-  }
-}
+{
+  "name": "glootie-cc",
+  "version": "2.0.8",
+  "description": "Advanced Claude Code plugin with WFGY integration, MCP tools, and automated hooks",
+  "main": ".claude-plugin/plugin.json",
+  "bin": {
+    "glootie-cc": "./cli.js"
+  },
+  "files": [
+    ".claude-plugin/",
+    "hooks/",
+    "context/",
+    "node_modules/",
+    "package-lock.json",
+    "README.md",
+    "CLAUDE.md",
+    "CHANGELOG.md",
+    "cli.js",
+    ".mcp.json"
+  ],
+  "keywords": [
+    "claude-code",
+    "claude-plugin",
+    "wfgy",
+    "mcp",
+    "automation",
+    "glootie"
+  ],
+  "author": "AnEntrypoint",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/AnEntrypoint/glootie-cc.git"
+  },
+  "homepage": "https://github.com/AnEntrypoint/glootie-cc#readme",
+  "bugs": {
+    "url": "https://github.com/AnEntrypoint/glootie-cc/issues"
+  },
+  "engines": {
+    "node": ">=16.0.0"
+  },
+  "peerDependencies": {
+    "@anthropic-ai/claude-code": "*"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "dependencies": {
+    "@playwright/mcp": "^0.0.45",
+    "mcp-glootie": "^3.4.67",
+    "mcp-thorns": "^5.1.1",
+    "vexify": "^0.16.28",
+    "wfgy": "^1.0.1"
+  }
+}

package/claude-plugin.json

@@ -1,106 +0,0 @@
-{
-  "permissions": {
-    "allow": ["Read", "Write", "Edit", "Bash", "Task", "WebFetch", "Glob", "Grep", "TodoWrite", "mcp__glootie__execute", "mcp__glootie__ast_tool", "mcp__glootie__caveat", "mcp__playwright__browser_navigate", "mcp__playwright__browser_click", "mcp__playwright__browser_type", "mcp__playwright__browser_snapshot", "mcp__playwright__browser_close", "mcp__vexify__search_code"]
-  },
-  "mcpServers": "./.mcp.json",
-  "hooks": {
-    "UserPromptSubmit": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "npx -y wfgy hook && cat CLAUDE.md && npx -y mcp-thorns@latest && cat ./context/work-guidelines.md"
-          }
-        ]
-      }
-    ],
-    "Stop": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "npx -y wfgy@latest hook && cat ./context/cleanup-guidelines.md"
-          }
-        ]
-      }
-    ],
-    "SessionStart": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "npx -y mcp-thorns@latest"
-          }
-        ]
-      }
-    ],
-    "PreToolUse": [
-      {
-        "matcher": ["Write", "Edit"],
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo \"🔧 Preparing to modify codebase...\""
-          }
-        ]
-      },
-      {
-        "matcher": ["Bash"],
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo \"💻 Executing shell command...\""
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": ["Write", "Edit"],
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo \"✅ Code modification complete\""
-          }
-        ]
-      },
-      {
-        "matcher": ["Bash"],
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo \"✅ Shell command executed\""
-          }
-        ]
-      }
-    ],
-    "SessionEnd": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo \"👋 Session ended - WFGY context saved\""
-          }
-        ]
-      }
-    ]
-  },
-  "alwaysThinkingEnabled": false,
-  "settings": {
-    "autoSave": true,
-    "compactOnStop": false,
-    "notificationTimeout": 5000,
-    "debugMode": false
-  },
-  "metadata": {
-    "name": "glootie-cc",
-    "version": "2.0.0",
-    "description": "Advanced Claude Code plugin with WFGY integration, MCP tools, and automated hooks",
-    "author": "AnEntrypoint",
-    "homepage": "https://github.com/AnEntrypoint/glootie-cc"
-  }
-}

package/cli.js

@@ -1,16 +0,0 @@
-#!/usr/bin/env node
-
-console.log('glootie-cc Claude Code Plugin v2.0.0');
-console.log('Advanced plugin with WFGY integration and MCP tools');
-console.log('');
-console.log('This plugin should be installed via Claude Code plugin system:');
-console.log('  /plugin install glootie-cc');
-console.log('');
-console.log('Features:');
-console.log('  - 6 automated hooks for complete workflow automation');
-console.log('  - 3 bundled MCP servers (glootie, vexify, playwright)');
-console.log('  - WFGY integration and architectural guidance');
-console.log('  - Complete tool permissions for enhanced productivity');
-console.log('');
-console.log('GitHub: https://github.com/AnEntrypoint/glootie-cc');
-console.log('NPM: https://www.npmjs.com/package/glootie-cc');

package/context/cleanup-guidelines.md

@@ -1,3 +0,0 @@
-Assign wfgy mutables to any issues that remain, to troubleshoot and fix them then scan the codebase to see if there are any other areas that should also be updated because of these changes, then use WFGY to determine if there's architectural changes that must now happen, and finally if the project is deployable, deploy it, if it's an npm project, publish it, and merge and sync the github intelligently, then clean up any files we've left behind in the codebase, that aren't part of the program's permanent structure, and use WFGY the selection of code if there's any complexity in the github merge to ensure we intelligently merge additions and removals whenever they represent an intentional advancement in the codebase.
-
-Mandatory: there must only be one comment in every file, at the top of the file, with a super compact description of the technical caveats, intended exports and imports, relationship to the rest of the program structure and internal function of it, we must ALWAYS update the spec of each file we edited, if we see a code file with no spec at the top, it must immediately be added, we must immediately remove any comments we find that's not that comment, no exceptions. Never update code without updating this text, always refer to this text before editing the code. If our codebase analysis exposes files with more or less than one comment, fix it immediately. Use MCP playwright never use regular playwright.

package/context/work-guidelines.md

@@ -1,24 +0,0 @@
-Do not create files that aren't a part of the permanent structure of the codebase unless asked for.
-Never add any mocks or simulations anywhere.
-Only write primary implementations and never make fallbacks of any kind.
-Always first check that we're not re-implementing an existing part before making new parts.
-
-Memorize everything you learn to make it work to CLAUDE.md. We want to memorize how things work (NO CHANGELOGS JUST TECH INFO) not what's been done (IN THE PROJECT CODEBASE) continuously. It's not a log or a work history, it's for all the technical caveats and notes. Always clean it up while editing it, remove any changelogs from it, it must be as concise as possible without losing any meaning, zero additional tokens. Otherwise if the information applies to all projects edit ~/.claude/CLAUDE.md so you don't make mistakes in the future, update it and remove things that no longer apply.
-
-# VERY IMPORTANT YOU MUST **ALWAYS DO THIS USING MCP** **(NO EXCEPTIONS)**:
-- If there's client side code create global to access client side parts in real time for debugging
-- Analyze and handle all issues before implementing in code, be as methodical and deal with all corner cases first, find ground truth by executing code to make sure you measure-twice-cut-once
-- Use the mop-and-bucket approach to check the rest of the codebase and make sure we don't make duplicate implementations, consolidate all duplicates, keep the codebase simple, well frameworked, convention-over-configuration, configuration-over-code at all times
-- Make all outstanding codebase changes immediately, don't stop when there's work left to do
-- Before making changes to client side code, do code executions in playwright mcp to find out if the changes will work
-- Test and change as many times as needed to finish all the work requested, never under any circumstances finish or summarize when there's work left to do. Check what mcp tools are available and use what's useful
-
-Be forward thinking about architectural sanity, if something should be done, to improve the architecture, generalize or DRY the code, do it immediately before continuing. Our code style must be at all times concise, DRY, generalized and forward thinking structurally.
-
-If a file is more than 200 lines split it immediately before continuing.
-When troubleshooting any issue look back a few versions in the git history to see if it's a regression, use the history to guide to back to a working version if possible, otherwise choose a solution.
-
-Always use a persistent background shell to do your tests.
-
-When using playwright, always close everything before you start your test, this will sort out the cache.
-Use vexify, glootie, and playwright as much as possible when available. Test server side ideas in glootie execute and client side ideas in playwright code execution before changing code, use them to debug in real time by executing, use vexify for code lookups when you don't know the exact syntax or for searching for multiple things that are similar.