extensions/chrome/README.md
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
thinking-claude-v1.0.2.zip)Install in Chrome
chrome://extensions/dist folder in the extracted folderStart Using
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
chrome://extensions/dist folder (created after building)Development Mode
# Start development server with hot reload
bun run start
# Watch for changes
bun run watch
Language & Type Safety
Frontend
Build & Bundle
Testing & Quality
Development Environment
Required tools:
This extension uses:
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
chrome://extensions/ in the address bardist (visible after running bun run build) folder from this projectchrome/
āāā 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:
The project uses automated version bumping through CI:
Automatic Version Bumping: When code is merged to main, the CI will:
Manual Version Control:
package.json and manifest.jsonNote: If you need to manually set a version, update both
package.jsonandmanifest.jsonbefore merging to main.
Our GitHub Actions setup automatically: