vivekmind 0.15.6 → 1.0.0

package/LICENSE

@@ -187,8 +187,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-  Copyright 2025 Google LLC
-  Copyright 2025 Qwen
+  Copyright 2026 VivekMind (https://code.vivekmind.com)
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

package/README.md

@@ -4,6 +4,8 @@
 
 <h1 align="center">VivekMind CLI</h1>
 
+<h3 align="center"><a href="https://code.vivekmind.com">code.vivekmind.com</a></h3>
+
 <p align="center">
   <strong>Open-source terminal AI coding agent with full AWS Bedrock support</strong>
 </p>
@@ -16,7 +18,7 @@
 
 ---
 
-VivekMind is a fork of [Qwen Code](https://github.com/QwenLM/qwen-code) (by Google & Alibaba Cloud), tailored for developers who want a powerful, provider-flexible AI coding assistant that lives entirely inside the terminal. It ships with native AWS Bedrock integration, 20+ AI provider support, and a rich extensible architecture built around tools, skills, agents, and MCP servers.
+VivekMind CLI is a powerful, provider-flexible AI coding assistant that lives entirely inside your terminal. It features native AWS Bedrock integration, multi-model capability (20+ providers supported), and a rich extensible architecture built around tools, skills, subagents, and Model Context Protocol (MCP) servers.
 
 Install it, point it at any model, and start coding — all from your shell.
 
@@ -48,7 +50,7 @@ VivekMind supports a wide range of AI providers out of the box. Set the correspo
 
 | Provider | Auth Type | Example Models |
 |----------|-----------|----------------|
-| **AWS Bedrock** | `bedrock` | Claude Opus 4.7, Amazon Nova Pro, Llama 4 Maverick |
+| **AWS Bedrock** | `bedrock` | Claude (3/3.5/4.7), Amazon Nova (Pro/Lite/Micro), Llama (3/3.1/3.3/4), VivekMind CLIr, GLM, Mistral, Cohere |
 | **Anthropic** | `anthropic` | Claude Opus 4.7, Sonnet 4.6, Haiku 4.5 |
 | **Google Gemini** | `gemini` | Gemini 3 Pro, 2.5 Pro, 2.5 Flash |
 | **OpenAI** | `openai` | GPT-5.2, 5.4 Mini, 4.1, o3, o4-mini |
@@ -56,7 +58,7 @@ VivekMind supports a wide range of AI providers out of the box. Set the correspo
 | **Anthropic (Vertex AI)** | `anthropic-vertex-ai` | Claude Opus 4.7 (Vertex) |
 | **DeepSeek** | `deepseek` | DeepSeek Chat V3, DeepSeek Reasoner R1 |
 | **Mistral AI** | `mistral` | Mistral Large, Codestral, Pixtral Large |
-| **Alibaba DashScope** | `dashscope` | Qwen3 Coder Plus, Qwen VL Max |
+| **Alibaba DashScope** | `dashscope` | VivekMind3 Coder Plus, VivekMind VL Max |
 | **xAI (Grok)** | `xai` | Grok 4 |
 | **OpenRouter** | `openrouter` | Claude Opus 4.7 (OpenRouter) |
 | **Groq** | `groq` | Llama 3.3 70B (Groq) |
@@ -73,7 +75,7 @@ VivekMind supports a wide range of AI providers out of the box. Set the correspo
 
 ### AWS Bedrock Setup
 
-AWS Bedrock works with your existing AWS credentials. No additional API key is needed:
+AWS Bedrock works with your existing AWS credentials. No additional API key is needed. VivekMind supports the full list of AWS Bedrock models, including **Anthropic Claude** (3/3.5/4.7), **Amazon Nova** (Pro/Lite/Micro), **Meta Llama** (3/3.3/4), **VivekMind CLIr** models, **GLMs**, **Mistral**, and **Cohere Command**:
 
 ```bash
 # Ensure AWS credentials are set
@@ -85,7 +87,7 @@ export AWS_SECRET_ACCESS_KEY=your-secret
 vivekmind
 ```
 
-Bedrock models are auto-discovered via `ListFoundationModels` API. Configure specific models in `settings.json`:
+Bedrock models are auto-discovered via the `ListFoundationModels` API. You can configure and name specific models in `settings.json`:
 
 ```json
 {
@@ -371,16 +373,6 @@ npm run lint
 npm run preflight
 ```
 
----
-
-## Attribution
-
-VivekMind is a fork of [Qwen Code](https://github.com/QwenLM/qwen-code), originally developed by Google LLC and Alibaba Cloud.
-
-Qwen Code is copyright (C) 2025 Google LLC and Alibaba Cloud, and is used under the Apache License, Version 2.0.
-
-VivekMind modifications are copyright (C) 2026 [VivekMind](https://vivekmind.com).
-
 ## License
 
 This project is licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

package/bundled/qc-helper/SKILL.md

@@ -41,7 +41,7 @@ Use this index to locate the right document for the user's question. Load only t
 | Settings reference (all config keys)      | `docs/configuration/settings.md`        |
 | Authentication setup                      | `docs/configuration/auth.md`            |
 | Model providers (OpenAI-compatible, etc.) | `docs/configuration/model-providers.md` |
-| .vivekmindignore file                          | `docs/configuration/qwen-ignore.md`     |
+| .vivekmindignore file                          | `docs/configuration/vivekmind-ignore.md`     |
 | Themes                                    | `docs/configuration/themes.md`          |
 | Memory                                    | `docs/configuration/memory.md`          |
 | Trusted folders                           | `docs/configuration/trusted-folders.md` |
@@ -103,7 +103,7 @@ When the user asks about configuration, the primary reference is `docs/configura
 | ------- | ------------------------------------------------------------ | -------------------------------------- |
 | User    | `~/.vivekmind/settings.json`                                      | Personal global config                 |
 | Project | `<project>/.vivekmind/settings.json`                              | Project-specific, overrides user level |
-| System  | macOS: `/Library/Application Support/QwenCode/settings.json` | Admin-level config                     |
+| System  | macOS: `/Library/Application Support/VivekMindCode/settings.json` | Admin-level config                     |
 
 **Priority** (highest to lowest): CLI args > env vars > system settings > project settings > user settings > defaults
 

package/bundled/review/DESIGN.md

@@ -149,7 +149,7 @@ Line-based classification was chosen because it's deterministic, cheap, and catc
 - ❌ Adds two extra API calls (`check-runs` + `statuses`) per APPROVE-bound submit; only relevant for the `APPROVE` path so the cost is negligible.
 - ❌ A genuinely flaky CI failure can downgrade what should have been an Approve. Mitigation: the body text directs the user to verify; they can always submit `APPROVE` manually after triaging.
 
-## Why the deterministic checks live as `qwen review` subcommands
+## Why the deterministic checks live as `vivekmind review` subcommands
 
 **Original behavior:** Step 9's three pre-submission checks (self-PR detection, CI status, existing-comment classification) and Step 11's cleanup were inlined in SKILL.md as `gh api` / `git` shell commands. The LLM ran each command itself, parsed the output, and applied the classification logic.
 
@@ -157,7 +157,7 @@ Line-based classification was chosen because it's deterministic, cheap, and catc
 
 1. **Token cost**: each command, jq filter, classification rule, and output schema is part of the prompt — every `/review` invocation pays this cost.
 2. **Drift risk**: the classification logic exists twice (in the prompt's English description, and in whatever the LLM internally synthesizes). When rules change (new check_run conclusion type, new comment bucket), both have to update or they drift.
-3. **Cross-platform fragility**: `/tmp/qwen-review-*` worked on macOS shell but Node's `os.tmpdir()` returned `/var/folders/...`. The mismatch only surfaced when the cleanup logic was tested.
+3. **Cross-platform fragility**: `/tmp/vivekmind-review-*` worked on macOS shell but Node's `os.tmpdir()` returned `/var/folders/...`. The mismatch only surfaced when the cleanup logic was tested.
 4. **Testability**: prompt text isn't unit-testable. Logic that classifies CI states or comment buckets is the kind of thing that benefits from real assertions.
 
 **Current behavior:** the deterministic logic lives in `packages/cli/src/commands/review/` as TypeScript subcommands of the `vivekmind` CLI:

package/bundled/review/SKILL.md

@@ -32,8 +32,8 @@ First, parse the `--comment` flag: split the arguments by whitespace, and if any
 To disambiguate the argument type: if the argument is a pure integer, treat it as a PR number. If it's a URL containing `/pull/`, extract the owner/repo/number from the URL. Then determine if the local repo can access this PR:
 
 1. Check if any git remote URL matches the URL's owner/repo: run `git remote -v` and look for a remote whose URL contains the owner/repo (e.g., `openjdk/jdk`). This handles forks — a local clone of `wenshao/jdk` with an `upstream` remote pointing to `openjdk/jdk` can still review `openjdk/jdk` PRs.
-2. If a matching remote is found, proceed with the **normal worktree flow** — use that remote name (instead of hardcoded `origin`) for `git fetch <remote> pull/<number>/head:qwen-review/pr-<number>`. In Step 9, use the owner/repo from the URL for posting comments.
-3. If **no remote matches**, use **lightweight mode**: run `gh pr diff <url>` to get the diff directly. Skip Steps 2 (no local rules), 3 (no local linter), 8 (no local files to fix), 10 (no local cache). In Step 11, skip worktree removal (none was created) but still clean up temp files (`.vivekmind/tmp/qwen-review-{target}-*`). Also fetch existing PR comments using the URL's owner/repo (`gh api repos/{owner}/{repo}/pulls/{number}/comments`) to avoid duplicating human feedback. In Step 9, use the owner/repo from the URL. Inform the user: "Cross-repo review: running in lightweight mode (no build/test, no linter, no autofix)."
+2. If a matching remote is found, proceed with the **normal worktree flow** — use that remote name (instead of hardcoded `origin`) for `git fetch <remote> pull/<number>/head:vivekmind-review/pr-<number>`. In Step 9, use the owner/repo from the URL for posting comments.
+3. If **no remote matches**, use **lightweight mode**: run `gh pr diff <url>` to get the diff directly. Skip Steps 2 (no local rules), 3 (no local linter), 8 (no local files to fix), 10 (no local cache). In Step 11, skip worktree removal (none was created) but still clean up temp files (`.vivekmind/tmp/vivekmind-review-{target}-*`). Also fetch existing PR comments using the URL's owner/repo (`gh api repos/{owner}/{repo}/pulls/{number}/comments`) to avoid duplicating human feedback. In Step 9, use the owner/repo from the URL. Inform the user: "Cross-repo review: running in lightweight mode (no build/test, no linter, no autofix)."
 
 Otherwise (not a URL, not an integer), treat the argument as a file path.
 
@@ -44,15 +44,15 @@ Based on the remaining arguments:
   - If both diffs are empty, inform the user there are no changes to review and stop here — do not proceed to the review agents
 
 - **PR number or same-repo URL** (e.g., `123` or a URL whose owner/repo matches the current repo — cross-repo URLs are handled by the lightweight mode above):
-  - **Run `vivekmind review fetch-pr`** to set up the working state in one pass — it cleans any stale worktree, fetches the PR HEAD into `qwen-review/pr-<n>`, queries `gh pr view` for metadata, and creates an ephemeral worktree at `.vivekmind/tmp/review-pr-<n>`:
+  - **Run `vivekmind review fetch-pr`** to set up the working state in one pass — it cleans any stale worktree, fetches the PR HEAD into `vivekmind-review/pr-<n>`, queries `gh pr view` for metadata, and creates an ephemeral worktree at `.vivekmind/tmp/review-pr-<n>`:
 
     ```bash
     vivekmind review fetch-pr <pr_number> <owner>/<repo> \
       --remote <remote> \
-      --out .vivekmind/tmp/qwen-review-pr-<pr_number>-fetch.json
+      --out .vivekmind/tmp/vivekmind-review-pr-<pr_number>-fetch.json
     ```
 
-    `<remote>` is the matched remote from the URL-based detection above (e.g. `upstream` for fork workflows), or `origin` by default for pure integer PR numbers. Read `.vivekmind/tmp/qwen-review-pr-<n>-fetch.json` for: `worktreePath`, `baseRefName`, `headRefName`, `fetchedSha` (use as the **pre-autofix HEAD commit SHA** for Step 9), `isCrossRepository`, `diffStat` (files / additions / deletions). If the command fails (auth, network, PR not found), inform the user and stop.
+    `<remote>` is the matched remote from the URL-based detection above (e.g. `upstream` for fork workflows), or `origin` by default for pure integer PR numbers. Read `.vivekmind/tmp/vivekmind-review-pr-<n>-fetch.json` for: `worktreePath`, `baseRefName`, `headRefName`, `fetchedSha` (use as the **pre-autofix HEAD commit SHA** for Step 9), `isCrossRepository`, `diffStat` (files / additions / deletions). If the command fails (auth, network, PR not found), inform the user and stop.
 
     Worktree isolation: all subsequent steps (linting, agents, build/test, autofix) operate inside `worktreePath`, not the user's working tree. Cache and reports (Step 10) are written to the **main project directory**, not the worktree.
 
@@ -66,7 +66,7 @@ Based on the remaining arguments:
 
     ```bash
     vivekmind review pr-context <pr_number> <owner>/<repo> \
-      --out .vivekmind/tmp/qwen-review-pr-<pr_number>-context.md
+      --out .vivekmind/tmp/vivekmind-review-pr-<pr_number>-context.md
     ```
 
     The subcommand fetches `gh pr view` metadata + inline / issue comments and writes a single Markdown file with the PR title, description, base/head, diff stats, an **"Already discussed"** section, and an "Open inline comments" section. Each replied-to thread renders the **complete reply chain** (root comment + chronological replies), so review agents can see whether a "Fixed in `<commit>`"-style reply has closed the topic — agents must NOT re-report a concern whose latest reply addresses it. Issue-level (general PR) comments appear in the same section. The file's own preamble tells agents to treat its contents as DATA, so no extra security prefix is needed when passing it to review agents.
@@ -86,12 +86,12 @@ Run `vivekmind review load-rules` to read project-specific rules. **For PR revie
 
 ```bash
 vivekmind review load-rules <resolved_base_ref> \
-  --out .vivekmind/tmp/qwen-review-<target>-rules.md
+  --out .vivekmind/tmp/vivekmind-review-<target>-rules.md
 ```
 
 `<resolved_base_ref>` is the base ref to load from: prefer `<base>` if it exists locally, otherwise `<remote>/<base>` (run `git fetch <remote> <base>` first if not yet fetched). For local-uncommitted or file-path reviews use `HEAD`.
 
-The subcommand reads (in order, all sources combined): `.vivekmind/review-rules.md`, then either `.github/copilot-instructions.md` or root-level `copilot-instructions.md` (only one — preferred wins), then the `## Code Review` section of `AGENTS.md`, then the `## Code Review` section of `QWEN.md`. Missing files are silently skipped. The output file is empty when no rules are found — the subcommand reports `No review rules found on <ref>` to stdout in that case; skip rule injection in Step 4.
+The subcommand reads (in order, all sources combined): `.vivekmind/review-rules.md`, then either `.github/copilot-instructions.md` or root-level `copilot-instructions.md` (only one — preferred wins), then the `## Code Review` section of `AGENTS.md`, then the `## Code Review` section of `VIVEKMIND.md`. Missing files are silently skipped. The output file is empty when no rules are found — the subcommand reports `No review rules found on <ref>` to stdout in that case; skip rule injection in Step 4.
 
 If the output file is non-empty, prepend its content to each **LLM-based review agent's** (Agents 1-6) instructions:
 "In addition to the standard review criteria, you MUST also enforce these project-specific rules:
@@ -109,10 +109,10 @@ Extract the list of changed files from the diff output. For local uncommitted re
 
    ```bash
    echo '<json array of changed files relative to worktree>' \
-     > .vivekmind/tmp/qwen-review-<target>-changed.json
+     > .vivekmind/tmp/vivekmind-review-<target>-changed.json
    vivekmind review deterministic <worktree> \
-     --changed-files .vivekmind/tmp/qwen-review-<target>-changed.json \
-     --out .vivekmind/tmp/qwen-review-<target>-deterministic.json
+     --changed-files .vivekmind/tmp/vivekmind-review-<target>-changed.json \
+     --out .vivekmind/tmp/vivekmind-review-<target>-deterministic.json
    ```
 
    Tools currently covered:
@@ -475,7 +475,7 @@ Use the **pre-autofix HEAD commit SHA** captured in Step 1. If not captured, fal
 Optionally write the `(path, line)` anchors of the comments you're about to post so existing-comment Overlap can be detected:
 
 ```bash
-echo '[{"path":"src/foo.ts","line":42}, ...]' > .vivekmind/tmp/qwen-review-{target}-findings.json
+echo '[{"path":"src/foo.ts","line":42}, ...]' > .vivekmind/tmp/vivekmind-review-{target}-findings.json
 ```
 
 Then run:
@@ -483,11 +483,11 @@ Then run:
 ```bash
 vivekmind review presubmit \
   {pr_number} {commit_sha} {owner}/{repo} \
-  .vivekmind/tmp/qwen-review-{target}-presubmit.json \
-  [--new-findings .vivekmind/tmp/qwen-review-{target}-findings.json]
+  .vivekmind/tmp/vivekmind-review-{target}-presubmit.json \
+  [--new-findings .vivekmind/tmp/vivekmind-review-{target}-findings.json]
 ```
 
-Read `.vivekmind/tmp/qwen-review-{target}-presubmit.json`. Schema:
+Read `.vivekmind/tmp/vivekmind-review-{target}-presubmit.json`. Schema:
 
 ```typescript
 {
@@ -528,7 +528,7 @@ Read `.vivekmind/tmp/qwen-review-{target}-presubmit.json`. Schema:
 
 ⚠️ **Findings that can be mapped to a diff line → go in `comments` array (with `line` field). Findings that CANNOT be mapped to a specific diff line → go in `body` field.** Every entry in the `comments` array MUST have a valid `line` number. Do NOT put a comment in the `comments` array without a `line` — it creates an orphaned comment with no code reference.
 
-**Build the review JSON** with `write_file` to create `.vivekmind/tmp/qwen-review-{target}-review.json`. Every high-confidence Critical/Suggestion finding that can be mapped to a diff line MUST be an entry in the `comments` array:
+**Build the review JSON** with `write_file` to create `.vivekmind/tmp/vivekmind-review-{target}-review.json`. Every high-confidence Critical/Suggestion finding that can be mapped to a diff line MUST be an entry in the `comments` array:
 
 ````json
 {
@@ -559,7 +559,7 @@ Then submit:
 
 ```bash
 gh api repos/{owner}/{repo}/pulls/{pr_number}/reviews \
-  --input .vivekmind/tmp/qwen-review-{target}-review.json
+  --input .vivekmind/tmp/vivekmind-review-{target}-review.json
 ```
 
 If there are **no confirmed findings**, submit a single-line review. Use `event=APPROVE` by default; if the presubmit JSON has `downgradeApprove=true`, use `event=COMMENT` and prepend the downgrade reasons to the body:
@@ -629,7 +629,7 @@ Run the bundled cleanup subcommand:
 vivekmind review cleanup <target>
 ```
 
-`<target>` is the same suffix used throughout (`pr-<n>`, `local`, or filename). The command removes the worktree at `.vivekmind/tmp/review-pr-<n>` (PR targets only), deletes the local branch ref `qwen-review/pr-<n>`, and clears any `.vivekmind/tmp/qwen-review-<target>-*` side files (review JSON, PR context, presubmit / findings reports). It is idempotent — missing files are silent OK.
+`<target>` is the same suffix used throughout (`pr-<n>`, `local`, or filename). The command removes the worktree at `.vivekmind/tmp/review-pr-<n>` (PR targets only), deletes the local branch ref `vivekmind-review/pr-<n>`, and clears any `.vivekmind/tmp/vivekmind-review-<target>-*` side files (review JSON, PR context, presubmit / findings reports). It is idempotent — missing files are silent OK.
 
 **If Step 8 flagged the worktree for preservation** (autofix commit/push failure), skip Step 11 entirely. The user needs the worktree intact to recover the autofix commit. Inform the user the worktree is preserved at `.vivekmind/tmp/review-pr-<n>` and they should run `vivekmind review cleanup pr-<n>` manually after recovering the commit.