A Chrome extension that enhances Claude's thinking process, making it more human-like and transparent.
Important Notice: The original Chrome extension (
chrome_v0
) has been deprecated. This is the new rewritten version (chrome
) with improved architecture and modern tech stack. If you're using the old version, please update to this new version for better performance and continued support.
-
Download the Extension
- Go to Latest Releases
- Download the latest version (e.g.,
thinking-claude-v1.0.2.zip
) - Extract the ZIP file
-
Install in Chrome
- Open Chrome and go to
chrome://extensions/
- Enable "Developer mode" in the top right
- Click "Load unpacked"
- Select the
dist
folder in the extracted folder
- Open Chrome and go to
-
Start Using
- Visit Claude.ai
- Start a new conversation or refresh an existing one
- The extension will automatically enhance Claude's thinking process
-
Quick Setup
# Clone the repository git clone https://github.com/richards199999/Thinking-Claude.git cd Thinking-Claude/extensions/chrome # Install dependencies bun install # Build the extension bun run build
-
Load in Chrome
- Open Chrome and go to
chrome://extensions/
- Enable "Developer mode" in the top right
- Click "Load unpacked"
- Select the
dist
folder (created after building)
- Open Chrome and go to
-
Development Mode
# Start development server with hot reload bun run start # Watch for changes bun run watch
-
Language & Type Safety
- TypeScript - Strongly typed programming language
- ESLint - Code linting and standards
- Prettier - Code formatting
-
Frontend
- React - UI library
- Tailwind CSS - Utility-first CSS framework
- shadcn/ui - Best UI components
- Chrome Extension API - Browser extension development
-
Build & Bundle
-
Testing & Quality
- Vitest - Unit testing framework
- Husky - Git hooks
- lint-staged - Staged files linter
-
Development Environment
- Node.js - JavaScript runtime
- Chrome DevTools - Browser debugging
Required tools:
- Bun - A fast all-in-one JavaScript runtime & toolkit
- Node.js (v18 or higher) - JavaScript runtime environment
- Git - For version control
- Google Chrome - The browser we're building for
This extension uses:
- TypeScript - Type-safe JavaScript
- React - UI framework
- Tailwind CSS - Utility-first CSS framework
- Webpack - Module bundler
-
Download Node.js from nodejs.org
-
Choose the LTS (Long Term Support) version
-
Run the installer
-
Verify installation:
node --version npm --version
Bun is required to run this project. Here's how to install it:
Windows Users:
-
First, install Windows Subsystem for Linux (WSL):
# Open PowerShell as Administrator and run: wsl --install
After installation, restart your computer.
-
Install Bun through WSL:
# Open WSL terminal and run: curl -fsSL https://bun.sh/install | bash
macOS or Linux Users:
# Open terminal and run:
curl -fsSL https://bun.sh/install | bash
To verify installation, run:
bun --version
-
Get the code:
# Clone this repository to your computer git clone https://github.com/richards199999/Thinking-Claude.git # Go to the extension directory cd extensions/chrome # Install project dependencies bun install
Here are the main commands you'll use during development:
# Build the extension for production
bun run build
# Start development mode with auto-reload
bun run start
# Watch for file changes
bun run watch
# Run tests
bun run test
# Fix code style and formatting
bun run fix
- Open Chrome and type
chrome://extensions/
in the address bar - Turn on "Developer mode" using the switch in the top right corner
- Click "Load unpacked" and select the
dist (visible after running bun run build)
folder from this project
chrome/
├── src/ # Your source code goes here
├── public/ # Built extension (created after running build)
│ ├── manifest.json # Extension configuration
│ ├── content.js # Main extension script
│ └── icons/ # Extension icons
├── package.json # Project configuration and scripts
└── CHANGELOG.md # Version history and changes
We use several tools to maintain code quality:
- Husky: Automatically checks your code before commits
- ESLint: Finds and fixes JavaScript problems
- Prettier: Formats your code consistently
The project uses automated version bumping through CI:
-
Automatic Version Bumping: When code is merged to main, the CI will:
- Auto-increment the patch version (e.g., 1.0.0 -> 1.0.1)
- Create a new release with the bumped version
- Skip version bump for major versions (x.0.0)
-
Manual Version Control:
- Developers can manually set both versions in
package.json
andmanifest.json
- Major version changes (x.0.0) must be set manually
- Manual versions will be respected by CI
- Developers can manually set both versions in
Note: If you need to manually set a version, update both
package.json
andmanifest.json
before merging to main.
Our GitHub Actions setup automatically:
- Builds the extension
- Updates version numbers
- Creates new releases
- Check the CHANGELOG.md for recent updates
- Visit our GitHub Issues for known problems or to report new ones
- Feel free to ask questions in our GitHub Discussions