[FEATURE] [FEATURE] Add hint support to Claude Code CLI
Resolved 💬 4 comments Opened Mar 11, 2026 by jkgeekJack Closed Apr 8, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
When working on complex projects with Claude Code CLI, developers often need contextual help or hints during their workflow. Currently, there is no built-in hint system to provide guidance on available commands, best practices, or contextual suggestions within the CLI interface.
Proposed Solution
Add a --hint flag to the Claude Code CLI that enables an interactive hint system. The system should:
- Display contextual hints based on the current project structure and file types being edited
- - Provide suggestions for commonly used commands relevant to the detected tech stack
- - - Offer best practices and optimization tips
- - - - Be toggleable via CLI flag
--hintor--help-modefor enhanced user guidance - - - - - Include a hint notification system that can be enabled/disabled in configuration
Alternative Solutions
- External documentation references: Could link to external docs for each tech stack
- - AI-powered suggestions: Use Claude's capabilities to generate contextual hints on the fly based on current code state
- - - Tutorial mode: A beginner-friendly mode that walks users through common workflows
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
A developer working on a TypeScript/React project runs:
claude --hint
The CLI detects the tech stack and provides hints like:
- "You're working with React. Consider using /analyze-component to understand component structure"
- - "TypeScript detected. Use /type-check to validate types"
- - - "Package.json found. Available npm scripts are: dev, build, test"
This helps new users and experienced developers discover Claude Code's capabilities more efficiently.
Additional Context
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