massgen 0.0.3__py3-none-any.whl → 0.1.0__py3-none-any.whl

massgen/configs/tools/filesystem/fs_permissions_test.yaml

@@ -0,0 +1,87 @@
+# Example configuration demonstrating context_paths filesystem access control
+# This config shows how agents can access user-specified files with permission control
+
+agents:
+  # - id: "claude1"
+  #   backend:
+  #     type: "claude"
+  #     model: "claude-sonnet-4-20250514"  # Model name
+  #     cwd: "workspace1"
+
+  # - id: "agent_oss"
+  #   backend:
+  #     type: "chatcompletion"
+  #     model: "openai/gpt-oss-120b"
+  #     base_url: "https://api.groq.com/openai/v1"
+  #     cwd: "workspace1"
+
+  # - id: "claude_code_agent1"
+  #   backend:
+  #     type: "claude_code"
+  #     cwd: "workspace1"  # Working directory for file operations
+
+  # - id: "grok_mini1"
+  #   backend:
+  #     type: "grok"
+  #     model: "grok-code-fast-1"
+  #     cwd: "workspace1"
+
+  # - id: "grok_mini2"
+  #   backend:
+  #     type: "grok"
+  #     model: "grok-code-fast-1"
+  #     cwd: "workspace2"
+
+  - id: "gpt5nano_1"
+    backend:
+      type: "openai"
+      model: "gpt-5"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "low"  # Fast responses for debugging
+      cwd: "workspace1"
+
+  - id: "gpt5nano_2"
+    backend:
+      type: "openai"
+      model: "gpt-5"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "low"  # Fast responses for debugging
+      cwd: "workspace2"
+
+  # - id: "code_analyzer"
+  #   backend:
+  #     type: "gemini"
+  #     model: "gemini-2.5-flash"
+  #     cwd: "analyzer_workspace"
+
+  # - id: "code_modifier"
+  #   backend:
+  #     type: "gemini"
+  #     model: "gemini-2.5-flash"
+  #     cwd: "modifier_workspace"
+
+  # - id: "documentation_writer"
+  #   backend:
+  #     type: "gemini"
+  #     model: "gemini-2.5-flash"
+  #     cwd: "docs_workspace"
+
+orchestrator:
+    snapshot_storage: "snapshots"
+    agent_temporary_workspace: "temp_workspaces"
+    # Context paths applied to all agents - always read-only access during orchestration, write for final agent if specified
+    context_paths:
+      - path: "massgen/configs/resources/v0.0.21-example"
+        permission: "write"
+      # - path: "testing_permissions"
+      #   # permission: "read"
+      #   permission: "write"
+
+# UI Configuration
+ui:
+  type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/filesystem/gemini_gemini_workspace_cleanup.yaml

@@ -0,0 +1,54 @@
+# Example Configuration: Workspace Cleanup with Deletion Tools
+#
+# Use Case: Agents can delete outdated files during iteration to keep workspace clean
+#
+# This demonstrates the delete_file and delete_files_batch tools. The v0.0.26-example
+# directory contains a messy workspace with multiple HTML files and scattered resources.
+# Agents can clean this up by deleting redundant files.
+#
+# Run with:
+#   massgen --config @examples/tools/filesystem/gemini_gemini_workspace_cleanup "Please improve the website to reference Jimi Hendrix then remove the other files and directories that aren't being used"
+
+agents:
+  - id: "agent_a"
+    backend:
+      type: "gemini"
+      model: "gemini-2.5-pro"
+      cwd: "workspace1"
+
+  - id: "agent_b"
+    backend:
+      type: "openai"
+      model: "gpt-5-nano"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "medium"
+        summary: "auto"
+      cwd: "workspace2"
+
+orchestrator:
+  snapshot_storage: "snapshots"
+  agent_temporary_workspace: "temp_workspaces"
+  context_paths:
+    - path: "massgen/configs/resources/v0.0.26-example"
+      permission: "write"
+      # Agents can read the messy directory and delete redundant files
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true
+
+# What happens:
+# 1. Agents analyze the messy directory with multiple HTML files:
+#    - beatles.html
+#    - dylan.html
+#    - index.html
+#    - bob_dylan_website/ subdirectory
+# 2. Agents combine the best elements from existing websites to create improved Jimi Hendrix website
+# 3. Agents use delete_file tool to remove old/redundant files
+# 4. Final workspace contains only one clean website
+#
+# Available deletion tools:
+# - delete_file(path, recursive=False) - Delete single file/directory
+# - delete_files_batch(base_path, include_patterns, exclude_patterns) - Delete multiple files

