aigency 0.0.1rc15474277__tar.gz → 0.0.1rc163779164__tar.gz

aigency-0.0.1rc163779164/PKG-INFO

@@ -0,0 +1,267 @@
+Metadata-Version: 2.4
+Name: aigency
+Version: 0.0.1rc163779164
+Summary: Add your description here
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+Requires-Dist: google-adk>=1.11.0
+Requires-Dist: a2a-sdk==0.3.0
+Requires-Dist: litellm<1.73.0,>=1.72.6
+Requires-Dist: pyyaml==6.0.2
+Requires-Dist: PyJWT==2.10.1
+
+# aigency-lib
+
+A library for creating and managing AI agents.
+
+## Quick Start
+
+To test a simple agent:
+
+```bash
+cd examples/simple_agents/hello_world_agent
+docker compose up
+```
+
+## 🔧 Version Management
+
+This project includes an automated system for managing versions in both development and production.
+
+### Version Manager
+
+The `scripts/version_manager.py` script helps you manage your package versions locally.
+
+#### Available Commands
+
+##### 1. View current information
+```bash
+python scripts/version_manager.py show
+```
+**What it does:**
+- Shows the current version in `pyproject.toml`
+- Shows the current git branch
+- Shows the current commit
+- If you're not on `main`, suggests a development version
+
+**Example output:**
+```
+Current version: 0.0.1
+Branch: feature/new-agent
+Commit: a1b2c3d
+Suggested dev version: 0.0.1.dev20250409143022+feature/new-agent.a1b2c3d
+```
+
+##### 2. Create development version
+```bash
+python scripts/version_manager.py dev
+```
+**What it does:**
+- Takes the current version and creates a development version
+- Format: `version.devYYYYMMDDHHMMSS+branch.commit`
+- Automatically updates the `pyproject.toml`
+
+**Example:**
+```bash
+# If you're on branch "feature/auth" with commit "abc123"
+python scripts/version_manager.py dev
+# Result: 0.0.1.dev20250409143022
+```
+
+##### 3. Set specific version
+```bash
+python scripts/version_manager.py set --version "0.1.0"
+```
+**What it does:**
+- Changes the version to the one you specify
+- Useful for releases or to fix versions
+
+**Examples:**
+```bash
+# Release version
+python scripts/version_manager.py set --version "1.0.0"
+
+# Beta version
+python scripts/version_manager.py set --version "1.0.0b1"
+
+# Alpha version
+python scripts/version_manager.py set --version "1.0.0a1"
+```
+
+##### 4. Create Release Candidate version
+```bash
+python scripts/version_manager.py rc --version "1.0.1"
+```
+**What it does:**
+- Creates an RC version with the format `version-rc<commit>`
+- Useful for preparing releases on `release/*` branches
+
+##### 5. Validate current version
+```bash
+python scripts/version_manager.py validate
+```
+**What it does:**
+- Validates that the current version is appropriate for the branch
+- Verifies semantic format on `main` and `release/*` branches
+
+##### 6. Create dev with custom base version
+```bash
+python scripts/version_manager.py dev --base-version "0.2.0"
+```
+**What it does:**
+- Uses a different base version than the current one
+- Useful when you want to prepare a dev version for the next release
+
+### 🚀 Recommended Workflow
+
+#### For daily development:
+```bash
+# 1. View current status
+python scripts/version_manager.py show
+
+# 2. If you're on a feature branch, create dev version
+python scripts/version_manager.py dev
+
+# 3. Make your changes and commits
+git add .
+git commit -m "feat: new functionality"
+
+# 4. If you need to update the dev version (optional)
+python scripts/version_manager.py dev
+```
+
+#### For releases:
+```bash
+# 1. On main branch, set release version
+python scripts/version_manager.py set --version "1.0.0"
+
+# 2. Commit the version
+git add pyproject.toml
+git commit -m "bump: version 1.0.0"
+
+# 3. Use GitHub workflow to publish
+```
+
+#### For testing:
+```bash
+# Create specific test version
+python scripts/version_manager.py set --version "1.0.0rc1"
+```
+
+### ⚠️ PyPI Limitations
+
+PyPI doesn't allow "local versions" (versions with `+` and local identifiers). That's why we've adapted the format:
+
+- ❌ Not allowed: `1.0.0.dev20250409+feature.abc123`
+- ✅ Allowed: `1.0.0.dev20250409`
+
+**Solution for Release Candidates:**
+- We convert the commit hash (hexadecimal) to decimal
+- Example: commit `abc123` → `11256099` → version `1.0.1rc11256099`
+- This maintains commit uniqueness in a PyPI-compatible format
+
+**Result:**
+- Dev versions include unique timestamp
+- RC versions include commit hash (in decimal)
+- We maintain traceability without using local versions
+
+### 📋 Practical Use Cases
+
+**Scenario 1: Working on a feature**
+```bash
+git checkout -b feature/new-auth
+python scripts/version_manager.py dev
+# Now you have: 0.0.1.dev20250409143022
+```
+
+**Scenario 2: Preparing release**
+```bash
+git checkout main
+python scripts/version_manager.py set --version "1.0.0"
+git add pyproject.toml
+git commit -m "release: v1.0.0"
+```
+
+**Scenario 3: Preparing Release Candidate**
+```bash
+git checkout -b release/1.0.1
+python scripts/version_manager.py rc --version "1.0.1"
+# Result: 1.0.1rc12345678 (where 12345678 is the commit hash in decimal)
+```
+
+**Scenario 4: Urgent hotfix**
+```bash
+git checkout -b hotfix/critical-bug
+python scripts/version_manager.py dev --base-version "1.0.1"
+# Result: 1.0.1.dev20250409143022
+```
+
+## 🔄 Intelligent CI/CD Workflow
+
+The project includes a single intelligent workflow (`python-publish.yml`) that automatically handles different version types based on the branch:
+
+### Automatic behavior by branch:
+
+#### 🚀 `main` Branch - Production Versions
+- **Trigger**: Push to `main` or manual execution
+- **Version**: Uses exactly the version from `pyproject.toml`
+- **Validations**:
+  - ✅ Verifies it's a valid semantic version (e.g.: `1.0.0`)
+  - ✅ Verifies it doesn't already exist on PyPI
+  - ❌ Fails if it contains development suffixes (`dev`, `rc`, `alpha`, `beta`)
+- **Target**: PyPI production
+
+#### 🎯 `release/*` Branches - Release Candidates
+- **Trigger**: Push to `release/X.Y.Z` branch or manual execution
+- **Version**: `X.Y.ZrcN` where N is the commit hash in decimal (e.g.: `1.0.1rc12345678`)
+- **Validations**:
+  - ✅ Verifies that `X.Y.Z` is a valid semantic version
+  - ✅ Extracts version from branch name
+  - ✅ Uses commit hash as unique identifier
+  - ✅ PyPI-compatible format
+- **Target**: PyPI production
+- **Example**: Branch `release/1.0.1` + commit `abc123` → Version `1.0.1rc11256099`
+
+#### 🔧 Other Branches - Development Versions
+- **Trigger**: Push to any other branch or manual execution
+- **Version**: `current.devYYYYMMDDHHMMSS` (e.g.: `0.0.1.dev20250409143022`)
+- **Target**: PyPI production
+- **Note**: No local versions for PyPI compatibility
+
+### Recommended workflow:
+
+```bash
+# 1. Development on feature branch
+git checkout -b feature/new-functionality
+# Automatic version: 0.0.1.dev20250409143022+feature-new-functionality.abc123
+
+# 2. Prepare release
+git checkout -b release/1.0.0
+git push origin release/1.0.0
+# Automatic version: 1.0.0rc12345678
+
+# 3. Final release
+git checkout main
+python scripts/version_manager.py set --version "1.0.0"
+git add pyproject.toml
+git commit -m "release: v1.0.0"
+git push origin main
+# Version: 1.0.0 (with validations)
+```
+
+## 📦 Installation
+
+```bash
+pip install aigency
+```
+
+## 🛠️ Development
+
+1. Clone the repository
+2. Install development dependencies
+3. Use the version manager to manage versions during development
+
+```bash
+git clone <repo-url>
+cd aigency-lib
+pip install -e .
+```

