autobyteus 1.2.1__py3-none-any.whl → 1.3.0__py3-none-any.whl

autobyteus/workflow/phases/__init__.py

@@ -1,11 +0,0 @@
-# file: autobyteus/autobyteus/workflow/phases/__init__.py
-"""
-This package contains components for defining and managing workflow operational phases.
-"""
-from autobyteus.workflow.phases.workflow_operational_phase import WorkflowOperationalPhase
-from autobyteus.workflow.phases.workflow_phase_manager import WorkflowPhaseManager
-
-__all__ = [
-    "WorkflowOperationalPhase",
-    "WorkflowPhaseManager",
-]

autobyteus/workflow/phases/workflow_operational_phase.py

@@ -1,19 +0,0 @@
-# file: autobyteus/autobyteus/workflow/phases/workflow_operational_phase.py
-from enum import Enum
-
-class WorkflowOperationalPhase(str, Enum):
-    """Defines the operational phases of an AgenticWorkflow."""
-    UNINITIALIZED = "uninitialized"
-    BOOTSTRAPPING = "bootstrapping"
-    IDLE = "idle"
-    PROCESSING = "processing"
-    SHUTTING_DOWN = "shutting_down"
-    SHUTDOWN_COMPLETE = "shutdown_complete"
-    ERROR = "error"
-
-    def is_terminal(self) -> bool:
-        """Checks if the phase is a terminal state."""
-        return self in [WorkflowOperationalPhase.SHUTDOWN_COMPLETE, WorkflowOperationalPhase.ERROR]
-
-    def __str__(self) -> str:
-        return self.value

autobyteus/workflow/phases/workflow_phase_manager.py

@@ -1,48 +0,0 @@
-# file: autobyteus/autobyteus/workflow/phases/workflow_phase_manager.py
-import logging
-from typing import TYPE_CHECKING, Optional
-
-from autobyteus.workflow.phases.workflow_operational_phase import WorkflowOperationalPhase
-
-if TYPE_CHECKING:
-    from autobyteus.workflow.context.workflow_context import WorkflowContext
-    from autobyteus.workflow.streaming.workflow_event_notifier import WorkflowExternalEventNotifier
-
-logger = logging.getLogger(__name__)
-
-class WorkflowPhaseManager:
-    """Manages the operational phase of a workflow."""
-    def __init__(self, context: 'WorkflowContext', notifier: 'WorkflowExternalEventNotifier'):
-        self.context = context
-        self.notifier = notifier
-        self.context.state.current_phase = WorkflowOperationalPhase.UNINITIALIZED
-        logger.debug(f"WorkflowPhaseManager initialized for workflow '{context.workflow_id}'.")
-
-    async def _transition_phase(self, new_phase: WorkflowOperationalPhase, extra_data: Optional[dict] = None):
-        old_phase = self.context.state.current_phase
-        if old_phase == new_phase:
-            return
-        logger.info(f"Workflow '{self.context.workflow_id}' transitioning from {old_phase.value} to {new_phase.value}.")
-        self.context.state.current_phase = new_phase
-        self.notifier.notify_phase_change(new_phase, old_phase, extra_data)
-
-    async def notify_bootstrapping_started(self):
-        await self._transition_phase(WorkflowOperationalPhase.BOOTSTRAPPING)
-
-    async def notify_initialization_complete(self):
-        await self._transition_phase(WorkflowOperationalPhase.IDLE)
-        
-    async def notify_processing_started(self):
-        await self._transition_phase(WorkflowOperationalPhase.PROCESSING)
-
-    async def notify_processing_complete_and_idle(self):
-        await self._transition_phase(WorkflowOperationalPhase.IDLE)
-
-    async def notify_error_occurred(self, error_message: str, error_details: Optional[str] = None):
-        await self._transition_phase(WorkflowOperationalPhase.ERROR, {"error_message": error_message, "error_details": error_details})
-
-    async def notify_shutdown_initiated(self):
-        await self._transition_phase(WorkflowOperationalPhase.SHUTTING_DOWN)
-
-    async def notify_final_shutdown_complete(self):
-        await self._transition_phase(WorkflowOperationalPhase.SHUTDOWN_COMPLETE)

autobyteus-1.2.1.dist-info/METADATA