massgen/configs/tools/filesystem/gemini_gpt5_filesystem_casestudy.yaml

@@ -0,0 +1,30 @@
+# massgen --config @examples/tools/filesystem/gemini_gpt5_filesystem_casestudy "Build a game where users see a diverse set of up-to-date small, static coding puzzles related to common coding bugs. Then, award them points if they can clearly spot the error in the code. Use Vite with a package.json with minimal dependencies."
+# please do `npm install && npm run dev` to run the Vite projects
+agents:
+  - id: "gemini"
+    backend:
+      type: "gemini"
+      model: "gemini-2.5-pro"
+      cwd: "workspace1"  # Working directory for file operations
+      enable_web_search: true
+
+  - id: "gpt-5"
+    backend:
+      type: "openai"
+      model: "gpt-5"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "low"
+        summary: "auto"
+      cwd: "workspace2"  # this is for the desired version
+      enable_web_search: true
+
+orchestrator:
+    snapshot_storage: "snapshots"  # Directory to store workspace snapshots
+    agent_temporary_workspace: "temp_workspaces"  # Directory for temporary agent workspaces
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true
+

massgen/configs/tools/filesystem/gemini_gpt5nano_file_context_path.yaml

@@ -0,0 +1,43 @@
+# Example Configuration: File Context Path
+#
+# Use Case: Give agents access to a specific file without exposing the entire directory
+#
+# This config demonstrates the file context path feature which allows you to provide
+# access to a single file, preventing agents from accessing sibling files in the same directory.
+#
+# Run with:
+#   massgen --config @examples/tools/filesystem/gemini_gpt5nano_file_context_path "Analyze the CSS file and make modern improvements"
+
+agents:
+  - id: "agent_a"
+    backend:
+      type: "gemini"
+      model: "gemini-2.5-flash"
+      cwd: "workspace1"
+
+  - id: "agent_b"
+    backend:
+      type: "openai"
+      model: "gpt-5-nano"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "medium"
+        summary: "auto"
+      cwd: "workspace2"
+
+orchestrator:
+  snapshot_storage: "snapshots"
+  agent_temporary_workspace: "temp_workspaces"
+  context_paths:
+    - path: "massgen/configs/resources/v0.0.21-example/styles.css"
+      permission: "write"
+      # Only styles.css is accessible - index.html in the same directory is NOT accessible
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true
+
+# Result:
+# ✅ massgen/configs/resources/v0.0.21-example/styles.css → Can read/write
+# ❌ massgen/configs/resources/v0.0.21-example/index.html → NOT accessible (sibling file blocked)

massgen/configs/tools/filesystem/gemini_gpt5nano_protected_paths.yaml

@@ -0,0 +1,45 @@
+# Example Configuration: Protected Paths
+#
+# Use Case: Allow agents to modify files but prevent changes to specific reference files
+#
+# This config demonstrates the protected_paths feature which makes specific files/directories
+# within a writable context path immune from modification or deletion.
+#
+# Run with:
+#   massgen --config @examples/tools/filesystem/gemini_gpt5nano_protected_paths "Review the HTML and CSS files, then improve the styling"
+
+agents:
+  - id: "agent_a"
+    backend:
+      type: "gemini"
+      model: "gemini-2.5-flash"
+      cwd: "workspace1"
+
+  - id: "agent_b"
+    backend:
+      type: "openai"
+      model: "gpt-5-nano"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "medium"
+        summary: "auto"
+      cwd: "workspace2"
+
+orchestrator:
+  snapshot_storage: "snapshots"
+  agent_temporary_workspace: "temp_workspaces"
+  context_paths:
+    - path: "massgen/configs/resources/v0.0.21-example"
+      permission: "write"
+      protected_paths:
+        - "index.html"  # This file is read-only (protected)
+        # styles.css remains writable - agents can modify it
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true
+
+# Result:
+# ✅ massgen/configs/resources/v0.0.21-example/styles.css → Can modify/delete
+# ❌ massgen/configs/resources/v0.0.21-example/index.html → Read-only (protected)

massgen/configs/tools/filesystem/gpt5mini_cc_fs_context_path.yaml