aigency-0.0.1rc163779164/README.md

@@ -0,0 +1,255 @@
+# aigency-lib
+
+A library for creating and managing AI agents.
+
+## Quick Start
+
+To test a simple agent:
+
+```bash
+cd examples/simple_agents/hello_world_agent
+docker compose up
+```
+
+## 🔧 Version Management
+
+This project includes an automated system for managing versions in both development and production.
+
+### Version Manager
+
+The `scripts/version_manager.py` script helps you manage your package versions locally.
+
+#### Available Commands
+
+##### 1. View current information
+```bash
+python scripts/version_manager.py show
+```
+**What it does:**
+- Shows the current version in `pyproject.toml`
+- Shows the current git branch
+- Shows the current commit
+- If you're not on `main`, suggests a development version
+
+**Example output:**
+```
+Current version: 0.0.1
+Branch: feature/new-agent
+Commit: a1b2c3d
+Suggested dev version: 0.0.1.dev20250409143022+feature/new-agent.a1b2c3d
+```
+
+##### 2. Create development version
+```bash
+python scripts/version_manager.py dev
+```
+**What it does:**
+- Takes the current version and creates a development version
+- Format: `version.devYYYYMMDDHHMMSS+branch.commit`
+- Automatically updates the `pyproject.toml`
+
+**Example:**
+```bash
+# If you're on branch "feature/auth" with commit "abc123"
+python scripts/version_manager.py dev
+# Result: 0.0.1.dev20250409143022
+```
+
+##### 3. Set specific version
+```bash
+python scripts/version_manager.py set --version "0.1.0"
+```
+**What it does:**
+- Changes the version to the one you specify
+- Useful for releases or to fix versions
+
+**Examples:**
+```bash
+# Release version
+python scripts/version_manager.py set --version "1.0.0"
+
+# Beta version
+python scripts/version_manager.py set --version "1.0.0b1"
+
+# Alpha version
+python scripts/version_manager.py set --version "1.0.0a1"
+```
+
+##### 4. Create Release Candidate version
+```bash
+python scripts/version_manager.py rc --version "1.0.1"
+```
+**What it does:**
+- Creates an RC version with the format `version-rc<commit>`
+- Useful for preparing releases on `release/*` branches
+
+##### 5. Validate current version
+```bash
+python scripts/version_manager.py validate
+```
+**What it does:**
+- Validates that the current version is appropriate for the branch
+- Verifies semantic format on `main` and `release/*` branches
+
+##### 6. Create dev with custom base version
+```bash
+python scripts/version_manager.py dev --base-version "0.2.0"
+```
+**What it does:**
+- Uses a different base version than the current one
+- Useful when you want to prepare a dev version for the next release
+
+### 🚀 Recommended Workflow
+
+#### For daily development:
+```bash
+# 1. View current status
+python scripts/version_manager.py show
+
+# 2. If you're on a feature branch, create dev version
+python scripts/version_manager.py dev
+
+# 3. Make your changes and commits
+git add .
+git commit -m "feat: new functionality"
+
+# 4. If you need to update the dev version (optional)
+python scripts/version_manager.py dev
+```
+
+#### For releases:
+```bash
+# 1. On main branch, set release version
+python scripts/version_manager.py set --version "1.0.0"
+
+# 2. Commit the version
+git add pyproject.toml
+git commit -m "bump: version 1.0.0"
+
+# 3. Use GitHub workflow to publish
+```
+
+#### For testing:
+```bash
+# Create specific test version
+python scripts/version_manager.py set --version "1.0.0rc1"
+```
+
+### ⚠️ PyPI Limitations
+
+PyPI doesn't allow "local versions" (versions with `+` and local identifiers). That's why we've adapted the format:
+
+- ❌ Not allowed: `1.0.0.dev20250409+feature.abc123`
+- ✅ Allowed: `1.0.0.dev20250409`
+
+**Solution for Release Candidates:**
+- We convert the commit hash (hexadecimal) to decimal
+- Example: commit `abc123` → `11256099` → version `1.0.1rc11256099`
+- This maintains commit uniqueness in a PyPI-compatible format
+
+**Result:**
+- Dev versions include unique timestamp
+- RC versions include commit hash (in decimal)
+- We maintain traceability without using local versions
+
+### 📋 Practical Use Cases
+
+**Scenario 1: Working on a feature**
+```bash
+git checkout -b feature/new-auth
+python scripts/version_manager.py dev
+# Now you have: 0.0.1.dev20250409143022
+```
+
+**Scenario 2: Preparing release**
+```bash
+git checkout main
+python scripts/version_manager.py set --version "1.0.0"
+git add pyproject.toml
+git commit -m "release: v1.0.0"
+```
+
+**Scenario 3: Preparing Release Candidate**
+```bash
+git checkout -b release/1.0.1
+python scripts/version_manager.py rc --version "1.0.1"
+# Result: 1.0.1rc12345678 (where 12345678 is the commit hash in decimal)
+```
+
+**Scenario 4: Urgent hotfix**
+```bash
+git checkout -b hotfix/critical-bug
+python scripts/version_manager.py dev --base-version "1.0.1"
+# Result: 1.0.1.dev20250409143022
+```
+
+## 🔄 Intelligent CI/CD Workflow
+
+The project includes a single intelligent workflow (`python-publish.yml`) that automatically handles different version types based on the branch:
+
+### Automatic behavior by branch:
+
+#### 🚀 `main` Branch - Production Versions
+- **Trigger**: Push to `main` or manual execution
+- **Version**: Uses exactly the version from `pyproject.toml`
+- **Validations**:
+  - ✅ Verifies it's a valid semantic version (e.g.: `1.0.0`)
+  - ✅ Verifies it doesn't already exist on PyPI
+  - ❌ Fails if it contains development suffixes (`dev`, `rc`, `alpha`, `beta`)
+- **Target**: PyPI production
+
+#### 🎯 `release/*` Branches - Release Candidates
+- **Trigger**: Push to `release/X.Y.Z` branch or manual execution
+- **Version**: `X.Y.ZrcN` where N is the commit hash in decimal (e.g.: `1.0.1rc12345678`)
+- **Validations**:
+  - ✅ Verifies that `X.Y.Z` is a valid semantic version
+  - ✅ Extracts version from branch name
+  - ✅ Uses commit hash as unique identifier
+  - ✅ PyPI-compatible format
+- **Target**: PyPI production
+- **Example**: Branch `release/1.0.1` + commit `abc123` → Version `1.0.1rc11256099`
+
+#### 🔧 Other Branches - Development Versions
+- **Trigger**: Push to any other branch or manual execution
+- **Version**: `current.devYYYYMMDDHHMMSS` (e.g.: `0.0.1.dev20250409143022`)
+- **Target**: PyPI production
+- **Note**: No local versions for PyPI compatibility
+
+### Recommended workflow:
+
+```bash
+# 1. Development on feature branch
+git checkout -b feature/new-functionality
+# Automatic version: 0.0.1.dev20250409143022+feature-new-functionality.abc123
+
+# 2. Prepare release
+git checkout -b release/1.0.0
+git push origin release/1.0.0
+# Automatic version: 1.0.0rc12345678
+
+# 3. Final release
+git checkout main
+python scripts/version_manager.py set --version "1.0.0"
+git add pyproject.toml
+git commit -m "release: v1.0.0"
+git push origin main
+# Version: 1.0.0 (with validations)
+```
+
+## 📦 Installation
+
+```bash
+pip install aigency
+```
+
+## 🛠️ Development
+
+1. Clone the repository
+2. Install development dependencies
+3. Use the version manager to manage versions during development
+
+```bash
+git clone <repo-url>
+cd aigency-lib
+pip install -e .
+```