@@ -1,205 +0,0 @@
-Metadata-Version: 2.4
-Name: autobyteus
-Version: 1.2.1
-Summary: Multi-Agent framework
-Home-page: https://github.com/AutoByteus/autobyteus
-Author: Ryan Zheng
-Author-email: ryan.zheng.work@gmail.com
-Classifier: Development Status :: 3 - Alpha
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3.8
-Classifier: Programming Language :: Python :: 3.9
-Classifier: Programming Language :: Python :: 3.10
-Requires-Python: >=3.8
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: aiohttp
-Requires-Dist: anthropic
-Requires-Dist: beautifulsoup4
-Requires-Dist: boto3
-Requires-Dist: botocore
-Requires-Dist: brui-core==1.0.9
-Requires-Dist: certifi==2025.4.26
-Requires-Dist: cryptography
-Requires-Dist: google-api-python-client
-Requires-Dist: google-genai==1.38.0
-Requires-Dist: httpx
-Requires-Dist: Jinja2
-Requires-Dist: mcp[cli]
-Requires-Dist: mistral_common
-Requires-Dist: mistralai
-Requires-Dist: numpy
-Requires-Dist: ollama
-Requires-Dist: openai
-Requires-Dist: requests
-Requires-Dist: rich
-Requires-Dist: textual
-Requires-Dist: tiktoken
-Requires-Dist: tokenizers
-Provides-Extra: dev
-Requires-Dist: coverage; extra == "dev"
-Requires-Dist: flake8; extra == "dev"
-Requires-Dist: numpy; extra == "dev"
-Requires-Dist: pre-commit; extra == "dev"
-Requires-Dist: black; extra == "dev"
-Requires-Dist: isort; extra == "dev"
-Requires-Dist: gitpython==3.1.31; extra == "dev"
-Requires-Dist: auto-gpt-plugin-template; extra == "dev"
-Requires-Dist: mkdocs; extra == "dev"
-Requires-Dist: pytest; extra == "dev"
-Requires-Dist: asynctest; extra == "dev"
-Requires-Dist: pytest-asyncio; extra == "dev"
-Requires-Dist: pytest-benchmark; extra == "dev"
-Requires-Dist: pytest-cov; extra == "dev"
-Requires-Dist: pytest-integration; extra == "dev"
-Requires-Dist: pytest-mock; extra == "dev"
-Requires-Dist: vcrpy; extra == "dev"
-Requires-Dist: pytest-vcr; extra == "dev"
-Requires-Dist: load_dotenv; extra == "dev"
-Dynamic: author
-Dynamic: author-email
-Dynamic: classifier
-Dynamic: description
-Dynamic: description-content-type
-Dynamic: home-page
-Dynamic: license-file
-Dynamic: provides-extra
-Dynamic: requires-dist
-Dynamic: requires-python
-Dynamic: summary
-
-# Autobyteus
-
-Autobyteus is an open-source, application-first agentic framework for Python. It is designed to help developers build, test, and deploy complex, stateful, and extensible AI agents by providing a robust architecture and a powerful set of tools.
-
-![Autobyteus TUI Dashboard](docs/images/image_1.png)
-
-## Architecture
-
-Autobyteus is built with a modular, event-driven architecture designed for extensibility and clear separation of concerns. The key components are:
-
--   **Agent Core**: The heart of the system. Each agent is a stateful, autonomous entity that runs as a background process in its own thread, managed by a dedicated `AgentWorker`. This design makes every agent a truly independent entity capable of handling long-running tasks.
--   **Agent Teams**: The framework provides powerful constructs for building hierarchical multi-agent systems. The `AgentTeam` module allows you to compose teams of individual agents and even nest teams within other teams, enabling sophisticated, real-world organizational structures and delegation patterns.
--   **Context & Configuration**: Agent behavior is defined through a static configuration (`AgentConfig`) and its dynamic state is managed in `AgentRuntimeState`. These are bundled into a comprehensive `AgentContext` that is passed to all components, providing a single source of truth.
--   **Event-Driven System**: Agents operate on an internal `asyncio` event loop. User messages, tool results, and internal signals are handled as events, which are processed by dedicated `EventHandlers`. This decouples logic and makes the system highly extensible.
--   **Pluggable Processors & Hooks**: The framework provides a chain of extension points to inject custom logic at every major step of an agent's reasoning loop. This architecture powers features like flexible tool format parsing. You can customize behavior by implementing:
-    -   **`InputProcessors`**: To modify or enrich user messages *before* they are sent to the LLM.
-    -   **`LLMResponseProcessors`**: To parse the LLM's raw output and extract structured actions, such as tool calls.
-    -   **`ToolExecutionResultProcessors`**: To modify the result from a tool *before* it is sent back to the LLM for the next step of reasoning.
-    -   **`PhaseHooks`**: To run custom code on specific agent lifecycle transitions (e.g., when an agent becomes `IDLE`).
--   **Context-Aware Tooling**: Tools are first-class citizens that receive the agent's full `AgentContext` during execution. This allows tools to be deeply integrated with the agent's state, configuration, and workspace, enabling more intelligent and powerful actions.
--   **Tool Approval Flow**: The framework has native support for human-in-the-loop workflows. By setting `auto_execute_tools=False` in the agent's configuration, the agent will pause before executing a tool, emit an event requesting permission, and wait for external approval before proceeding.
--   **MCP Integration**: The framework has native support for the Model Context Protocol (MCP). This allows agents to discover and use tools from external, language-agnostic tool servers, making the ecosystem extremely flexible and ready for enterprise integration.
-
-## Key Features
-
-#### 📊 Interactive TUI Dashboard
-Launch and monitor your agent teams with our built-in Textual-based TUI.
--   **Hierarchical View**: See the structure of your team, including sub-teams and their agents.
--   **Real-Time Status**: Agent and team statuses are updated live, showing you who is idle, thinking, or executing a tool.
--   **Detailed Logs**: Select any agent to view a detailed, streaming log of their thoughts, actions, and tool interactions.
--   **Live Task Plan**: Watch your team's `TaskPlan` update in real-time as the coordinator publishes a plan and agents complete their tasks.
-
-| TUI - Detailed Agent Log | TUI - Task Plan with Completed Task |
-| :---: | :---: |
-| ![Autobyteus Agent Log](docs/images/image_4.png) | ![Autobyteus Task Plan](docs/images/image_3.png) |
-
-#### 🏗️ Fluent Team Building
-Define complex agent and team structures with an intuitive, fluent API. The `AgentTeamBuilder` makes composing your team simple and readable.
-
-```python
-# --- From the Multi-Researcher Team Example ---
-research_team = (
-    AgentTeamBuilder(
-        name="MultiSpecialistResearchTeam",
-        description="A team for delegating to multiple specialists."
-    )
-    .set_coordinator(coordinator_config)
-    .add_agent_node(researcher_web_config)
-    .add_agent_node(researcher_db_config)
-    .build()
-)
-```
-
-#### 🔁 Flexible Tool Formatting (JSON & XML)
-Autobyteus intelligently handles tool communication with LLMs while giving you full control.
--   **Provider-Aware by Default**: The framework automatically generates tool manifests and parses responses in the optimal format for the selected LLM provider (e.g., JSON for OpenAI/Gemini, XML for Anthropic).
--   **XML Override for Efficiency**: You can set `use_xml_tool_format=True` on an `AgentConfig` or `AgentTeamBuilder` to force the use of XML for tool calls, which can be more efficient and reliable than JSON for complex tool schemas.
-
-#### 📈 Flexible Communication Protocols
-Choose the collaboration pattern that best fits your use case with configurable `TaskNotificationMode`s.
--   **`AGENT_MANUAL_NOTIFICATION` (Default)**: A traditional approach where a coordinator agent is responsible for creating a plan and then explicitly notifying other agents to begin their work via messages.
--   **`SYSTEM_EVENT_DRIVEN`**: A more automated approach where the coordinator's only job is to publish a plan to the `TaskPlan`. The framework then monitors the board and automatically notifies agents when their tasks become unblocked, enabling parallel execution and reducing coordinator overhead.
-
-## Requirements
-
--   **Python Version**: Python 3.11 is the recommended and tested version for this project. Using newer versions of Python may result in dependency conflicts when installing the required packages. For a stable and tested environment, please use Python 3.11.
-
-## Getting Started
-
-### Installation
-
-1.  **Clone the repository:**
-    ```bash
-    git clone https://github.com/your-username/autobyteus.git
-    cd autobyteus
-    ```
-
-2.  **For users:**
-    To install Autobyteus and its core dependencies:
-    ```bash
-    pip install .
-    ```
-
-3.  **For developers:**
-    To install Autobyteus with all development and example dependencies (including the TUI):
-    ```bash
-    pip install -r requirements-dev.txt
-    ```
-
-4.  **Set up Environment Variables:**
-    Create a `.env` file in the root of the project and add your LLM provider API keys:
-    ```
-    # .env
-    OPENAI_API_KEY="sk-..."
-    KIMI_API_KEY="your-kimi-api-key"
-    # etc.
-    ```
-
-### Running the Examples
-
-The best way to experience Autobyteus is to run one of the included examples. The event-driven software engineering team is a great showcase of the framework's capabilities.
-
-```bash
-# Run the event-driven software engineering team example
-python autobyteus/examples/agent_team/event_driven/run_software_engineering_team.py --llm-model gpt-4o
-
-# Run the hierarchical debate team example
-python autobyteus/examples/agent_team/manual_notification/run_debate_team.py --llm-model gpt-4-turbo
-```
-You can see all available models and their identifiers by running an example with the `--help-models` flag.
-
-### Building the Library
-
-To build Autobyteus as a distributable package, follow these steps:
-
-1.  Ensure you have the latest version of `setuptools` and `wheel` installed:
-    ```
-    pip install --upgrade setuptools wheel
-    ```
-
-2.  Build the distribution packages:
-    ```
-    python setup.py sdist bdist_wheel
-    ```
-
-This will create a `dist` directory containing the built `sdist` and `wheel` distributions.
-
-## Contributing
-
-(Add guidelines for contributing to the project)
-
-## License
-
-This project is licensed under the MIT License.