Claude Editor Hook banner
alosec alosec

Claude Editor Hook

Development community

Description

Command palette for Claude Code via Ctrl-G hook. Spawn parallel Claude instances, stream logs, run tools - anything executable with clean return paths.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

claude-editor-hook

A command palette for Claude Code that intercepts `Ctrl-G` to launch editors, tools, and specialized agents.

**Note:** Also available as `g-menu` for convenience.

Current Status

✅ **Working and Simple** - FZF command palette with persistent sessions.

**✅ Working Now:**

  • FZF command palette with 8+ options
  • Edit with Emacs/Vi/Nano (returns to Claude Code when done)
  • Open Terminal (full shell with $PROMPT env var set to temp file path)
  • Recent Files - Query JSONL logs for last 25 files Claude touched (with intelligent caching)
  • Subagent Context Package - Spawn Claude instances with rich parent context (conversation + tools + files)
  • Interactive + non-interactive prompt enhancement
  • Universal command palette accessible from any terminal via menu or m commands

**📋 Future Exploration (Not Actively Planned):**

  • Menu extensions based on real usage needs (git ops, log streaming, test runners)
  • Enhanced history viewer - "Better Ctrl-O" parsing ~/.claude/projects
  • Context file system for multi-file opening (may revisit if use cases emerge)
  • Multi-pane tmux layouts with logs
  • MCP tool for Claude to write context files
  • Multi-agent orchestration (interesting theory, likely overkill)

What Is This?

When you press `Ctrl-G` in Claude Code to edit a prompt, it launches whatever is in your `$EDITOR` environment variable. This project intercepts that hook to provide a command palette that can launch:

  • Interactive menus with FZF for choosing editors and tools
  • Prompt enhancement agents that investigate your codebase and rewrite prompts
  • Any editor (emacs, vi, nano) or viewer (batcat)
  • Anything scriptable - the menu accepts any command or script
  • 📋 Multiple files at specific line numbers (requires context file system - planned)
  • 📋 Tmux layouts with editor, logs, and test panes (planned)
  • 📋 Log streams from servers or browsers (planned)

How It Works

┌───────────