Merge branch 'main' into add-oauth-pkce-login

Author: aseembits93

.claude-plugin/marketplace.json

@@ -6,13 +6,13 @@
     "email": "support@codeflash.ai"
   },
   "metadata": {
-    "description": "Codeflash plugin for Claude Code — optimize Python code for performance",
+    "description": "Codeflash plugin for Claude Code — optimize code for performance",
     "version": "0.1.10"
   },
   "plugins": [
     {
       "name": "codeflash",
-      "description": "Run codeflash as a background agent to optimize Python code for performance",
+      "description": "Run codeflash as a background agent to optimize code for performance",
       "version": "0.1.10",
       "author": {
         "name": "Codeflash",
@@ -22,7 +22,7 @@
       "homepage": "https://codeflash.ai",
       "repository": "https://github.com/codeflash-ai/codeflash-cc-plugin",
       "license": "MIT",
-      "keywords": ["python", "optimization", "performance", "codeflash"],
+      "keywords": ["python", "javascript", "typescript", "optimization", "performance", "codeflash", "speedup", "runtime"],
       "category": "development"
     }
   ]

.claude-plugin/plugin.json

@@ -1,13 +1,13 @@
 {
   "name": "codeflash",
-  "description": "Run codeflash as a background agent to optimize Python code for performance",
-  "version": "0.1.11",
+  "description": "Run codeflash as a background agent to optimize code for performance",
+  "version": "0.1.10",
   "author": {
     "name": "Codeflash",
     "url": "https://codeflash.ai"
   },
   "repository": "https://github.com/codeflash-ai/codeflash-cc-plugin",
   "homepage": "https://codeflash.ai",
   "license": "MIT",
-  "keywords": ["python", "optimization", "performance", "codeflash"]
+  "keywords": ["python", "javascript", "typescript", "optimization", "performance", "codeflash", "speedup", "runtime"]
 }

.github/workflows/test.yml

@@ -0,0 +1,35 @@
+name: Tests
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+
+    env:
+      FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "22"
+
+      - name: Install BATS
+        run: npm install -g bats
+
+      - name: Verify dependencies
+        run: |
+          bats --version
+          jq --version
+          git --version
+
+      - name: Run tests
+        run: bats tests/

README.md

@@ -1,12 +1,12 @@
 # Codeflash Claude Code Plugin
 
-A minimal Claude Code plugin that runs [Codeflash](https://codeflash.ai) as a background agent to optimize Python code for performance.
+A minimal Claude Code plugin that runs [Codeflash](https://codeflash.ai) as a background agent to optimize Python, JavaScript, and TypeScript code for performance.
 
 ## Prerequisites
 
 - Claude Code v2.1.38 or later
-- [codeflash](https://pypi.org/project/codeflash/) installed in your project
-- Project initialized with `codeflash init` (creates `[tool.codeflash]` in `pyproject.toml`)
+- **Python projects**: [codeflash](https://pypi.org/project/codeflash/) installed in a virtual environment, configured via `[tool.codeflash]` in `pyproject.toml`
+- **JS/TS projects**: [codeflash](https://www.npmjs.com/package/codeflash) installed as a dev dependency (`npm install --save-dev codeflash`), configured via a `"codeflash"` key in `package.json`
 
 ## Installation
 
@@ -69,7 +69,7 @@ Run `/plugin` to open the plugin manager and confirm codeflash appears under the
 
 ### Auto-suggest after commits
 
-When you make a git commit that includes Python file changes, the plugin suggests running `/optimize` on those files.
+When you make a git commit that includes Python, JavaScript, or TypeScript file changes, the plugin suggests running `/optimize` on those files.
 
 ## Plugin Structure
 
@@ -84,7 +84,7 @@ codeflash-cc-plugin/
 │   └── hooks.json               # Stop hook for commit detection
 ├── scripts/
 │   ├── find-venv.sh             # Shared helper: find and activate a Python venv
-│   └── suggest-optimize.sh      # Detects Python changes, suggests /optimize
+│   └── suggest-optimize.sh      # Detects Python/JS/TS changes, suggests /optimize
 ├── skills/
 │   └── optimize/
 │       └── SKILL.md             # /optimize slash command
@@ -96,7 +96,7 @@ codeflash-cc-plugin/
 The plugin is a thin wrapper around the `codeflash` CLI:
 
 1. `/optimize` spawns a background optimizer agent
-2. Verifies codeflash is installed (via `pip install codeflash`) and configured
+2. Verifies codeflash is installed (`pip install codeflash` for Python, `npm install --save-dev codeflash` for JS/TS) and configured
 3. Runs the `codeflash` CLI with the appropriate flags
 4. Reports results (optimizations found, PRs created)
 

agents/optimizer.md

@@ -1,7 +1,7 @@
 ---
 name: optimizer
 description: |
-  Optimizes Python code for performance using Codeflash. Use when asked to optimize, speed up, or improve performance of Python code. Also triggered automatically after commits that change Python files.
+  Optimizes Python and JavaScript/TypeScript code for performance using Codeflash. Use when asked to optimize, speed up, or improve performance of Python, JavaScript, or TypeScript code. Also triggered automatically after commits that change Python/JS/TS files.
 
   <example>
   Context: User explicitly asks to optimize code
@@ -21,6 +21,24 @@ description: |
   </commentary>
   </example>
 
+  <example>
+  Context: User explicitly asks to optimize JS/TS code
+  user: "Optimize src/utils.ts for performance"
+  assistant: "I'll use the optimizer agent to run codeflash on that file."
+  <commentary>
+  Direct optimization request for a TypeScript file — trigger the optimizer agent with the file path.
+  </commentary>
+  </example>
+
+  <example>
+  Context: User wants to speed up a JS/TS function
+  user: "Can you make the parseData function in src/parser.js faster?"
+  assistant: "I'll use the optimizer agent to optimize that function with codeflash."
+  <commentary>
+  Performance improvement request targeting a specific JS function — trigger with file and function name.
+  </commentary>
+  </example>
+
   <example>
   Context: Hook detected Python files changed in a commit
   user: "Python files were changed in the latest commit. Use the Task tool to optimize..."
@@ -36,7 +54,7 @@ color: cyan
 tools: Read, Glob, Grep, Bash, Write, Edit
 ---
 
-You are a thin-wrapper agent that runs the codeflash CLI to optimize Python code.
+You are a thin-wrapper agent that runs the codeflash CLI to optimize Python and JavaScript/TypeScript code.
 
 ## Workflow
 
@@ -139,13 +157,24 @@ export CODEFLASH_API_KEY="cf-your-key-here"
 
 ### 1. Locate Project Configuration
 
-Walk upward from the current working directory to the git repository root (`git rev-parse --show-toplevel`) looking for `pyproject.toml`. Use the **first** (closest to CWD) file found. Record:
-- **Project directory**: the directory containing the discovered `pyproject.toml`
-- **Configured**: whether the file contains a `[tool.codeflash]` section
+Walk upward from the current working directory to the git repository root (`git rev-parse --show-toplevel`) looking for a project configuration file. Check for both `pyproject.toml` (Python) and `package.json` (JavaScript/TypeScript) at each directory level. Use the **first** (closest to CWD) file found.
+
+**Determine the project type:**
+- If `pyproject.toml` is found first → **Python project**. Record:
+  - **Project directory**: the directory containing `pyproject.toml`
+  - **Configured**: whether the file contains a `[tool.codeflash]` section
+- If `package.json` is found first → **JS/TS project**. Record:
+  - **Project directory**: the directory containing `package.json`
+  - **Configured**: whether the JSON has a `"codeflash"` key at the root level
+- If both exist in the same directory, determine the project type from the file being optimized (`.py` → Python, `.js`/`.ts`/`.jsx`/`.tsx` → JS/TS). If ambiguous, prefer `pyproject.toml`.
+
+If neither file is found, use the git repository root as the project directory.
 
-If no `pyproject.toml` is found, use the git repository root as the project directory.
+### 2. Verify Environment and Installation
 
-### 2. Verify Virtual Environment and Installation
+The verification process depends on the project type determined in Step 1.
+
+#### 2a. Python projects
 
 First, check that a Python virtual environment is active by running `echo $VIRTUAL_ENV`.
 
@@ -182,8 +211,30 @@ pip install codeflash
 
 If the user agrees, run the installation command in the project directory. If installation succeeds, proceed to Step 3. If the user declines or installation fails, stop.
 
+#### 2b. JS/TS projects
+
+Check whether the `codeflash` npm package is installed in the project by running:
+
+```bash
+npx codeflash --version
+```
+
+If it succeeds, proceed to Step 3.
+
+If it fails (command not found or package not available), codeflash is not installed. Ask the user whether they'd like to install it now:
+
+```bash
+npm install --save-dev codeflash
+```
+
+If the user agrees, run the installation command in the project directory (from Step 1). If installation succeeds, proceed to Step 3. If the user declines or installation fails, stop.
+
 ### 3. Verify Setup
 
+The setup process depends on the project type determined in Step 1.
+
+#### 3a. Python projects (`pyproject.toml`)
+
 Use the `pyproject.toml` discovered in Step 1:
 
 - **If `[tool.codeflash]` is already present** → check the formatter (see sub-step 5 below), then proceed to Step 4.
@@ -213,23 +264,60 @@ formatter-cmds = ["disabled"]
 
 5. **Verify formatter**: Read the `formatter-cmds` value from the `[tool.codeflash]` section. If it is set to `["disabled"]` or is empty, skip this check. Otherwise, for each command in the `formatter-cmds` list, extract the base command name (the first word, e.g. `black` from `"black --line-length 88 {file}"`) and run `which <command>` to check if it is installed. If any formatter command is **not found**, inform the user which formatter(s) are missing and ask if they'd like to install them (e.g. `pip install <formatter>`). If the user agrees, run the install. If the user declines, warn that codeflash may fail to format optimized code and proceed to Step 4 anyway.
 
+#### 3b. JS/TS projects (`package.json`)
+
+Use the `package.json` discovered in Step 1:
+
+- **If a `"codeflash"` key already exists at the root of the JSON** → check the formatter (see sub-step 5 below), then proceed to Step 4.
+- **If `package.json` exists but has no `"codeflash"` key** → add the config to that file.
+- **If no `package.json` was found** → create one at the git repository root with `npm init -y`, then add the config.
+
+When configuration is missing, interactively set it up:
+
+1. **Ask the user two questions** (use AskUserQuestion or prompt directly):
+   - **Module root**: "What is the relative path to the root of your JavaScript/TypeScript module?" (e.g. `.` for the root directory, `src`, `src/lib`)
+   - **Tests folder**: "What is the relative path to your tests folder?" (e.g. `tests`, `test`, `__tests__`, `src/__tests__`)
+
+2. **Validate directories**: Check whether the tests folder the user provided exists. If it does **not** exist, create it with `mkdir -p`.
+
+3. **Write the configuration**: Read the existing `package.json`, parse it as JSON, add a `"codeflash"` key at the root level, and write the file back. Use exactly this structure, substituting the user's answers:
+
+```json
+{
+  "codeflash": {
+    "moduleRoot": "<user's module root>",
+    "testsRoot": "<user's tests folder>",
+    "formatterCmds": ["disabled"],
+    "ignorePaths": ["dist", "**/node_modules", "**/__tests__"]
+  }
+}
+```
+
+**Important**: When writing to `package.json`, you must preserve all existing content. Read the file, parse the JSON, add/update only the `"codeflash"` key, then write the full JSON back with 2-space indentation.
+
+4. Confirm to the user that the configuration has been written.
+
+5. **Verify formatter**: Read the `formatterCmds` value from the `"codeflash"` config. If it is set to `["disabled"]` or is empty, skip this check. Otherwise, for each command in the `formatterCmds` array, extract the base command name (the first word, ignoring `npx` — e.g. `prettier` from `"npx prettier --write {file}"`). If the command is invoked via `npx`, check that the package is available with `npx <command> --version`. If invoked directly, run `which <command>`. If any formatter command is **not found**, inform the user which formatter(s) are missing and ask if they'd like to install them (e.g. `npm install --save-dev <formatter>`). If the user agrees, run the install. If the user declines, warn that codeflash may fail to format optimized code and proceed to Step 4 anyway.
+
 Then proceed to Step 4.
 
 ### 4. Parse Task Prompt
 
 Extract from the prompt you receive:
-- **file path**: Python file to optimize (e.g. `src/utils.py`)
+- **file path**: file to optimize (e.g. `src/utils.py`, `src/utils.ts`)
 - **function name**: Specific function to target (optional)
 - Any other flags: pass through to codeflash
 
 If no file and no `--all` flag, run codeflash without `--file` or `--all` to let it detect changed files automatically. Only use `--all` when explicitly requested.
 
 ### 5. Run Codeflash
 
-If the project directory from Step 1 differs from the current working directory, **`cd` to the project directory first** so that relative paths in the config resolve correctly.
+**Always `cd` to the project directory** (from Step 1) before running codeflash, so that relative paths in the config resolve correctly.
 
 Execute the appropriate command **in the background** (`run_in_background: true`) with a **10-minute timeout** (`timeout: 600000`):
 
+#### Python projects
+
 ```bash
 # Default: let codeflash detect changed files
 source $VIRTUAL_ENV/bin/activate && cd <project_dir> && codeflash --subagent [flags]
@@ -243,6 +331,23 @@ source $VIRTUAL_ENV/bin/activate && cd <project_dir> && codeflash --subagent --a
 
 If CWD is already the project directory, omit the `cd`. Always include the `source $VIRTUAL_ENV/bin/activate` prefix to ensure the virtual environment is active in the shell that runs codeflash.
 
+#### JS/TS projects
+
+**Important**: Codeflash must always be run from the project root (the directory containing `package.json`).
+
+```bash
+# Default: let codeflash detect changed files
+cd <project_dir> && npx codeflash --subagent [flags]
+
+# Specific file
+cd <project_dir> && npx codeflash --subagent --file <path> [--function <name>] [flags]
+
+# All files (only when explicitly requested with --all)
+cd <project_dir> && npx codeflash --subagent --all [flags]
+```
+
+If CWD is already the project directory, omit the `cd`. Use `npx codeflash` (no virtual environment activation needed).
+
 **IMPORTANT**: Always use `run_in_background: true` when calling the Bash tool to execute codeflash. This allows optimization to run in the background while Claude continues other work. Tell the user "Codeflash is optimizing in the background, you'll be notified when it completes" and do not wait for the result.
 
 ### 6. Report Initial Status

scripts/find-venv.sh

@@ -5,6 +5,9 @@
 # Effect:   If no venv is active, searches common locations relative to
 #           CHECK_DIR and REPO_ROOT, and activates the first one found.
 #           After return, VIRTUAL_ENV will be set if a venv was found.
+#
+# Note: This helper is only used for Python projects. JS/TS projects
+# do not require a virtual environment — they use npx/npm instead.
 
 if [ -z "${VIRTUAL_ENV:-}" ]; then
   for candidate in "$CHECK_DIR/.venv" "$CHECK_DIR/venv" "$REPO_ROOT/.venv" "$REPO_ROOT/venv"; do