@machina.ai/cell-cli-core 1.45.1-rc4 → 1.49.0-rc1

package/dist/docs/cli/skills.md

@@ -1,6 +1,6 @@
 # Agent Skills
 
-Agent Skills let you extend Gemini CLI with specialized expertise, procedural
+Agent Skills let you extend Cell CLI with specialized expertise, procedural
 workflows, and task-specific resources. Based on the
 [Agent Skills](https://agentskills.io) open standard, a "skill" is a
 self-contained directory that packages instructions and assets into a
@@ -8,7 +8,7 @@ discoverable capability.
 
 Unlike general context files ([GEMINI.md](./gemini-md.md)), which provide
 persistent workspace-wide background, Skills represent **on-demand expertise**.
-This lets Gemini CLI maintain a vast library of specialized capabilities—such as
+This lets Cell CLI maintain a vast library of specialized capabilities—such as
 security auditing, cloud deployments, or codebase migrations—without cluttering
 the model's immediate context window.
 
@@ -17,8 +17,6 @@ the model's immediate context window.
 The lifecycle of an Agent Skill involves discovery, activation, and conditional
 resource access.
 
-> > > > > > > release/v0.29.5
-
 1.  **Discovery**: At the start of a session, Cell CLI scans the discovery tiers
     and injects the name and description of all enabled skills into the system
     prompt.
@@ -36,23 +34,24 @@ resource access.
 
 ## Discovery tiers
 
-Gemini CLI discovers skills from several locations, following a specific order
-of precedence (lowest to highest):
+Cell CLI discovers skills from several locations, following a specific order of
+precedence (lowest to highest):
 
-1.  **Built-in skills**: Standard skills included with Gemini CLI that provide
+1.  **Built-in skills**: Standard skills included with Cell CLI that provide
     foundational capabilities.
 2.  **Extension skills**: Skills bundled within installed
     [extensions](../extensions/index.md).
-3.  **User skills**: Located in `~/.gemini/skills/` or the `~/.agents/skills/`
+3.  **User skills**: Located in `~/.cell-cli/skills/` or the `~/.agents/skills/`
     alias.
-4.  **Workspace skills**: Located in `.gemini/skills/` or the `.agents/skills/`
-    alias. Workspace skills are shared with your team via version control.
+4.  **Workspace skills**: Located in `.cell-cli/skills/` or the
+    `.agents/skills/` alias. Workspace skills are shared with your team via
+    version control.
 
 ### Precedence and aliases
 
 If multiple skills share the same name, the version from the higher-precedence
 location is used. Within the same tier (user or workspace), the
-`.agents/skills/` alias takes precedence over the `.gemini/skills/` directory.
+`.agents/skills/` alias takes precedence over the `.cell-cli/skills/` directory.
 
 The `.agents/skills/` alias provides an interoperable path for managing
 agent-specific expertise that remains compatible across different AI tools.

package/dist/docs/cli/system-prompt.md

@@ -27,11 +27,13 @@ via a `.cell-cli/.env` file. See
 [Persisting Environment Variables](../get-started/authentication.mdx#persisting-environment-variables).
 
 - Use the project default path (`.cell-cli/system.md`):
+
   - `CELL_SYSTEM_MD=true` or `CELL_SYSTEM_MD=1`
   - The CLI reads `./.cell-cli/system.md` (relative to your current project
     directory).
 
 - Use a custom file path:
+
   - `CELL_SYSTEM_MD=/absolute/path/to/my-system.md`
   - Relative paths are supported and resolved from the current working
     directory.

package/dist/docs/cli/telemetry.md

@@ -64,6 +64,7 @@ and Cloud Logging.
 You must complete several setup steps before enabling Google Cloud telemetry.
 
 1.  Set your Google Cloud project ID:
+
     - To send telemetry to a separate project:
 
       **macOS/Linux**
@@ -93,8 +94,10 @@ You must complete several setup steps before enabling Google Cloud telemetry.
       ```
 
 2.  Authenticate with Google Cloud using one of these methods:
+
     - **Method A: Application Default Credentials (ADC)**: Use this method for
       service accounts or standard `gcloud` authentication.
+
       - For user accounts:
         ```bash
         gcloud auth application-default login
@@ -112,6 +115,7 @@ You must complete several setup steps before enabling Google Cloud telemetry.
         ```powershell
         $env:GOOGLE_APPLICATION_CREDENTIALS="C:\path\to\your\service-account.json"
         ```
+
     * **Method B: CLI Auth** (Direct export only): Simplest method for local
       users. Cell CLI uses the same OAuth credentials you used for login. To
       enable this, set `useCliAuth: true` in your `.cell-cli/settings.json`:
@@ -133,6 +137,7 @@ You must complete several setup steps before enabling Google Cloud telemetry.
 > telemetry will be disabled.
 
 3.  Ensure your account or service account has these IAM roles:
+
     - Cloud Trace Agent
     - Monitoring Metric Writer
     - Logs Writer

package/dist/docs/core/local-model-routing.md

@@ -15,6 +15,16 @@ routing decisions to a hosted model).
 > using the [`gemini gemma` Setup Guide](./gemma-setup.md) instead of following
 > these manual steps.
 
+<!-- prettier-ignore -->
+> [!NOTE]
+> This is an experimental feature currently under active development.
+
+<!-- prettier-ignore -->
+> [!IMPORTANT]
+> **Recommended:** We now provide a fully automated setup command. We recommend
+> using the [`gemini gemma` Setup Guide](./gemma-setup.md) instead of following
+> these manual steps.
+
 This feature can help reduce costs associated with hosted model usage while
 offering similar routing decision latency and quality.
 

package/dist/docs/core/subagents.md

@@ -106,7 +106,7 @@ Cell CLI comes with the following built-in subagents:
     slow. You can invoke it explicitly using `@generalist`.
 - **Configuration:** Enabled by default.
 
-### Browser Agent (experimental)
+### Browser Agent
 
 - **Name:** `browser_agent`
 - **Purpose:** Automate web browser tasks — navigating websites, filling forms,
@@ -116,10 +116,6 @@ Cell CLI comes with the following built-in subagents:
   the pricing table from this page," "Click the login button and enter my
   credentials."
 
-<!-- prettier-ignore -->
-> [!NOTE]
-> This is a preview feature currently under active development.
-
 #### Prerequisites
 
 The browser agent requires:

package/dist/docs/ide-integration/ide-companion-spec.md

@@ -56,6 +56,7 @@ creating a "discovery file."
     }
   }
   ```
+
   - `port` (number, required): The port of the MCP server.
   - `workspacePath` (string, required): A list of all open workspace root paths,
     delimited by the OS-specific path separator (`:` for Linux/macOS, `;` for
@@ -187,6 +188,7 @@ The plugin **MUST** register an `openDiff` tool on its MCP server.
 - **Response (`CallToolResult`):** The tool **MUST** immediately return a
   `CallToolResult` to acknowledge the request and report whether the diff view
   was successfully opened.
+
   - On Success: If the diff view was opened successfully, the response **MUST**
     contain empty content (that is, `content: []`).
   - On Failure: If an error prevented the diff view from opening, the response

package/dist/docs/ide-integration/index.md

@@ -27,6 +27,7 @@ AI-generated code changes directly within your editor.
 
 - **Workspace context:** The CLI automatically gains awareness of your workspace
   to provide more relevant and accurate responses. This context includes:
+
   - The **10 most recently accessed files** in your workspace.
   - Your active cursor position.
   - Any text you have selected (up to a 16KB limit; longer selections will be
@@ -227,6 +228,7 @@ If you are using Cell CLI within a sandbox, be aware of the following:
 
 - **Message:**
   `🔴 Disconnected: Failed to connect to IDE companion extension in [IDE Name]. Please ensure the extension is running. To install the extension, run /ide install.`
+
   - **Cause:** Cell CLI could not find the necessary environment variables
     (`CELL_CLI_IDE_WORKSPACE_PATH` or `CELL_CLI_IDE_SERVER_PORT`) to connect to
     the IDE. This usually means the IDE companion extension is not running or
@@ -269,6 +271,7 @@ connect using the provided PID.
 
 - **Message:**
   `🔴 Disconnected: Directory mismatch. Cell CLI is running in a different location than the open workspace in [IDE Name]. Please run the CLI from one of the following directories: [List of directories]`
+
   - **Cause:** The CLI's current working directory is outside the workspace you
     have open in your IDE.
   - **Solution:** `cd` into the same directory that is open in your IDE and
@@ -283,6 +286,7 @@ connect using the provided PID.
 
 - **Message:**
   `IDE integration is not supported in your current environment. To use this feature, run Cell CLI in one of these supported IDEs: [List of IDEs]`
+
   - **Cause:** You are running Cell CLI in a terminal or environment that is not
     a supported IDE.
   - **Solution:** Run Cell CLI from the integrated terminal of a supported IDE,

package/dist/docs/issue-and-pr-automation.md

@@ -154,7 +154,35 @@ and will never be auto-unassigned.
   - **Unassign yourself** if you can no longer work on the issue by commenting
     `/unassign`, so other contributors can pick it up right away.
 
-### 6. Release automation
+### 6. Automatically label PRs by size: `PR Size Labeler`
+
+To help maintainers estimate review effort and keep the PR history clean, this
+workflow automatically tags every pull request with a size label representing
+the total volume of line changes.
+
+- **Workflow File**: `.github/workflows/pr-size-labeler.yml`
+- **When it runs**: Immediately after a pull request is created, synchronized
+  (new commits pushed), or reopened. It can also be triggered manually via
+  `workflow_dispatch` with a PR number.
+- **What it does**:
+  - **Calculates total changes**: Summarizes additions and deletions across all
+    changed files in a single consolidated API request.
+  - **Applies standard size labels**:
+    - `size/XS`: < 10 lines changed
+    - `size/S`: 10-49 lines changed
+    - `size/M`: 50-249 lines changed
+    - `size/L`: 250-999 lines changed
+    - `size/XL`: >= 1000 lines changed
+  - **Updates size tag atomically**: Adds the new correct size label and removes
+    any obsolete size labels in one atomic step.
+  - **Updates/Posts PR size info comment**: Instead of spamming a new comment on
+    every commit push, it updates the existing size labeler status comment
+    inline to keep the PR conversation timeline perfectly neat and clean.
+- **What you should do**:
+  - You do not need to take any actions. The workflow runs automatically and
+    updates the label and comment seamlessly as you push new updates.
+
+### 7. Release automation
 
 This workflow handles the process of packaging and publishing new versions of
 Cell CLI.

package/dist/docs/local-development.md

@@ -59,6 +59,7 @@ You can view traces in the Jaeger UI for local development.
 
     This command configures your workspace for local telemetry and provides a
     link to the Jaeger UI (usually `http://localhost:16686`).
