Skip to content

autocode plugin not working in Claude Code - EnterPlanMode takes priority #1

@123456789123-123

Description

@123456789123-123

autocode plugin not working in Claude Code - EnterPlanMode takes priority

Environment

  • Claude Code version: Latest (2026-03-17)
  • Model: Claude Opus 4.6
  • OS: Windows 11
  • Plugin version: autocode 1.0.0

Issue Description

The autocode plugin's session-start.md hook is loaded, but Claude Code's built-in EnterPlanMode tool intercepts "build X" requests before the plugin can take effect.

Expected Behavior

When I say "I want to build a blog website", autocode should:

  1. Ask 1-2 simple questions in natural language
  2. Then execute: Spec → Plan → Code → Test → Review → Commit

Actual Behavior

Claude Code shows a structured multi-choice questionnaire with:

  • Technical stack selection (Next.js/Hugo/WordPress/Custom)
  • Content management options
  • Feature requirements
  • Deployment options

This is Claude Code's native EnterPlanMode behavior, not autocode's simplified workflow.

Steps to Reproduce

  1. Install autocode plugin: claude plugin install autocode@claude-plugins-official
  2. Enable plugin: claude plugin enable autocode@claude-plugins-official
  3. Start new session
  4. Say: "I want to build a blog website"
  5. Result: CC's structured questionnaire appears instead of autocode's natural dialogue

Root Cause Analysis

  • autocode uses session-start.md hook (prompt-based)
  • Claude Code's EnterPlanMode is a tool call (higher priority than prompts)
  • Tool calls execute before prompt hooks, so autocode's instructions are ignored

Verification

Confirmed that:

  • Plugin is enabled: claude plugin list shows status ✔ enabled
  • Hook file exists: ~/.claude/hooks/autocode-session-start.md is present
  • Hook content is correct: Contains "MANDATORY: Never Write Code Without Clarifying First"

But the hook's instructions are not followed when EnterPlanMode triggers.

Suggested Fix

Consider one of:

  1. Make autocode a tool (not just a prompt hook) so it can intercept before EnterPlanMode
  2. Add a plugin priority system where plugins can override built-in tools
  3. Add a setting to disable EnterPlanMode when autocode is enabled
  4. Document that autocode only works for non-build tasks (fix/refactor/review)

Additional Context

The plugin works great for token compression and workflow automation in theory, but the EnterPlanMode interception makes it unusable for "build X" tasks, which are the primary use case mentioned in the README.

Would appreciate guidance on whether this is:

  • A configuration issue on my end
  • A known limitation
  • A bug that needs fixing

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions