juno-code 1.0.14 → 1.0.17

package/dist/templates/scripts/kanban.sh

@@ -1,13 +1,147 @@
-#!/bin/bash
+#!/usr/bin/env bash
+
+# kanban.sh
 #
-# Kanban Wrapper Script
+# Purpose: Kanban wrapper with Python environment setup
 #
-# This script ensures juno-kanban always executes from the project root directory,
-# maintaining a single consistent database location regardless of where this script is called from.
+# This script ensures juno-kanban always executes from the project root directory
+# with the proper Python virtual environment activated.
 #
 # Usage: ./.juno_task/scripts/kanban.sh [juno-kanban arguments]
 # Example: ./.juno_task/scripts/kanban.sh list --limit 5
 #
+# Created by: juno-code init command
+# Date: Auto-generated during project initialization
+
+set -euo pipefail  # Exit on error, undefined variable, or pipe failure
+
+# DEBUG OUTPUT: Show that kanban.sh is being executed
+echo "[DEBUG] kanban.sh is being executed from: $(pwd)" >&2
+
+# Color output for better readability
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+# Configuration
+VENV_DIR=".venv_juno"
+SCRIPTS_DIR=".juno_task/scripts"
+INSTALL_SCRIPT="${SCRIPTS_DIR}/install_requirements.sh"
+
+# Logging functions
+log_info() {
+    echo -e "${BLUE}[KANBAN]${NC} $1"
+}
+
+log_success() {
+    echo -e "${GREEN}[KANBAN]${NC} $1"
+}
+
+log_warning() {
+    echo -e "${YELLOW}[KANBAN]${NC} $1"
+}
+
+log_error() {
+    echo -e "${RED}[KANBAN]${NC} $1"
+}
+
+# Function to check if we're inside .venv_juno specifically
+# CRITICAL: Don't just check for ANY venv - check if we're in .venv_juno
+is_in_venv_juno() {
+    # Check if VIRTUAL_ENV is set and points to .venv_juno
+    if [ -n "${VIRTUAL_ENV:-}" ]; then
+        # Check if VIRTUAL_ENV path contains .venv_juno
+        if [[ "${VIRTUAL_ENV:-}" == *"/.venv_juno" ]] || [[ "${VIRTUAL_ENV:-}" == *".venv_juno"* ]]; then
+            return 0  # Inside .venv_juno
+        fi
+
+        # Check if the basename is .venv_juno
+        if [ "$(basename "${VIRTUAL_ENV:-}")" = ".venv_juno" ]; then
+            return 0  # Inside .venv_juno
+        fi
+    fi
+
+    return 1  # Not inside .venv_juno (or not in any venv)
+}
+
+# Function to activate virtual environment
+activate_venv() {
+    local venv_path="$1"
+
+    if [ ! -d "$venv_path" ]; then
+        log_error "Virtual environment not found: $venv_path"
+        return 1
+    fi
+
+    # Activate the venv
+    # shellcheck disable=SC1091
+    if [ -f "$venv_path/bin/activate" ]; then
+        source "$venv_path/bin/activate"
+        log_success "Activated virtual environment: $venv_path"
+        return 0
+    else
+        log_error "Activation script not found: $venv_path/bin/activate"
+        return 1
+    fi
+}
+
+# Function to ensure Python environment is ready
+ensure_python_environment() {
+    log_info "Checking Python environment..."
+
+    # Step 1: Check if we're already in .venv_juno specifically
+    if is_in_venv_juno; then
+        log_success "Already inside .venv_juno virtual environment"
+        return 0
+    fi
+
+    # Step 2: Not in .venv_juno - check if .venv_juno exists in project root
+    if [ -d "$VENV_DIR" ]; then
+        log_info "Found existing virtual environment: $VENV_DIR"
+
+        # Activate the venv
+        if activate_venv "$VENV_DIR"; then
+            return 0
+        else
+            log_error "Failed to activate virtual environment"
+            return 1
+        fi
+    fi
+
+    # Step 3: .venv_juno doesn't exist - need to create it
+    log_warning "Virtual environment not found: $VENV_DIR"
+    log_info "Running install_requirements.sh to create virtual environment..."
+
+    # Check if install_requirements.sh exists
+    if [ ! -f "$INSTALL_SCRIPT" ]; then
+        log_error "Install script not found: $INSTALL_SCRIPT"
+        log_error "Please run 'juno-code init' to initialize the project"
+        return 1
+    fi
+
+    # Make sure the script is executable
+    chmod +x "$INSTALL_SCRIPT"
+
+    # Run the install script
+    if bash "$INSTALL_SCRIPT"; then
+        log_success "Python environment setup completed successfully"
+
+        # After install, activate the venv if it was created
+        if [ -d "$VENV_DIR" ]; then
+            if activate_venv "$VENV_DIR"; then
+                return 0
+            fi
+        fi
+
+        return 0
+    else
+        log_error "Failed to run install_requirements.sh"
+        log_error "Please check the error messages above"
+        return 1
+    fi
+}
 
 # Get the directory where this script is located
 SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