+
     - **Collector logs:** `~/.cell-cli/tmp/<projectHash>/otel/collector.log`
 
 2.  **Run Cell CLI:**
@@ -108,6 +109,7 @@ Trace for custom processing or routing.
 
     The script outputs links to view traces, metrics, and logs in the Google
     Cloud Console.
+
     - **Collector logs:** `~/.cell-cli/tmp/<projectHash>/otel/collector-gcp.log`
 
 3.  **Run Cell CLI:**

package/dist/docs/mcp_integration.md

@@ -124,6 +124,7 @@ Una vez que haya realizado los cambios en el código y reconstruido el CLI, pued
 verificar que la integración funciona correctamente de la siguiente manera:
 
 1.  **Asegúrese de que su configuración sea correcta:**
+
     - Verifique que el archivo `~/.cell-cli/config.yaml` existe y contiene una
       entrada válida para `agent_api_url`. Por ejemplo:
       ```yaml

package/dist/docs/reference/commands.md

@@ -505,6 +505,7 @@ the dedicated [Custom Commands documentation](../cli/custom-commands.md).
 These shortcuts apply directly to the input prompt for text manipulation.
 
 - **Undo:**
+
   - **Keyboard shortcut:** Press **Ctrl+z** (Windows), **Cmd+z** (macOS), or
     **Alt+z** (Linux/WSL) to undo the last action in the input prompt.
 
@@ -518,6 +519,7 @@ At commands are used to include the content of files or directories as part of
 your prompt to Gemini. These commands include git-aware filtering.
 
 - **`@<path_to_file_or_directory>`**
+
   - **Description:** Inject the content of the specified file or files into your
     current prompt. This is useful for asking questions about specific code,
     text, or collections of files.
@@ -564,6 +566,7 @@ The `!` prefix lets you interact with your system's shell directly from within
 Cell CLI.
 
 - **`!<shell_command>`**
+
   - **Description:** Execute the given `<shell_command>` using `bash` on
     Linux/macOS or `powershell.exe -NoProfile -Command` on Windows (unless you
     override `ComSpec`). Any output or errors from the command are displayed in
@@ -573,6 +576,7 @@ Cell CLI.
     - `!git status` (executes `git status` and returns to Cell CLI)
 
 - **`!` (Toggle shell mode)**
+
   - **Description:** Typing `!` on its own toggles shell mode.
     - **Entering shell mode:**
       - When active, shell mode uses a different coloring and a "Shell Mode