feat: Enhance VTCode distribution setup and publishing workflows

- Updated Cargo.toml with metadata including authors, description, license, and keywords.
- Added GitHub Actions workflows for building and releasing binaries across multiple platforms.
- Created a workflow for publishing the crate to crates.io upon release.
- Documented the distribution setup process in DISTRIBUTION_SETUP.md and DISTRIBUTION_SETUP_GUIDE.md.
- Implemented Homebrew formula for VTCode with placeholders for SHA256 checksums.
- Developed npm package structure with installation scripts for binary downloads.
- Added scripts for setting up and testing the distribution configuration.

Author: vinhnx

.github/workflows/build-release.yml

@@ -0,0 +1,62 @@
+name: Build and Release Binaries
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    strategy:
+      matrix:
+        include:
+          - os: ubuntu-latest
+            target: x86_64-unknown-linux-gnu
+            name: linux-x64
+          - os: macos-latest
+            target: x86_64-apple-darwin
+            name: macos-x64
+          - os: macos-latest
+            target: aarch64-apple-darwin
+            name: macos-arm64
+          - os: windows-latest
+            target: x86_64-pc-windows-msvc
+            name: windows-x64
+
+    runs-on: ${{ matrix.os }}
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Rust
+        uses: dtolnay/rust-toolchain@stable
+        with:
+          targets: ${{ matrix.target }}
+
+      - name: Cache dependencies
+        uses: Swatinem/rust-cache@v2
+
+      - name: Build release binary
+        run: cargo build --release --target ${{ matrix.target }}
+
+      - name: Package binary (Unix)
+        if: matrix.os != 'windows-latest'
+        run: |
+          cd target/${{ matrix.target }}/release
+          tar -czf ../../../vtcode-v${{ github.event.release.tag_name }}-x86_64-${{ matrix.name }}.tar.gz vtcode
+
+      - name: Package binary (Windows)
+        if: matrix.os == 'windows-latest'
+        run: |
+          cd target/${{ matrix.target }}/release
+          7z a ../../../vtcode-v${{ github.event.release.tag_name }}-x86_64-${{ matrix.name }}.zip vtcode.exe
+
+      - name: Upload binary
+        uses: actions/upload-release-asset@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          upload_url: ${{ github.event.release.upload_url }}
+          asset_path: ./vtcode-v${{ github.event.release.tag_name }}-${{ matrix.name }}.${{ matrix.os == 'windows-latest' && 'zip' || 'tar.gz' }}
+          asset_name: vtcode-v${{ github.event.release.tag_name }}-${{ matrix.name }}.${{ matrix.os == 'windows-latest' && 'zip' || 'tar.gz' }}
+          asset_content_type: application/${{ matrix.os == 'windows-latest' && 'zip' || 'gzip' }}

.github/workflows/publish-crates.yml

@@ -0,0 +1,42 @@
+name: Publish to Crates.io
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Rust
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Cache dependencies
+        uses: Swatinem/rust-cache@v2
+
+      - name: Verify Cargo authentication
+        run: |
+          if [ -z "$CRATES_IO_TOKEN" ]; then
+            echo "CRATES_IO_TOKEN secret is not set"
+            echo "Please set up the CRATES_IO_TOKEN secret in your repository settings"
+            echo "Get your token from: https://crates.io/me"
+            exit 1
+          fi
+        env:
+          CRATES_IO_TOKEN: ${{ secrets.CRATES_IO_TOKEN }}
+
+      - name: Publish vtcode-core
+        run: cargo publish --manifest-path vtcode-core/Cargo.toml --token "$CRATES_IO_TOKEN"
+        env:
+          CRATES_IO_TOKEN: ${{ secrets.CRATES_IO_TOKEN }}
+
+      - name: Wait for vtcode-core to be available
+        run: sleep 30
+
+      - name: Publish vtcode
+        run: cargo publish --token "$CRATES_IO_TOKEN"
+        env:
+          CRATES_IO_TOKEN: ${{ secrets.CRATES_IO_TOKEN }}

Cargo.toml

@@ -2,6 +2,32 @@
 name = "vtcode"
 version = "0.8.0"
 edition = "2024"
+authors = ["vinhnx <vinhnx@users.noreply.github.com>"]
+description = "A Rust-based terminal coding agent with modular architecture supporting multiple LLM providers"
+license = "MIT"
+readme = "README.md"
+homepage = "https://github.com/vinhnx/vtcode"
+repository = "https://github.com/vinhnx/vtcode"
+keywords = [
+    "ai",
+    "coding",
+    "agent",
+    "llm",
+    "cli",
+    "terminal",
+    "rust",
+    "automation",
+]
+categories = ["command-line-utilities", "development-tools", "api-bindings"]
+exclude = [
+    "target/",
+    ".github/",
+    "docs/",
+    "scripts/",
+    "screenshots/",
+    "logs/",
+    "prompts/",
+]
 default-run = "vtcode"
 
 [workspace]

README.md

@@ -39,15 +39,45 @@ VTCode is a Rust-based terminal coding agent with modular architecture supportin
 
 ### Prerequisites
 
+**For pre-built installations (Cargo, Homebrew, npm):** None - binaries are ready to use.
+
+**For building from source:**
+
 -   Rust 1.75+ (stable)
--   API key for your preferred LLM provider:
-    -   `GEMINI_API_KEY` or `GOOGLE_API_KEY` for Gemini
-    -   `OPENAI_API_KEY` for OpenAI
-    -   `ANTHROPIC_API_KEY` for Anthropic
-    -   `DEEPSEEK_API_KEY` for DeepSeek
+
+**API Keys (required for all installation methods):**
+
+-   `GEMINI_API_KEY` or `GOOGLE_API_KEY` for Gemini
+-   `OPENAI_API_KEY` for OpenAI
+-   `ANTHROPIC_API_KEY` for Anthropic
+-   `DEEPSEEK_API_KEY` for DeepSeek
 
 ### Installation
 