@@ -0,0 +1,31 @@
+# Example configuration demonstrating context_paths filesystem access control
+# This config shows how agents can access user-specified files with permission control
+
+agents:
+  - id: "agent_a"
+    backend:
+      type: "openai"
+      model: "gpt-5"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "low"  # Fast responses for debugging
+      cwd: "workspace1"
+
+  - id: "agent_b"
+    backend:
+      type: "claude_code"
+      cwd: "workspace2"
+
+orchestrator:
+    snapshot_storage: "snapshots"
+    agent_temporary_workspace: "temp_workspaces"
+    # Context paths applied to all agents - read-only access during orchestration, write for final agent if specified
+    context_paths:
+      - path: "massgen/configs/resources/v0.0.21-example"
+        permission: "write"
+
+# UI Configuration
+ui:
+  type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/filesystem/grok4_gpt5_gemini_filesystem.yaml

@@ -0,0 +1,32 @@
+# uv tool run massgen --config tools/filesystem/grok4_gpt5_gemini_filesystem.yaml
+agents:
+  - id: "agent_a"
+    backend:
+      type: "grok"
+      model: "grok-4-fast-reasoning"  # "grok-code-fast-1"
+      cwd: "workspace1"
+
+  - id: "agent_b"
+    backend:
+      type: "openai"
+      model: "gpt-5-mini"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "medium"
+        summary: "auto"
+      cwd: "workspace2"
+
+  - id: "agent_c"
+    backend:
+      type: "gemini"
+      model: "gemini-2.5-pro"
+      cwd: "workspace3"
+
+orchestrator:
+    snapshot_storage: "snapshots"  # Directory to store workspace snapshots
+    agent_temporary_workspace: "temp_workspaces"  # Directory for temporary agent workspaces
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/filesystem/multiturn/grok4_gpt5_claude_code_filesystem_multiturn.yaml

@@ -0,0 +1,58 @@
+# Multi-Turn Filesystem Configuration Example
+#
+# This configuration enables agents to build upon previous work across multiple conversation turns.
+#
+# Key Features:
+# - session_storage: Saves conversation history and workspace state between turns
+# - context_paths: Gives agents access to your project files
+#   - Use "." for current directory to work directly in your project
+#   - Files are read-only during coordination, writable by final agent
+#
+# Example usage:
+# massgen --config @examples/tools/filesystem/multiturn_grok4_gpt5_claude_code_filesystem_multiturn
+#
+# Or with uv tool:
+# uv tool run massgen --config tools/filesystem/multiturn/grok4_gpt5_claude_code_filesystem_multiturn.yaml
+
+agents:
+  - id: "agent_a"
+    backend:
+      type: "grok"
+      model: "grok-4-fast-reasoning"  # "grok-code-fast-1"
+      cwd: "workspace1"  # Working directory for file operations
+
+  - id: "agent_b"
+    backend:
+      type: "openai"
+      model: "gpt-5-mini"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "medium"
+        summary: "auto"
+      cwd: "workspace2"  # this is for the desired version
+
+  - id: "agent_c"
+    backend:
+      type: "claude_code"
+      cwd: "workspace3"  # Working directory for file operations
+      model: "claude-sonnet-4-20250514"
+
+orchestrator:
+    snapshot_storage: "snapshots"  # Directory to store workspace snapshots
+    agent_temporary_workspace: "temp_workspaces"  # Directory for temporary agent workspaces
+    session_storage: "sessions"  # Used for multi-turn conversations to store previous rounds
+
+    # Context paths - give agents access to your project files
+    # Tip: Use "." to automatically work in current directory
+    context_paths:
+      - path: "."  # Current directory (where you run massgen)
+        permission: "write"  # Allow final agent to create/modify files
+        # Optional: Add protected_paths to prevent accidental modifications
+        # protected_paths:
+        #   - ".env"
+        #   - "config.json"
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/filesystem/multiturn/grok4_gpt5_gemini_filesystem_multiturn.yaml