aigency-0.0.1rc163779164/aigency/agents/client.py

@@ -0,0 +1,59 @@
+import httpx
+ 
+from a2a.client.client import ClientConfig
+from a2a.client.client_factory import ClientFactory
+from a2a.types import AgentCard, Message, SendMessageResponse
+#TODO: Enable when auth is implemented
+#from a2a.client.auth.interceptor import AuthInterceptor
+
+
+class AgentClient:
+    """A class to hold the connections to the remote agents.
+
+    This class manages connections to remote agents using the A2A protocol.
+    It provides methods for retrieving agent information and sending messages
+    to remote agents.
+
+    Attributes:
+        _httpx_client (httpx.AsyncClient): The HTTP client used for asynchronous requests.
+        agent_card (AgentCard): The agent card containing metadata about the remote agent.
+    """
+
+    def __init__(self, agent_card: AgentCard):
+        """Initialize a connection to a remote agent.
+
+        Args:
+            agent_card (AgentCard): The agent card containing metadata about the remote agent.
+
+        Raises:
+            None
+
+        Returns:
+            None
+        """
+        self._httpx_client = httpx.AsyncClient(timeout=60)
+        self.card = agent_card
+
+        config = ClientConfig(httpx_client=self._httpx_client)
+        factory = ClientFactory(config=config)
+        self.agent_client = factory.create(agent_card)
+
+    def get_agent(self) -> AgentCard:
+        """Get the agent card for this remote agent connection.
+
+        Returns:
+            AgentCard: The agent card containing metadata about the remote agent.
+        """
+        return self.card
+
+    async def send_message(self, message_request: Message) -> SendMessageResponse:
+        """Send a message to the remote agent.
+
+        Args:
+            message_request (Message): The message request to send to the remote agent.
+
+        Returns:
+            SendMessageResponse: The response from the remote agent.
+        """
+        async for response in self.agent_client.send_message(message_request):
+            yield response