+#### Option 1: Cargo (crates.io) - Recommended for Rust developers
+
+```bash
+cargo install vtcode
+```
+
+#### Option 2: Homebrew (macOS)
+
+```bash
+brew install vinhnx/tap/vtcode
+```
+
+#### Option 3: npm (Cross-platform)
+
+```bash
+npm install -g vtcode
+```
+
+#### Option 4: Pre-built binaries
+
+Download the latest release from [GitHub Releases](https://github.com/vinhnx/vtcode/releases) for your platform.
+
+#### Option 5: Build from source
+
 ```bash
 # Clone the repository
 git clone https://github.com/vinhnx/vtcode.git
@@ -749,3 +779,51 @@ Example:
 default_policy = "prompt"
 max_tool_loops = 100
 ```
+
+### Distribution & Releases
+
+VTCode supports multiple distribution channels for easy installation:
+
+#### Release Process
+
+The project uses an automated release script that handles publishing to multiple package managers:
+
+```bash
+# Create a patch release (increments 0.1.0 → 0.1.1)
+./scripts/release.sh --patch
+
+# Create a minor release (increments 0.1.0 → 0.2.0)
+./scripts/release.sh --minor
+
+# Create a major release (increments 0.1.0 → 1.0.0)
+./scripts/release.sh --major
+
+# Release a specific version
+./scripts/release.sh 1.0.0
+
+# Dry run to see what would happen
+./scripts/release.sh --patch --dry-run
+
+# Skip certain distribution channels
+./scripts/release.sh --patch --skip-npm --skip-homebrew
+```
+
+#### Distribution Channels
+
+1. **Cargo (crates.io)**: `cargo install vtcode`
+2. **npm**: `npm install -g vtcode`
+3. **Homebrew**: `brew install vinhnx/tap/vtcode`
+4. **GitHub Releases**: Pre-built binaries for all platforms
+
+#### Setup for Distribution
+
+To set up publishing to these channels:
+
+```bash
+# Run the setup script for guidance
+./scripts/setup-distribution.sh
+
+# Follow the prompts to set up authentication for each channel
+```
+
+For detailed setup instructions, see: [Distribution Setup Guide](docs/project/DISTRIBUTION_SETUP_GUIDE.md)

docs/project/DISTRIBUTION_SETUP.md

@@ -0,0 +1,82 @@
+# VTCode Distribution Setup
+
+This document outlines the complete distribution setup for VTCode across multiple package managers and platforms.
+
+## Distribution Channels
+
+### 1. Cargo (crates.io)
+
+-   **Primary Rust package repository**
+-   **Location**: `https://crates.io/crates/vtcode`
+-   **Workflow**: `.github/workflows/publish-crates.yml`
+-   **Metadata**: Added to `Cargo.toml` and `vtcode-core/Cargo.toml`
+
+### 2. Homebrew (macOS)
+
+-   **Formula**: `homebrew/vtcode.rb`
+-   **Installation**: `brew install vinhnx/tap/vtcode`
+-   **Binaries**: Downloaded from GitHub Releases
+
+### 3. npm (Cross-platform)
+
+-   **Package**: `@vinhnx/vtcode` (when published)
+-   **Installation**: `npm install -g vtcode`
+-   **Structure**: `npm/` directory with postinstall script
+
+### 4. GitHub Releases
+
+-   **Binaries**: Pre-built for multiple platforms
+-   **Workflow**: `.github/workflows/build-release.yml`
+-   **Platforms**: Linux x64, macOS x64/ARM64, Windows x64
+
+## File Structure
+
+```
+vtcode/
+├── Cargo.toml                    # Main crate metadata
+├── vtcode-core/
+│   └── Cargo.toml               # Core library metadata
+├── homebrew/
+│   └── vtcode.rb               # Homebrew formula
+├── npm/
+│   ├── package.json            # npm package config
+│   ├── index.js               # Main entry point
+│   ├── bin/
+│   │   └── vtcode            # Executable wrapper
+│   └── scripts/
+│       ├── postinstall.js     # Binary download script
+│       └── preuninstall.js    # Cleanup script
+├── .github/workflows/
+│   ├── publish-crates.yml     # Cargo publishing
+│   ├── build-release.yml      # Binary builds
+│   └── release.yml           # Release creation
+└── scripts/
+    ├── release.sh            # Release management
+    └── test-distribution.sh  # Distribution validation
+```
+
+## Release Process
+
+1. **Create Release**: Use `./scripts/release.sh` to bump version and create git tag
+2. **Build Binaries**: GitHub Actions automatically builds binaries for all platforms
+3. **Publish to Cargo**: Automatically publishes to crates.io
+4. **Manual Steps**:
+    - Publish npm package: `cd npm && npm publish`
+    - Update Homebrew formula with correct SHA256 hashes
+    - Create Homebrew tap if needed
+
+## Validation
+
+Run `./scripts/test-distribution.sh` to validate the entire setup before releasing.
+
+## Secrets Required
+
+-   `CRATES_IO_TOKEN`: For publishing to crates.io
+-   `GITHUB_TOKEN`: Automatically provided by GitHub Actions
+
+## Next Steps
+
+1. Create a test release to validate the pipeline
+2. Set up npm publishing (requires npm account)
+3. Create Homebrew tap repository
+4. Update documentation with final installation URLs