@@ -0,0 +1,58 @@
+# Multi-Turn Filesystem Configuration Example
+#
+# This configuration enables agents to build upon previous work across multiple conversation turns.
+#
+# Key Features:
+# - session_storage: Saves conversation history and workspace state between turns
+# - context_paths: Gives agents access to your project files
+#   - Use "." for current directory to work directly in your project
+#   - Files are read-only during coordination, writable by final agent
+#
+# Example usage:
+# massgen --config @examples/tools/filesystem/multiturn_grok4_gpt5_gemini_filesystem_multiturn
+#
+# Or with uv tool:
+# uv tool run massgen --config tools/filesystem/multiturn/grok4_gpt5_gemini_filesystem_multiturn.yaml
+
+agents:
+  - id: "agent_a"
+    backend:
+      type: "grok"
+      model: "grok-4-fast-reasoning"  # "grok-code-fast-1"
+      cwd: "workspace1"
+
+  - id: "agent_b"
+    backend:
+      type: "openai"
+      model: "gpt-5-mini"
+      text:
+        verbosity: "medium"
+      reasoning:
+        effort: "medium"
+        summary: "auto"
+      cwd: "workspace2"
+
+  - id: "agent_c"
+    backend:
+      type: "gemini"
+      model: "gemini-2.5-pro"
+      cwd: "workspace3"
+
+orchestrator:
+    snapshot_storage: "snapshots"  # Directory to store workspace snapshots
+    agent_temporary_workspace: "temp_workspaces"  # Directory for temporary agent workspaces
+    session_storage: "sessions"  # Used for multi-turn conversations to store previous rounds
+
+    # Context paths - give agents access to your project files
+    # Tip: Use "." to automatically work in current directory
+    context_paths:
+      - path: "."  # Current directory (where you run massgen)
+        permission: "write"  # Allow final agent to create/modify files
+        # Optional: Add protected_paths to prevent accidental modifications
+        # protected_paths:
+        #   - ".env"
+        #   - "config.json"
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/filesystem/multiturn/two_claude_code_filesystem_multiturn.yaml

@@ -0,0 +1,47 @@
+# Multi-Turn Filesystem Configuration Example
+#
+# This configuration enables agents to build upon previous work across multiple conversation turns.
+#
+# Key Features:
+# - session_storage: Saves conversation history and workspace state between turns
+# - context_paths: Gives agents access to your project files
+#   - Use "." for current directory to work directly in your project
+#   - Files are read-only during coordination, writable by final agent
+#
+# Example usage:
+# massgen --config @examples/tools/filesystem/multiturn_two_claude_code_filesystem_multiturn
+#
+# Or with uv tool:
+# uv tool run massgen --config tools/filesystem/multiturn/two_claude_code_filesystem_multiturn.yaml
+
+agents:
+  - id: "agent_a"
+    backend:
+      type: "claude_code"
+      cwd: "workspace1"  # Working directory for file operations
+      model: "claude-sonnet-4-20250514"
+
+  - id: "agent_b"
+    backend:
+      type: "claude_code"
+      cwd: "workspace2"  # Working directory for file operations
+      model: "claude-sonnet-4-20250514"
+
+orchestrator:
+    snapshot_storage: "snapshots"  # Directory to store workspace snapshots
+    agent_temporary_workspace: "temp_workspaces"  # Directory for temporary agent workspaces
+    session_storage: "sessions"  # Used for multi-turn conversations to store previous rounds
+
+    # Context paths - give agents access to your project files
+    # Tip: Use "." to automatically work in current directory
+    context_paths:
+      - path: "."  # Current directory (where you run massgen)
+        permission: "write"  # Allow final agent to create/modify files
+        # Optional: Add protected_paths to prevent accidental modifications
+        # protected_paths:
+        #   - ".env"
+        #   - "config.json"
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/filesystem/multiturn/two_gemini_flash_filesystem_multiturn.yaml

@@ -0,0 +1,48 @@
+# Multi-Turn Filesystem Configuration Example
+#
+# This configuration enables agents to build upon previous work across multiple conversation turns.
+#
+# Key Features:
+# - session_storage: Saves conversation history and workspace state between turns
+# - context_paths: Gives agents access to your project files
+#   - Use "." for current directory to work directly in your project
+#   - Files are read-only during coordination, writable by final agent
+#
+# Example usage:
+# massgen --config @examples/tools/filesystem/multiturn_two_gemini_flash_filesystem_multiturn
+#
+# Or with uv tool:
+# uv tool run massgen --config tools/filesystem/multiturn/two_gemini_flash_filesystem_multiturn.yaml
+
+agents:
+  - id: "gemini_a"
+    backend:
+      type: "gemini"
+      model: "gemini-2.5-flash"
+      cwd: "workspace1"  # Working directory for file operations
+
+  - id: "gemini_b"
+    backend:
+      type: "gemini"
+      model: "gemini-2.5-flash"
+      cwd: "workspace2"  # Working directory for file operations
+
+orchestrator:
+    snapshot_storage: "snapshots"  # Directory to store workspace snapshots
+    agent_temporary_workspace: "temp_workspaces"  # Directory for temporary agent workspaces
+    session_storage: "sessions"  # Used for multi-turn conversations to store previous rounds
+
+    # Context paths - give agents access to your project files
+    # Tip: Use "." to automatically work in current directory
+    context_paths:
+      - path: "."  # Current directory (where you run massgen)
+        permission: "write"  # Allow final agent to create/modify files
+        # Optional: Add protected_paths to prevent accidental modifications
+        # protected_paths:
+        #   - ".env"
+        #   - "config.json"
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true
+

