npm - @mmmbuto/gemini-cli-termux - Versions diffs - 0.30.3-termux → 0.30.5-termux - Mend

@mmmbuto/gemini-cli-termux 0.30.3-termux → 0.30.5-termux

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (400) hide show

package/bundle/docs/termux-api/README.md DELETED Viewed

@@ -1,416 +0,0 @@
-# Termux-API Integration Plan
-**Project**: gemini-cli-termux **Version**: 0.22.0-termux **Author**: DioNanos
-**Date**: 2025-12-17 **Status**: Planning Phase
----
-## Executive Summary
-This document describes the plan to integrate native Termux-API commands into
-the `gemini-cli-termux` fork, allowing Gemini CLI to leverage Android hardware
-and software APIs through Termux.
-## Table of Contents
-1. [Current Architecture](#current-architecture)
-2. [Termux-API Commands](#termux-api-commands)
-3. [Integration Approaches](#integration-approaches)
-4. [Recommendation](#recommendation)
-5. [Implementation Roadmap](#implementation-roadmap)
-6. [Reference Files](#reference-files)
----
-## Current Architecture
-### Monorepo Structure
-```
-gemini-cli-termux/
-├── packages/
-│   ├── core/           # Logic core, tools, config
-│   │   └── src/
-│   │       ├── tools/  # Tool implementations
-│   │       ├── mcp/    # MCP support
-│   │       └── config/ # Configuration
-│   ├── cli/            # CLI interface
-│   ├── a2a-server/     # Agent-to-Agent server
-│   └── vscode-ide-companion/
-└── bundle/             # Built executable
-```
-### Tool System
-Tools in Gemini CLI follow a well-defined pattern:
-1. **BaseDeclarativeTool**: Base class for defining tools
-2. **BaseToolInvocation**: Class for tool execution
-3. **ToolRegistry**: Registers and manages all tools
-**Key files**:
-- `packages/core/src/tools/tools.ts` - Interfaces and base classes
-- `packages/core/src/tools/tool-registry.ts` - Tool registry
-- `packages/core/src/tools/shell.ts` - Example: ShellTool
-### Tool Call Flow
-```
-LLM → ToolRegistry.getTool() → DeclarativeTool.build() → ToolInvocation.execute()
-```
-### Discovery Mechanisms
-1. **Built-in Tools**: Manually registered in the registry
-2. **Discovered Tools**: Via `tool_discovery_command` in config
-3. **MCP Tools**: Via Model Context Protocol servers
----
-## Termux-API Commands
-### Categorization by Functionality
-| Category           | Commands                                                                                                 | Complexity      |
-| ------------------ | -------------------------------------------------------------------------------------------------------- | --------------- |
-| **System Info**    | battery-status, audio-info, wifi-connectioninfo, wifi-scaninfo, telephony-deviceinfo, telephony-cellinfo | Low             |
-| **Notifications**  | notification, notification-remove, notification-list, toast                                              | Low             |
-| **Clipboard**      | clipboard-get, clipboard-set                                                                             | Low             |
-| **Media**          | camera-photo, camera-info, microphone-record, media-player, media-scan, tts-speak, speech-to-text        | Medium          |
-| **Location**       | location                                                                                                 | Medium          |
-| **Sensors**        | sensor, infrared-frequencies, infrared-transmit, torch, vibrate, brightness                              | Medium          |
-| **Communication**  | sms-send, sms-inbox, sms-list, telephony-call, call-log, contact-list                                    | High (privacy)  |
-| **Storage**        | storage-get, download, share, open, open-url, saf-\*                                                     | Medium          |
-| **Security**       | fingerprint, keystore                                                                                    | High (security) |
-| **System Control** | volume, wake-lock, wake-unlock, wallpaper, wifi-enable                                                   | Medium          |
-| **Dialogs**        | dialog                                                                                                   | Medium          |
-| **NFC**            | nfc                                                                                                      | High            |
-| **USB**            | usb                                                                                                      | High            |
-| **Job Scheduler**  | job-scheduler                                                                                            | Medium          |
-### Priority Commands (Phase 1)
-1. **termux-battery-status** - Battery info (JSON output)
-2. **termux-clipboard-get/set** - Clipboard operations
-3. **termux-toast** - Toast notifications
-4. **termux-notification** - Persistent notifications
-5. **termux-tts-speak** - Text-to-Speech
-6. **termux-vibrate** - Haptic feedback
-7. **termux-torch** - Flashlight control
-8. **termux-location** - GPS location
-9. **termux-wifi-connectioninfo** - Network info
-10. **termux-audio-info** - Audio info
----
-## Integration Approaches
-### Approach A: Native Dedicated Tools
-**Description**: Create dedicated TypeScript classes for each category of Termux
-commands.
-**Proposed Structure**:
-```
-packages/core/src/tools/termux/
-├── index.ts
-├── termux-base.ts
-├── termux-system.ts      # battery, wifi, audio, telephony
-├── termux-notification.ts # toast, notification
-├── termux-clipboard.ts   # clipboard operations
-├── termux-media.ts       # camera, microphone, tts, speech
-├── termux-location.ts    # GPS
-├── termux-sensors.ts     # sensor, torch, vibrate
-└── termux-storage.ts     # download, share, open
-```
-**Pros**:
-- Deep integration with Gemini
-- Type-safe parameter validation
-- LLM-optimized descriptions
-- Specific error handling
-- Granular user confirmation
-**Cons**:
-- Much code to write (~50 tools)
-- Ongoing maintenance
-- Strong coupling
-**Estimated Effort**: High (2-3 weeks)
----
-### Approach B: MCP Server for Termux-API
-**Description**: Create a standalone MCP server that exposes all Termux commands
-as MCP tools.
-**Proposed Structure**:
-```
-termux-mcp-server/
-├── package.json
-├── src/
-│   ├── index.ts          # MCP server entry
-│   ├── tools/            # Tool definitions
-│   └── utils/            # Helper functions
-└── README.md
-```
-**Configuration**:
-```json
-// settings.json
-{
-  "mcpServers": {
-    "termux": {
-      "command": "npx",
-      "args": ["@mmmbuto/termux-mcp-server"]
-    }
-  }
-}
-```
-**Pros**:
-- Reusable with other MCP clients
-- Separation of concerns
-- Easy to update independently
-- Widely supported MCP standard
-- Publishable to npm separately
-**Cons**:
-- Communication overhead
-- Separate process dependency
-- More complex debugging
-**Estimated Effort**: Medium (1-2 weeks)
----
-### Approach C: Tool Discovery Script
-**Description**: Create a script that generates FunctionDeclarations for Termux
-commands, leveraging the existing tool discovery mechanism.
-**Implementation**:
-```bash
-# termux-tool-discovery.sh
-#!/bin/bash
-cat << 'EOF'
-[
-  {
-    "name": "termux_battery_status",
-    "description": "Get battery status including percentage, health, and charging state",
-    "parametersJsonSchema": {
-      "type": "object",
-      "properties": {}
-    }
-  },
-  ...
-]
-EOF
-```
-**Configuration**:
-```json
-// settings.json
-{
-  "tool_discovery_command": "bash ~/.config/gemini/termux-tool-discovery.sh",
-  "tool_call_command": "bash ~/.config/gemini/termux-tool-call.sh"
-}
-```
-**Pros**:
-- Leverages existing infrastructure
-- Zero core modifications
-- User configurable
-- Easy to extend
-**Cons**:
-- Less control over validation
-- Depends on external scripts
-- Limited error handling
-**Estimated Effort**: Low (3-5 days)
----
-### Approach D: Shell Allowlist Extension
-**Description**: Extend shell permissions to auto-approve `termux-*` commands.
-**Implementation**:
-```typescript
-// packages/core/src/utils/shell-permissions.ts
-const TERMUX_COMMANDS = [
-  'termux-battery-status',
-  'termux-clipboard-get',
-  'termux-clipboard-set',
-  // ...
-];
-export function isTermuxCommand(command: string): boolean {
-  return TERMUX_COMMANDS.some((tc) => command.startsWith(tc));
-}
-```
-**Pros**:
-- Minimal code impact
-- Uses existing ShellTool
-- Quick win
-**Cons**:
-- No additional semantics
-- LLM must know the syntax
-- No parameter validation
-- No description for LLM
-**Estimated Effort**: Minimal (1-2 days)
----
-### Approach E: Hybrid (Recommended)
-**Description**: Combine approaches B and C for maximum flexibility.
-**Phase 1**: Tool Discovery Script (quick win)
-- Generates declarations for all commands
-- Allows Gemini to use Termux immediately
-**Phase 2**: MCP Server (production)
-- Implements complete MCP server
-- Robust validation
-- Publishable to npm
-**Phase 3**: Native Tools (optional)
-- Only for critical/frequent commands
-- Optimized integration
----
-## Recommendation
-**Recommended Approach: E (Hybrid)**
-### Rationale
-1. **Quick Win**: Tool Discovery allows starting immediately
-2. **Scalability**: MCP Server is the standard for extensions
-3. **Flexibility**: Native tools only where needed
-4. **Maintainability**: Each phase can be developed independently
-### Implementation Priority
-| Phase | Approach         | Commands                        | Priority |
-| ----- | ---------------- | ------------------------------- | -------- |
-| 1     | Discovery Script | All                             | High     |
-| 2     | MCP Server       | System, Clipboard, Notification | Medium   |
-| 3     | Native Tools     | TTS, Location                   | Low      |
----
-## Implementation Roadmap
-### Phase 1: Tool Discovery (Quick Win)
-**Files to create**:
-- `scripts/termux-tool-discovery.sh`
-- `scripts/termux-tool-call.sh`
-- `docs/termux-api/DISCOVERY_SETUP.md`
-**Tasks**:
-1. [ ] Create discovery script with all FunctionDeclarations
-2. [ ] Create call script with command dispatch
-3. [ ] Document user configuration
-4. [ ] Test on Termux
-5. [ ] Update README
-### Phase 2: MCP Server
-**Files to create**:
-- New package `packages/termux-mcp/`
-- Or separate repository `termux-mcp-server`
-**Tasks**:
-1. [ ] Scaffold MCP server
-2. [ ] Implement System tools (battery, wifi, audio)
-3. [ ] Implement Clipboard tools
-4. [ ] Implement Notification tools
-5. [ ] Implement Media tools
-6. [ ] Test integration
-7. [ ] Publish to npm
-### Phase 3: Native Tools (Optional)
-**Files to modify**:
-- `packages/core/src/tools/` - New tool files
-- `packages/core/src/index.ts` - Export tools
-**Tasks**:
-1. [ ] Implement TermuxTTSTool
-2. [ ] Implement TermuxLocationTool
-3. [ ] Implement TermuxClipboardTool
-4. [ ] Register tools in registry
-5. [ ] Test and documentation
----
-## Reference Files
-### Core Architecture
-| File                                       | Description            |
-| ------------------------------------------ | ---------------------- |
-| `packages/core/src/tools/tools.ts`         | Base tool interfaces   |
-| `packages/core/src/tools/tool-registry.ts` | Registry and discovery |
-| `packages/core/src/tools/shell.ts`         | Example ShellTool      |
-| `packages/core/src/tools/mcp-tool.ts`      | MCP tool wrapper       |
-| `packages/core/src/tools/mcp-client.ts`    | MCP client             |
-### Configuration
-| File                                   | Description     |
-| -------------------------------------- | --------------- |
-| `packages/core/src/config/config.ts`   | Config loader   |
-| `packages/core/src/config/settings.ts` | Settings schema |
-### Existing Documentation
-| File             | Description      |
-| ---------------- | ---------------- |
-| `docs/TERMUX.md` | Setup Termux     |
-| `README.md`      | Project Overview |
----
-## Appendices
-- [COMMANDS.md](./COMMANDS.md) - Termux-API commands detail
-- [DISCOVERY_SETUP.md](./DISCOVERY_SETUP.md) - Tool Discovery setup guide
-- [MCP_SERVER.md](./MCP_SERVER.md) - MCP Server specifications
----
-_Author: DioNanos_

package/bundle/docs/troubleshooting.md DELETED Viewed

@@ -1,173 +0,0 @@
-# Troubleshooting guide
-This guide provides solutions to common issues and debugging tips, including
-topics on:
-- Authentication or login errors
-- Frequently asked questions (FAQs)
-- Debugging tips
-- Existing GitHub Issues similar to yours or creating new Issues
-## Authentication or login errors
-- **Error:
-  `You must be a named user on your organization's Gemini Code Assist Standard edition subscription to use this service. Please contact your administrator to request an entitlement to Gemini Code Assist Standard edition.`**
-  - **Cause:** This error might occur if Gemini CLI detects the
-    `GOOGLE_CLOUD_PROJECT` or `GOOGLE_CLOUD_PROJECT_ID` environment variable is
-    defined. Setting these variables forces an organization subscription check.
-    This might be an issue if you are using an individual Google account not
-    linked to an organizational subscription.
-  - **Solution:**
-    - **Individual Users:** Unset the `GOOGLE_CLOUD_PROJECT` and
-      `GOOGLE_CLOUD_PROJECT_ID` environment variables. Check and remove these
-      variables from your shell configuration files (for example, `.bashrc`,
-      `.zshrc`) and any `.env` files. If this doesn't resolve the issue, try
-      using a different Google account.
-    - **Organizational Users:** Contact your Google Cloud administrator to be
-      added to your organization's Gemini Code Assist subscription.
-- **Error:
-  `Failed to login. Message: Your current account is not eligible... because it is not currently available in your location.`**
-  - **Cause:** Gemini CLI does not currently support your location. For a full
-    list of supported locations, see the following pages:
-    - Gemini Code Assist for individuals:
-      [Available locations](https://developers.google.com/gemini-code-assist/resources/available-locations#americas)
-- **Error: `Failed to login. Message: Request contains an invalid argument`**
-  - **Cause:** Users with Google Workspace accounts or Google Cloud accounts
-    associated with their Gmail accounts may not be able to activate the free
-    tier of the Google Code Assist plan.
-  - **Solution:** For Google Cloud accounts, you can work around this by setting
-    `GOOGLE_CLOUD_PROJECT` to your project ID. Alternatively, you can obtain the
-    Gemini API key from
-    [Google AI Studio](http://aistudio.google.com/app/apikey), which also
-    includes a separate free tier.
-- **Error: `UNABLE_TO_GET_ISSUER_CERT_LOCALLY` or
-  `unable to get local issuer certificate`**
-  - **Cause:** You may be on a corporate network with a firewall that intercepts
-    and inspects SSL/TLS traffic. This often requires a custom root CA
-    certificate to be trusted by Node.js.
-  - **Solution:** First try setting `NODE_USE_SYSTEM_CA`; if that does not
-    resolve the issue, set `NODE_EXTRA_CA_CERTS`.
-    - Set the `NODE_USE_SYSTEM_CA=1` environment variable to tell Node.js to use
-      the operating system's native certificate store (where corporate
-      certificates are typically already installed).
-      - Example: `export NODE_USE_SYSTEM_CA=1`
-    - Set the `NODE_EXTRA_CA_CERTS` environment variable to the absolute path of
-      your corporate root CA certificate file.
-      - Example: `export NODE_EXTRA_CA_CERTS=/path/to/your/corporate-ca.crt`
-## Common error messages and solutions
-- **Error: `EADDRINUSE` (Address already in use) when starting an MCP server.**
-  - **Cause:** Another process is already using the port that the MCP server is
-    trying to bind to.
-  - **Solution:** Either stop the other process that is using the port or
-    configure the MCP server to use a different port.
-- **Error: Command not found (when attempting to run Gemini CLI with
-  `gemini`).**
-  - **Cause:** Gemini CLI is not correctly installed or it is not in your
-    system's `PATH`.
-  - **Solution:** The update depends on how you installed Gemini CLI:
-    - If you installed `gemini` globally, check that your `npm` global binary
-      directory is in your `PATH`. You can update Gemini CLI using the command
-      `npm install -g @google/gemini-cli@latest`.
-    - If you are running `gemini` from source, ensure you are using the correct
-      command to invoke it (e.g., `node packages/cli/dist/index.js ...`). To
-      update Gemini CLI, pull the latest changes from the repository, and then
-      rebuild using the command `npm run build`.
-- **Error: `MODULE_NOT_FOUND` or import errors.**
-  - **Cause:** Dependencies are not installed correctly, or the project hasn't
-    been built.
-  - **Solution:**
-    1.  Run `npm install` to ensure all dependencies are present.
-    2.  Run `npm run build` to compile the project.
-    3.  Verify that the build completed successfully with `npm run start`.
-- **Error: "Operation not permitted", "Permission denied", or similar.**
-  - **Cause:** When sandboxing is enabled, Gemini CLI may attempt operations
-    that are restricted by your sandbox configuration, such as writing outside
-    the project directory or system temp directory.
-  - **Solution:** Refer to the [Configuration: Sandboxing](./cli/sandbox.md)
-    documentation for more information, including how to customize your sandbox
-    configuration.
-- **Gemini CLI is not running in interactive mode in "CI" environments**
-  - **Issue:** The Gemini CLI does not enter interactive mode (no prompt
-    appears) if an environment variable starting with `CI_` (e.g., `CI_TOKEN`)
-    is set. This is because the `is-in-ci` package, used by the underlying UI
-    framework, detects these variables and assumes a non-interactive CI
-    environment.
-  - **Cause:** The `is-in-ci` package checks for the presence of `CI`,
-    `CONTINUOUS_INTEGRATION`, or any environment variable with a `CI_` prefix.
-    When any of these are found, it signals that the environment is
-    non-interactive, which prevents the Gemini CLI from starting in its
-    interactive mode.
-  - **Solution:** If the `CI_` prefixed variable is not needed for the CLI to
-    function, you can temporarily unset it for the command. e.g.,
-    `env -u CI_TOKEN gemini`
-- **DEBUG mode not working from project .env file**
-  - **Issue:** Setting `DEBUG=true` in a project's `.env` file doesn't enable
-    debug mode for gemini-cli.
-  - **Cause:** The `DEBUG` and `DEBUG_MODE` variables are automatically excluded
-    from project `.env` files to prevent interference with gemini-cli behavior.
-  - **Solution:** Use a `.gemini/.env` file instead, or configure the
-    `advanced.excludedEnvVars` setting in your `settings.json` to exclude fewer
-    variables.
-## Exit codes
-The Gemini CLI uses specific exit codes to indicate the reason for termination.
-This is especially useful for scripting and automation.
-| Exit Code | Error Type                 | Description                                                                                         |
-| --------- | -------------------------- | --------------------------------------------------------------------------------------------------- |
-| 41        | `FatalAuthenticationError` | An error occurred during the authentication process.                                                |
-| 42        | `FatalInputError`          | Invalid or missing input was provided to the CLI. (non-interactive mode only)                       |
-| 44        | `FatalSandboxError`        | An error occurred with the sandboxing environment (e.g., Docker, Podman, or Seatbelt).              |
-| 52        | `FatalConfigError`         | A configuration file (`settings.json`) is invalid or contains errors.                               |
-| 53        | `FatalTurnLimitedError`    | The maximum number of conversational turns for the session was reached. (non-interactive mode only) |
-## Debugging tips
-- **CLI debugging:**
-  - Use the `--debug` flag for more detailed output. In interactive mode, press
-    F12 to view the debug console.
-  - Check the CLI logs, often found in a user-specific configuration or cache
-    directory.
-- **Core debugging:**
-  - Check the server console output for error messages or stack traces.
-  - Increase log verbosity if configurable. For example, set the `DEBUG_MODE`
-    environment variable to `true` or `1`.
-  - Use Node.js debugging tools (e.g., `node --inspect`) if you need to step
-    through server-side code.
-- **Tool issues:**
-  - If a specific tool is failing, try to isolate the issue by running the
-    simplest possible version of the command or operation the tool performs.
-  - For `run_shell_command`, check that the command works directly in your shell
-    first.
-  - For _file system tools_, verify that paths are correct and check the
-    permissions.
-- **Pre-flight checks:**
-  - Always run `npm run preflight` before committing code. This can catch many
-    common issues related to formatting, linting, and type errors.
-## Existing GitHub issues similar to yours or creating new issues
-If you encounter an issue that was not covered here in this _Troubleshooting
-guide_, consider searching the Gemini CLI
-[Issue tracker on GitHub](https://github.com/google-gemini/gemini-cli/issues).
-If you can't find an issue similar to yours, consider creating a new GitHub
-Issue with a detailed description. Pull requests are also welcome!
-> **Note:** Issues tagged as "🔒Maintainers only" are reserved for project
-> maintainers. We will not accept pull requests related to these issues.

package/bundle/policies/conseca.toml DELETED Viewed

@@ -1,6 +0,0 @@
-[[safety_checker]]
-toolName = "*"
-priority = 100
-[safety_checker.checker]
-type = "in-process"
-name = "conseca"

package/bundle/sandbox-macos-permissive-closed.sb DELETED Viewed

@@ -1,32 +0,0 @@
-(version 1)
-;; allow everything by default
-(allow default)
-;; deny all writes EXCEPT under specific paths
-(deny file-write*)
-(allow file-write*
-    (subpath (param "TARGET_DIR"))
-    (subpath (param "TMP_DIR"))
-    (subpath (param "CACHE_DIR"))
-    (subpath (string-append (param "HOME_DIR") "/.gemini"))
-    (subpath (string-append (param "HOME_DIR") "/.npm"))
-    (subpath (string-append (param "HOME_DIR") "/.cache"))
-    (subpath (string-append (param "HOME_DIR") "/.gitconfig"))
-    ;; Allow writes to included directories from --include-directories
-    (subpath (param "INCLUDE_DIR_0"))
-    (subpath (param "INCLUDE_DIR_1"))
-    (subpath (param "INCLUDE_DIR_2"))
-    (subpath (param "INCLUDE_DIR_3"))
-    (subpath (param "INCLUDE_DIR_4"))
-    (literal "/dev/stdout")
-    (literal "/dev/stderr")
-    (literal "/dev/null")
-)
-;; deny all inbound network traffic EXCEPT on debugger port
-(deny network-inbound)
-(allow network-inbound (local ip "localhost:9229"))
-;; deny all outbound network traffic
-(deny network-outbound)