이맥스(Emacs)용 AI 페어 프로그래머 공개

CodeTutor CodeTutor is an Emacs package for learning while you code. It opens a right-side tutor panel, watches file saves, gathers project context, and asks a local AI assistant to respond like a senior/staff engineer pair-programming tutor. The important boundary: CodeTutor helps you write the code. It does not write into your project files for you. It can: review what changed after a save explain the concept behind feedback show compact illustrative code samples recommend the best next step answer minibuffer prompts answer follow-up questions using recent conversation turns keep durable architecture notes in .codetutor/ARCHITECTURE.md It should not: edit your source files produce patches produce full-file replacements hand you a complete ready-to-paste implementation for the exact task Status This is an early local package. It is designed for stock Emacs and Doom Emacs, with local codex and pi backends. Requirements Emacs 28.1 or newer Optional but recommended: Emacs 29+ with built-in tree-sitter support One local backend: codex pi CodeTutor degrades gracefully when tree-sitter is not available by using imenu where possible. Install Stock Emacs ( add-to-list 'load-path " /Users/jacobwindle/Projects/codetutor " ) ( require 'codetutor ) ( setq codetutor-backend 'auto ) (codetutor-mode 1 ) Doom Emacs Add the local package: ; ; ~/.config/doom/packages.el (package! codetutor :recipe ( :local-repo " ~/Projects/codetutor " )) Configure it: ; ; ~/.config/doom/config.el (use-package! codetutor :commands (codetutor-open codetutor-what-next codetutor-ask codetutor-follow-up codetutor-refresh-architecture-memory) :init ( setq codetutor-backend 'auto codetutor-open-on-enable nil codetutor-start-session-on-open t codetutor-review-on-save t ) :config (codetutor-mode 1 )) Then run: ~ /.config/emacs/bin/doom sync Restart Emacs after syncing. Commands Command Keybinding What It Does codetutor-mode none Enables/disables global CodeTutor hooks. codetutor-open C-c t o Opens the side panel and starts a project assessment. codetutor-what-next C-c t n Asks for the single best next step. codetutor-ask C-c t a Prompts from the minibuffer with current file/project context. codetutor-follow-up C-c t f Asks a follow-up about the previous answer using recent turns. codetutor-refresh-architecture-memory C-c t m Asks the tutor to refresh durable architecture notes. How It Works CodeTutor has four core loops: startup assessment, save review, manual prompt, and follow-up. Startup Assessment When you run M-x codetutor-open , CodeTutor: Detects the project root. Opens a right-side panel. Gathers project context. Starts a read-only backend request. Replaces the panel with Status: thinking . Replaces that status with the final tutor answer. The startup answer should tell you where to begin, what to learn first, and what engineering judgment matters before writing code. Save Review When codetutor-mode and codetutor-review-on-save are enabled, CodeTutor hooks into Emacs saves: before-save-hook reads the current on-disk file. The save happens normally. after-save-hook compares the previous on-disk contents with the saved buffer text. CodeTutor builds a unified diff. CodeTutor sends the diff plus project context to the backend. The side panel shows Status: thinking . The side panel is replaced with the final teaching response. Save reviews are proportional to the diff. The tutor should focus on concept, risk, architecture, tests, and one next move. Manual Prompt M-x codetutor-ask prompts from the minibuffer. It includes: the current file tree-sitter or imenu outline project context architecture memory project file index recent conversation turns The backend may inspect/search other project files through read-only tools when supported. Follow-Up M-x codetutor-follow-up asks a question about the previous answer. It does not display the prompt in the side panel. Follow-ups include recent private conversation turns, so you can ask things like: Can you show me a smaller example? or: What would the test shape look like? The follow-up still includes current file and project context, so the tutor can connect the prior answer to where you are now. What Next M-x codetutor-what-next asks the tutor to inspect available context and recommend one best next step. This is useful when you are between implementation slices and want a senior engineer's judgment on what to do next. Architecture Memory The tutor is asked to include durable architecture observations in a fenced block: ``` codetutor-memory - Boundary: The editor integration owns context gathering; the backend owns tutoring. ``` CodeTutor extracts those lines and appends new ones to: .codetutor/ARCHITECTURE.md That memory file is the only project file CodeTutor writes automatically. Context Sources CodeTutor builds a prompt from several local sources. Source When Included Purpose PROJECT.md , Project.md , project.md Every request Product/project direction. spec/ Every request Specs, requirements, design notes. .codetutor/ARCHITECTURE.md Every request when present Durable project memory. Current file text Every request What you are actively editing. Tree-sitter summary Every request when available Syntax-level outline of the current buffer. Imenu summary Fallback when tree-sitter is unavailable Lightweight outline. Project file index Every request Helps the tutor decide what else to inspect. Diff since last save Save reviews The actual change being reviewed. Other open project buffers Save reviews Nearby work you already have open. Recent conversation turns Follow-ups and later prompts Continuity across questions. Open-buffer context is capped so a large Emacs session does not overwhelm the backend. Backends Codex The Codex backend uses codex exec non-interactively. It is configured with: read-only sandbox approval policy never ephemeral session no terminal color optional web search --output-last-message so the panel displays only the final answer The command is built roughly like this: codex \ --sandbox read-only \ --ask-for-approval never \ --search \ exec \ -C " $PROJECT_ROOT " \ --skip-git-repo-check \ --color never \ --ephemeral \ --output-last-message " $TEMP_FILE " \ - pi The pi backend uses non-interactive print mode with only read-only tools: pi --print --tools read,grep,find,ls It can inspect files, but should not write or edit them. Output Model The side panel is intentionally not a chat transcript. For every request, CodeTutor: Clears the panel. Shows Status: thinking . Runs the backend. Extracts the final answer. Clears the panel again. Shows only the answer. The panel should not show: your prompt text generated prompt metadata full project context file contents sent as context backend progress output CLI transcripts The tutor is asked to wrap visible answers in: < codetutor-answer > ... </ codetutor-answer > CodeTutor extracts that block when present and strips architecture memory blocks from the visible panel output. Teaching Posture The built-in prompt tells the tutor to: teach underlying concepts guide the user toward the solution ask useful questions give one concrete next move include compact code samples when they clarify the idea explain how to adapt examples instead of handing over final code avoid patches, full-file replacements, and complete ready-to-paste implementations Good CodeTutor output should feel like a senior engineer pairing with you, not like an autocomplete engine. Customization Common settings: ( setq codetutor-backend 'auto ) ; ; 'auto, 'codex, or 'pi ( setq codetutor-model nil ) ; ; nil uses backend default ( setq codetutor-window-width 84 ) ( setq codetutor-review-on-save t ) ( setq codetutor-enable-web-search t ) ( setq codetutor-include-open-buffers-on-save t ) Context limits: ( setq codetutor-max-project-context-bytes 80000 ) ( setq codetutor-max-current-file-bytes 50000 ) ( setq codetutor-max-diff-bytes 60000 ) ( setq codetutor-max-open-buffers 12 ) ( setq codetutor-max-open-buffer-bytes 20000 ) ( se