user_requirements.md

User Requirements for GAIA Framework Improvement

Based on the provided pasted_content.txt, the user's requirements for improving the GAIA multi-agent framework are as follows:

Overall Goal

Improve the existing multi-agent framework to maximize performance on the GAIA benchmark.

Specific Objectives

1. Code Quality Review:

   • Analyze all source files (.py, config, tests, docs if present).
   • Identify weaknesses such as:
     • Design smells
     • Performance issues
     • Missing type hints
     • Brittle parsing logic
     • Insufficient test coverage
     • Other reliability impairments.

2. Refactor Proposals:

   • For each identified weakness, suggest concise improvements.
   • Provide practical improvements as diff-style patches where feasible.

3. New Feature Implementation:

   • YouTube Ingestion:
     • Input: YouTube video URL.
     • Process: Download audio -> Chunk audio (≤ 60 seconds) -> Transcribe chunks using Gemini 1.5 Pro.
     • Output: Full transcript and a one-paragraph summary.
   • Generic Audio Transcription:
     • Input: Local audio file path or remote audio URL.
     • Process: Transcribe using Gemini 1.5 Pro (preferred for latency tolerance) or Whisper-cpp (fallback).
     • Output: Expose functionality via a simple Python API.

4. Extra Agent Design:

   • Design at least three new specialized agents.
   • These agents should demonstrably contribute to boosting GAIA benchmark performance.
   • For each new agent, provide:
     • Purpose
     • Key tool calls
     • Sketch of the agent loop/logic.

5. Migration Plan:

   • Define the recommended order for applying the proposed refactor patches and implementing new features.
   • List all new dependencies required for requirements.txt.
   • Outline the minimal unit and/or integration tests needed to validate each new feature or significant change.

Output Format Requirements

• Start the final report with a short ASCII diagram representing the revised system architecture (incorporating proposed changes).
• For each modified source file or new module:
  • Provide a one-sentence rationale for the change.
  • Include any required unified diff patches enclosed in triple backticks with the filename in the header.
• Group related changes together.
• Use plain paragraphs rather than long bullet lists where appropriate.
• Maintain concise prose.
• Ask brief clarifying questions if uncertainties arise during the process.

Process Constraint

• Wait for user confirmation before starting the review.
• The initial phase involves analysis and presenting the improvement plan (including architecture diagram, code review findings, refactor proposals, new feature designs, extra agent designs, and migration plan).
• Stop after presenting this initial plan and await further instructions or confirmation.