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

package/bundle/docs/ROADMAP.md

@@ -1,113 +0,0 @@
-# Gemini CLI Roadmap
-
-The
-[Official Gemini CLI Roadmap](https://github.com/orgs/google-gemini/projects/11/)
-
-Gemini CLI is an open-source AI agent that brings the power of Gemini directly
-into your terminal. It provides lightweight access to Gemini, giving you the
-most direct path from your prompt to our model.
-
-This document outlines our approach to the Gemini CLI roadmap. Here, you'll find
-our guiding principles and a breakdown of the key areas we are focused on for
-development. Our roadmap is not a static list but a dynamic set of priorities
-that are tracked live in our GitHub Issues.
-
-As an
-[Apache 2.0 open source project](https://github.com/google-gemini/gemini-cli?tab=Apache-2.0-1-ov-file#readme),
-we appreciate and welcome
-[public contributions](https://github.com/google-gemini/gemini-cli/blob/main/CONTRIBUTING.md),
-and will give first priority to those contributions aligned with our roadmap. If
-you want to propose a new feature or change to our roadmap, please start by
-[opening an issue for discussion](https://github.com/google-gemini/gemini-cli/issues/new/choose).
-
-## Disclaimer
-
-This roadmap represents our current thinking and is for informational purposes
-only. It is not a commitment or a guarantee of future delivery. The development,
-release, and timing of any features are subject to change, and we may update the
-roadmap based on community discussions as well as when our priorities evolve.
-
-## Guiding Principles
-
-Our development is guided by the following principles:
-
-- **Power & Simplicity:** Deliver access to state-of-the-art Gemini models with
-  an intuitive and easy-to-use lightweight command-line interface.
-- **Extensibility:** An adaptable agent to help you with a variety of use cases
-  and environments along with the ability to run these agents anywhere.
-- **Intelligent:** Gemini CLI should be reliably ranked among the best agentic
-  tools as measured by benchmarks like SWE Bench, Terminal Bench, and CSAT.
-- **Free and Open Source:** Foster a thriving open source community where cost
-  isn’t a barrier to personal use, and PRs get merged quickly. This means
-  resolving and closing issues, pull requests, and discussion posts quickly.
-
-## How the Roadmap Works
-
-Our roadmap is managed directly through GitHub Issues. See our entry point
-Roadmap Issue [here](https://github.com/google-gemini/gemini-cli/issues/4191).
-This approach allows for transparency and gives you a direct way to learn more
-or get involved with any specific initiative. All our roadmap items will be
-tagged as Type:`Feature` and Label:`maintainer` for features we are actively
-working on, or Type:`Task` and Label:`maintainer` for a more detailed list of
-tasks.
-
-Issues are organized to provide key information at a glance:
-
-- **Target Quarter:** `Milestone` denotes the anticipated delivery timeline.
-- **Feature Area:** Labels such as `area/model` or `area/tooling` categorize the
-  work.
-- **Issue Type:** _Workstream_ => _Epics_ => _Features_ => _Tasks|Bugs_
-
-To see what we're working on, you can filter our issues by these dimensions. See
-all our items [here](https://github.com/orgs/google-gemini/projects/11/views/19)
-
-## Focus Areas
-
-To better organize our efforts, we categorize our work into several key feature
-areas. These labels are used on our GitHub Issues to help you filter and find
-initiatives that interest you.
-
-- **Authentication:** Secure user access via API keys, Gemini Code Assist login,
-  etc.
-- **Model:** Support new Gemini models, multi-modality, local execution, and
-  performance tuning.
-- **User Experience:** Improve the CLI's usability, performance, interactive
-  features, and documentation.
-- **Tooling:** Built-in tools and the MCP ecosystem.
-- **Core:** Core functionality of the CLI
-- **Extensibility:** Bringing Gemini CLI to other surfaces e.g. GitHub.
-- **Contribution:** Improve the contribution process via test automation and
-  CI/CD pipeline enhancements.
-- **Platform:** Manage installation, OS support, and the underlying CLI
-  framework.
-- **Quality:** Focus on testing, reliability, performance, and overall product
-  quality.
-- **Background Agents:** Enable long-running, autonomous tasks and proactive
-  assistance.
-- **Security and Privacy:** For all things related to security and privacy
-
-## How to Contribute
-
-Gemini CLI is an open-source project, and we welcome contributions from the
-community! Whether you're a developer, a designer, or just an enthusiastic user
-you can find our
-[Community Guidelines here](https://github.com/google-gemini/gemini-cli/blob/main/CONTRIBUTING.md)
-to learn how to get started. There are many ways to get involved:
-
-- **Roadmap:** Please review and find areas in our
-  [roadmap](https://github.com/google-gemini/gemini-cli/issues/4191) that you
-  would like to contribute to. Contributions based on this will be easiest to
-  integrate with.
-- **Report Bugs:** If you find an issue, please create a
-  [bug](https://github.com/google-gemini/gemini-cli/issues/new?template=bug_report.yml)
-  with as much detail as possible. If you believe it is a critical breaking
-  issue preventing direct CLI usage, please tag it as `priority/p0`.
-- **Suggest Features:** Have a great idea? We'd love to hear it! Open a
-  [feature request](https://github.com/google-gemini/gemini-cli/issues/new?template=feature_request.yml).
-- **Contribute Code:** Check out our
-  [CONTRIBUTING.md](https://github.com/google-gemini/gemini-cli/blob/main/CONTRIBUTING.md)
-  file for guidelines on how to submit pull requests. We have a list of "good
-  first issues" for new contributors.
-- **Write Documentation:** Help us improve our documentation, tutorials, and
-  examples. We are excited about the future of Gemini CLI and look forward to
-  building it with you!

package/bundle/docs/TERMUX.md

@@ -1,95 +0,0 @@
-# Gemini CLI – Termux Guide
-
-How to install and run the Termux edition `@mmmbuto/gemini-cli-termux` on
-Android.
-
-## Prerequisites
-
-- Termux installed
-- Node.js 20+ (`pkg install nodejs-lts -y`)
-- Git (only if building from source)
-
-## Install via npm (recommended)
-
-```bash
-npm install -g @mmmbuto/gemini-cli-termux
-
-gemini --version
-# expected: 0.24.6-termux (latest)
-```
-
-Features of the npm build
-
-- ARM64/Android bundle included
-- Termux clipboard patch (`PREFIX` -> `TERMUX__PREFIX`)
-- PTY prebuild via `@mmmbuto/node-pty-android-arm64` (no NDK required)
-
-## Build from source (Termux fork)
-
-```bash
-git clone https://github.com/DioNanos/gemini-cli-termux.git
-cd gemini-cli-termux
-npm install
-npm run build && npm run bundle
-node bundle/gemini.js --version
-```
-
-## Known issues
-
-1. If the PTY prebuild fails to load, the CLI falls back to `child_process`
-   (non-interactive).
-2. Node punycode warning is harmless; optional:
-   `node --no-deprecation bundle/gemini.js`.
-
-## Limitations
-
-- PTY support depends on the `@mmmbuto/node-pty-android-arm64` prebuild
-- No secure keychain → credentials stored in plain config files
-- Bash parsing simplified (no tree-sitter)
-
-## Update
-
-- npm: `npm install -g @mmmbuto/gemini-cli-termux@latest`
-- source: `git pull && npm install && npm run build && npm run bundle`
-
-## Termux-API Support (Optional)
-
-Enable access to Android hardware and APIs:
-
-1. Install Termux-API package:
-
-   ```bash
-   pkg install termux-api jq
-   ```
-
-2. Install Termux:API app from F-Droid
-
-3. Setup tool discovery:
-
-   ```bash
-   # Copy scripts to config
-   mkdir -p ~/.config/gemini/termux-tools
-   cp scripts/termux-tools/*.sh ~/.config/gemini/termux-tools/
-   chmod +x ~/.config/gemini/termux-tools/*.sh
-
-   # Configure in settings.json
-   cat > ~/.config/gemini/settings.json << 'EOF'
-   {
-     "tool_discovery_command": "bash ~/.config/gemini/termux-tools/discovery.sh",
-     "tool_call_command": "bash ~/.config/gemini/termux-tools/call.sh"
-   }
-   EOF
-   ```
-
-4. Test:
-   ```bash
-   gemini "What's my battery status?"
-   ```
-
-See [docs/termux-api/](./docs/termux-api/) for complete documentation.
-
-## Report Termux issues
-
-Use the fork issues: https://github.com/DioNanos/gemini-cli-termux/issues
-
-Sunset: will deprecate when upstream adds native Termux support.

package/bundle/docs/architecture.md

@@ -1,80 +0,0 @@
-# Gemini CLI Architecture Overview
-
-This document provides a high-level overview of the Gemini CLI's architecture.
-
-## Core components
-
-The Gemini CLI is primarily composed of two main packages, along with a suite of
-tools that can be used by the system in the course of handling command-line
-input:
-
-1.  **CLI package (`packages/cli`):**
-    - **Purpose:** This contains the user-facing portion of the Gemini CLI, such
-      as handling the initial user input, presenting the final output, and
-      managing the overall user experience.
-    - **Key functions contained in the package:**
-      - [Input processing](/docs/cli/commands)
-      - History management
-      - Display rendering
-      - [Theme and UI customization](/docs/cli/themes)
-      - [CLI configuration settings](/docs/get-started/configuration)
-
-2.  **Core package (`packages/core`):**
-    - **Purpose:** This acts as the backend for the Gemini CLI. It receives
-      requests sent from `packages/cli`, orchestrates interactions with the
-      Gemini API, and manages the execution of available tools.
-    - **Key functions contained in the package:**
-      - API client for communicating with the Google Gemini API
-      - Prompt construction and management
-      - Tool registration and execution logic
-      - State management for conversations or sessions
-      - Server-side configuration
-
-3.  **Tools (`packages/core/src/tools/`):**
-    - **Purpose:** These are individual modules that extend the capabilities of
-      the Gemini model, allowing it to interact with the local environment
-      (e.g., file system, shell commands, web fetching).
-    - **Interaction:** `packages/core` invokes these tools based on requests
-      from the Gemini model.
-
-## Interaction flow
-
-A typical interaction with the Gemini CLI follows this flow:
-
-1.  **User input:** The user types a prompt or command into the terminal, which
-    is managed by `packages/cli`.
-2.  **Request to core:** `packages/cli` sends the user's input to
-    `packages/core`.
-3.  **Request processed:** The core package:
-    - Constructs an appropriate prompt for the Gemini API, possibly including
-      conversation history and available tool definitions.
-    - Sends the prompt to the Gemini API.
-4.  **Gemini API response:** The Gemini API processes the prompt and returns a
-    response. This response might be a direct answer or a request to use one of
-    the available tools.
-5.  **Tool execution (if applicable):**
-    - When the Gemini API requests a tool, the core package prepares to execute
-      it.
-    - If the requested tool can modify the file system or execute shell
-      commands, the user is first given details of the tool and its arguments,
-      and the user must approve the execution.
-    - Read-only operations, such as reading files, might not require explicit
-      user confirmation to proceed.
-    - Once confirmed, or if confirmation is not required, the core package
-      executes the relevant action within the relevant tool, and the result is
-      sent back to the Gemini API by the core package.
-    - The Gemini API processes the tool result and generates a final response.
-6.  **Response to CLI:** The core package sends the final response back to the
-    CLI package.
-7.  **Display to user:** The CLI package formats and displays the response to
-    the user in the terminal.
-
-## Key design principles
-
-- **Modularity:** Separating the CLI (frontend) from the Core (backend) allows
-  for independent development and potential future extensions (e.g., different
-  frontends for the same backend).
-- **Extensibility:** The tool system is designed to be extensible, allowing new
-  capabilities to be added.
-- **User experience:** The CLI focuses on providing a rich and interactive
-  terminal experience.

package/bundle/docs/cli/authentication.md

@@ -1,3 +0,0 @@
-# Authentication setup
-
-See: [Getting Started - Authentication Setup](../get-started/authentication.md).