massgen/configs/tools/mcp/claude_code_discord_mcp_example.yaml

@@ -0,0 +1,27 @@
+agent:
+  id: "claude_code_discord_mcp"
+  backend:
+    type: "claude_code"
+    cwd: "claude_code_workspace_discord_mcp"
+    permission_mode: "bypassPermissions"
+
+    # Discord MCP server
+    mcp_servers:
+      discord:
+        type: "stdio"
+        command: "npx"
+        args: ["-y", "mcp-discord", "--config", "${DISCORD_BOT_TOKEN}"]
+        env:
+            NOTION_TOKEN: "${NOTION_TOKEN_ONE}"
+
+    allowed_tools:
+      - "Read"
+      - "Write"
+      - "Bash"
+      - "LS"
+      - "WebSearch"
+      # MCP tools will be auto-discovered from the server
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/mcp/claude_code_simple_mcp.yaml

@@ -0,0 +1,35 @@
+agent:
+  id: "claude_code_simple_mcp"
+  backend:
+    type: "claude_code"
+    cwd: "claude_code_simple_mcp_workspace"
+    permission_mode: "bypassPermissions"
+    
+    # Simple MCP server for testing
+    mcp_servers:
+      test:
+        type: "stdio"
+        command: "python3"
+        args: ["../mcp_servers/simple_test_server.py"]
+        
+    allowed_tools:
+      - "Read"
+      - "Write"
+      - "Bash"
+      - "LS"
+      - "WebSearch"
+      # MCP tools auto-discovered
+      
+  system_message: |
+    You are testing MCP integration with Claude Code.
+    
+    You have access to a simple MCP test server with these tools:
+    - mcp__test__echo: Echo back text
+    - mcp__test__add_numbers: Add two numbers
+    - mcp__test__get_current_time: Get current timestamp
+    
+    Please test these MCP tools to verify the integration is working.
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/mcp/claude_code_twitter_mcp_example.yaml

@@ -0,0 +1,32 @@
+agent:
+  id: "claude_code_twitter_mcp"
+  backend:
+    type: "claude_code"
+    cwd: "claude_code_workspace_twitter_mcp"
+    permission_mode: "bypassPermissions"
+    
+    # Twitter MCP server - using EnesCinr/twitter-mcp
+    mcp_servers:
+      twitter:
+        type: "stdio"
+        command: "npx"
+        args: ["-y", "@enescinar/twitter-mcp"]
+        env:
+        # You need to get these from Twitter Developer Portal: https://developer.twitter.com/
+        # Required credentials:
+          API_KEY: "YOUR_API_KEY"
+          API_SECRET_KEY: "YOUR_API_SECRET_KEY"
+          ACCESS_TOKEN: "YOUR_ACCESS_TOKEN"
+          ACCESS_TOKEN_SECRET: "YOUR_ACCESS_TOKEN_SECRET"
+
+    allowed_tools:
+      - "Read"
+      - "Write"
+      - "Bash"
+      - "LS"
+      - "WebSearch"
+      # MCP tools will be auto-discovered from the server
+
+ui:
+  display_type: "rich_terminal"
+  logging_enabled: true

massgen/configs/tools/mcp/claude_mcp_example.yaml

@@ -0,0 +1,24 @@
+# MassGen Configuration: Gemini with MCP Integration
+# Usage:
+#   massgen --config @examples/tools/mcp/claude_mcp_example "whats the weather of Tokyo"
+agents:
+  - id: "claude_mcp_weather"
+    backend:
+      type: "claude"
+      model: "claude-sonnet-4-20250514"  # Model name
+      mcp_servers:
+        - name: "weather"
+          type: "stdio"
+          command: "npx"
+          args: ["-y", "@fak111/weather-mcp"]
+    system_message: |
+      You are an AI assistant with access to weather information through MCP (Model Context Protocol) integration.
+
+      Weather tools are available via MCP sessions and will be called automatically by the system when needed.
+      Do not output tool call syntax or function declarations. Focus on answering the user's question clearly.
+
+      When users ask about weather conditions, forecasts, or alerts, include the location and time frame in your
+      response and provide concise, up-to-date information using the integrated tools.
+ui:
+  display_type: "simple"
+  logging_enabled: true