aigency-0.0.1rc163779164/aigency/agents/communicator.py

@@ -0,0 +1,107 @@
+import logging
+import uuid
+from typing import Any
+from a2a.types import Message, Task
+from google.adk.tools.tool_context import ToolContext
+
+logging.basicConfig(level=logging.INFO)
+logger = logging.getLogger(__name__)
+
+
+class Communicator:
+    """Base class for Agent-to-Agent communication."""
+
+    def __init__(self, remote_agent_connections=None):
+        self.remote_agent_connections = remote_agent_connections
+
+    async def send_message(self, agent_name: str, task: str, tool_context: ToolContext):
+        """Delegate a task to a specified remote agent.
+
+        This method sends a message to a remote agent, requesting it to perform a task.
+        It handles the creation of the message payload and manages the communication
+        with the remote agent.
+
+        Args:
+            agent_name: Name of the remote agent to send the task to.
+            task: Detailed description of the task for the remote agent to perform.
+            tool_context: Context object containing state and other information.
+
+        Returns:
+            Task object if successful, None otherwise.
+
+        Raises:
+            ValueError: If the specified agent is not found in the available connections.
+        """
+        logger.info(
+            f"`send_message` triggered with agent_name: {agent_name}, task: {task}"
+        )
+        if agent_name not in self.remote_agent_connections:
+            logger.error(
+                f"LLM tried to call '{agent_name}' but it was not found. "
+                f"Available agents: {list(self.remote_agent_connections.keys())}"
+            )
+            raise ValueError(f"Agent '{agent_name}' not found.")
+
+        state = tool_context.state
+        client = self.remote_agent_connections[agent_name]
+
+        if "remote_agent_contexts" not in state:
+            state["remote_agent_contexts"] = {}
+
+        if agent_name not in state["remote_agent_contexts"]:
+            logger.debug(f"Creating new context for agent: {agent_name}")
+            state["remote_agent_contexts"][agent_name] = {
+                "context_id": str(uuid.uuid4())
+            }
+        context_id = state["remote_agent_contexts"][agent_name]["context_id"]
+        task_id = state.get("task_id", None)
+        message_id = state.get("input_message_metadata", {}).get(
+            "message_id", str(uuid.uuid4())
+        )
+
+        payload = self.create_send_message_payload(task, task_id, context_id)
+        payload["message"]["message_id"] = message_id
+        logger.debug("`send_message` triggered with payload: %s", payload)
+
+        send_response = None
+        async for resp in client.send_message(
+            message_request=Message(**payload.get("message"))
+        ):
+            send_response = resp
+
+        if isinstance(send_response, tuple):
+            send_response, _ = send_response
+
+        if not isinstance(send_response, Task):
+            return None
+        return send_response
+
+    @staticmethod
+    def create_send_message_payload(
+        text: str,
+        task_id: str | None = None,
+        context_id: str | None = None,
+    ) -> dict[str, Any]:
+        """Create a message payload for sending to a remote agent.
+
+        Args:
+            text: The text content of the message.
+            task_id: Optional task ID to associate with the message.
+            context_id: Optional context ID to associate with the message.
+
+        Returns:
+            dict: A dictionary containing the formatted message payload ready
+                to be sent to a remote agent.
+        """
+        payload: dict[str, Any] = {
+            "message": {
+                "role": "user",
+                "parts": [{"type": "text", "text": text}],
+                "message_id": uuid.uuid4().hex,
+            },
+        }
+        if task_id:
+            payload["message"]["task_id"] = task_id
+        if context_id:
+            payload["message"]["context_id"] = context_id
+        return payload