@@ -15,5 +149,25 @@ SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
 # Navigate to project root (parent of scripts directory)
 PROJECT_ROOT="$( cd "$SCRIPT_DIR/../.." && pwd )"
 
-# Change to project root and execute juno-kanban with all passed arguments
-cd "$PROJECT_ROOT" && juno-kanban "$@"
+# Change to project root
+cd "$PROJECT_ROOT"
+
+# Main kanban logic
+main() {
+    log_info "=== juno-kanban Wrapper ==="
+
+    # Ensure Python environment is ready
+    if ! ensure_python_environment; then
+        log_error "Failed to setup Python environment"
+        exit 1
+    fi
+
+    log_success "Python environment ready!"
+
+    # Execute juno-kanban with all passed arguments from project root
+    log_info "Executing juno-kanban: $*"
+    exec juno-kanban "$@"
+}
+
+# Run main function with all arguments
+main "$@"

package/dist/templates/services/README.md

@@ -0,0 +1,271 @@
+# Juno-Code Service Scripts
+
+This directory contains service scripts that extend juno-code functionality. These scripts are Python-based utilities that can be customized by users.
+
+## Installation
+
+Service scripts are automatically installed to `~/.juno_code/services/` when you run:
+
+```bash
+juno-code init
+```
+
+Or you can manually install/manage them:
+
+```bash
+# Install services
+juno-code services install
+
+# List installed services
+juno-code services list
+
+# Check installation status
+juno-code services status
+
+# Show services directory path
+juno-code services path
+
+# Uninstall services
+juno-code services uninstall --yes
+```
+
+## Available Services
+
+### codex.py
+
+A wrapper for OpenAI Codex CLI with configurable options.
+
+#### Features
+
+- Automatic codex installation check
+- Support for inline prompts or prompt files
+- Configurable model selection
+- Auto-instruction prepending
+- Full argument passthrough and override support
+- JSON output support
+- Verbose mode for debugging
+
+#### Usage
+
+```bash
+# Basic usage with inline prompt
+~/.juno_code/services/codex.py -p "Write a hello world function"
+
+# Using a prompt file
+~/.juno_code/services/codex.py -pp /path/to/prompt.txt
+
+# Specify project directory
+~/.juno_code/services/codex.py -p "Add tests" --cd /path/to/project
+
+# Override default model
+~/.juno_code/services/codex.py -p "Refactor code" -m gpt-4-turbo
+
+# Custom auto-instruction
+~/.juno_code/services/codex.py -p "Fix bugs" --auto-instruction "You are a debugging expert"
+
+# Add custom codex config
+~/.juno_code/services/codex.py -p "Write code" -c custom_option=value
+
+# Enable verbose output
+~/.juno_code/services/codex.py -p "Analyze code" --verbose
+
+# JSON output
+~/.juno_code/services/codex.py -p "Generate function" --json
+```
+
+#### Arguments
+
+- `-p, --prompt <text>`: Prompt text to send to codex (required, mutually exclusive with --prompt-file)
+- `-pp, --prompt-file <path>`: Path to file containing the prompt (required, mutually exclusive with --prompt)
+- `--cd <path>`: Project path (absolute path). Default: current directory
+- `-m, --model <name>`: Model name. Default: gpt-4
+- `--auto-instruction <text>`: Auto instruction to prepend to prompt
+- `-c, --config <arg>`: Additional codex config arguments (can be used multiple times)
+- `--json`: Output in JSON format
+- `--verbose`: Enable verbose output
+
+#### Default Configuration
+
+The script comes with these default codex configurations:
+- `include_apply_patch_tool=true`
+- `use_experimental_streamable_shell_tool=true`
+- `sandbox_mode=danger-full-access`
+
+You can override these by providing the same config key with `-c`:
+
+```bash
+# Override sandbox mode
+~/.juno_code/services/codex.py -p "Safe operation" -c sandbox_mode=safe
+```
+
+### claude.py
+
+A wrapper for Anthropic Claude CLI with configurable options.
+
+#### Features
+
+- Automatic claude installation check
+- Support for inline prompts or prompt files
+- Configurable model selection (sonnet, opus, or full model names)
+- Auto-instruction prepending
+- Tool access control
+- Permission mode configuration
+- JSON output support
+- Verbose mode for debugging
+- Conversation continuation support
+
+#### Usage
+
+```bash
+# Basic usage with inline prompt
+~/.juno_code/services/claude.py -p "Write a hello world function"
+
+# Using a prompt file
+~/.juno_code/services/claude.py -pp /path/to/prompt.txt
+
+# Specify project directory
+~/.juno_code/services/claude.py -p "Add tests" --cd /path/to/project
+
+# Override default model
+~/.juno_code/services/claude.py -p "Refactor code" -m claude-opus-4-20250514
+
+# Use model aliases
+~/.juno_code/services/claude.py -p "Fix bugs" -m sonnet
+
+# Custom auto-instruction
+~/.juno_code/services/claude.py -p "Fix bugs" --auto-instruction "You are a debugging expert"
+
+# Specify allowed tools
+~/.juno_code/services/claude.py -p "Write code" --tool Bash --tool Edit --tool Write
+
+# Change permission mode
+~/.juno_code/services/claude.py -p "Review code" --permission-mode plan
+
+# Continue previous conversation
+~/.juno_code/services/claude.py -p "Continue working" --continue
+
+# Enable verbose output
+~/.juno_code/services/claude.py -p "Analyze code" --verbose
+
+# JSON output
+~/.juno_code/services/claude.py -p "Generate function" --json
+```
+
+#### Arguments
+
+- `-p, --prompt <text>`: Prompt text to send to claude (required, mutually exclusive with --prompt-file)
+- `-pp, --prompt-file <path>`: Path to file containing the prompt (required, mutually exclusive with --prompt)
+- `--cd <path>`: Project path (absolute path). Default: current directory
+- `-m, --model <name>`: Model name (e.g. 'sonnet', 'opus', or full name). Default: claude-sonnet-4-20250514
+- `--auto-instruction <text>`: Auto instruction to prepend to prompt
+- `--tool <name>`: Allowed tools (can be used multiple times, e.g. 'Bash' 'Edit')
+- `--permission-mode <mode>`: Permission mode: acceptEdits, bypassPermissions, default, or plan. Default: bypassPermissions
+- `--json`: Output in JSON format
+- `--verbose`: Enable verbose output
+- `-c, --continue`: Continue the most recent conversation
+- `--additional-args <args>`: Additional claude arguments as a space-separated string
+
+#### Default Configuration
+
+The script comes with these default allowed tools:
+- Read, Write, Edit, MultiEdit
+- Bash, Glob, Grep
+- WebFetch, WebSearch
+- TodoWrite
+
+You can override these by providing the `--tool` argument:
+
+```bash
+# Use only specific tools
+~/.juno_code/services/claude.py -p "Safe operation" --tool Read --tool Write
+```
+
+## Customization
+
+All service scripts installed in `~/.juno_code/services/` can be modified to suit your needs. This directory is designed for user customization.
+
+### Adding Custom Services
+
+You can add your own service scripts to `~/.juno_code/services/`:
+
+1. Create a new Python script (e.g., `my-service.py`)
+2. Make it executable: `chmod +x ~/.juno_code/services/my-service.py`
+3. Use it from anywhere: `~/.juno_code/services/my-service.py`
+
+### Service Script Template
+
+Here's a basic template for creating your own service:
+
+```python
+#!/usr/bin/env python3
+"""
+My Custom Service
+Description of what this service does
+"""
+
+import argparse
+import subprocess
+import sys
+
+def main():
+    parser = argparse.ArgumentParser(description="My Custom Service")
+    parser.add_argument('-p', '--prompt', required=True, help='Prompt text')
+    parser.add_argument('--cd', default='.', help='Working directory')
+
+    args = parser.parse_args()
+
+    # Your service logic here
+    print(f"Processing: {args.prompt}")
+
+    return 0
+
+if __name__ == "__main__":
+    sys.exit(main())
+```
+
+## Future Extensions
+
+These service scripts are part of juno-code's extensibility model. In future versions, you'll be able to:
+
+- Use these scripts as alternative backends for juno-code subagents
+- Create custom subagent implementations without MCP server dependency
+- Share and install community-created service scripts
+- Integrate with other AI coding tools and CLIs
+
+## Requirements
+
+Service scripts require Python 3.6+ to be installed on your system. Individual services may have additional requirements:
+
+- **codex.py**: Requires OpenAI Codex CLI to be installed
+- **claude.py**: Requires Anthropic Claude CLI to be installed (see https://docs.anthropic.com/en/docs/agents-and-tools/claude-code)
+
+## Troubleshooting
+
+### Services not found
+
+If services are not installed, run:
+
+```bash
+juno-code services install
+```
+
+### Permission denied
+
+Make sure scripts are executable:
+
+```bash
+chmod +x ~/.juno_code/services/*.py
+```
+
+### Python not found
+
+Ensure Python 3 is installed and available in your PATH:
+
+```bash
+python3 --version
+```
+
+## Support
+
+For issues or feature requests related to service scripts, please visit:
+https://github.com/owner/juno-code/issues