 Here is a summary designed to be used with an agent to implement the "Gemini Team Integration" script.
------------------------------
## Instructions for Team Integration: Adding Gemini to the Workflow## 1. Goal
Integrate Gemini 1.5/2.0 Pro into the existing imagej-elphel collaboration environment. Gemini must be accessible via CLI using the GEMINI_API_KEY from .bashrc. It will participate in the "summary" script to find consensus and unique recommendations.
## 2. Software Requirements

* Gemini CLI: Install via npm install -g @google/gemini-cli.
* Environment: Ensure export GEMINI_API_KEY="xxx" is active in the shell.

## 3. Model Logic (Flash vs. Pro)
To minimize human effort, the script should toggle models based on the task:

* Flash (Default): Use for quick code checks, unit test results, and standard console output analysis. It is fast and uses fewer tokens/credits.
* Pro (Deep Research/Multimodal): Use for "Consensus Summaries," reading complex PCB diagrams, or analyzing large sections of Xilinx Zynq documentation.
* CLI Implementation: Use the --model flag.
* Example: gemini --model gemini-1.5-pro "Task description"

## 4. Implementation Task
Write a bash script (e.g., agent_consulter.sh) that automates the following "Consultation" loop:

   1. Input: Takes the tail of the current session or a specific file path as input.
   2. Multimodal Handling: If a file path is a PDF or PNG (circuit diagram), it should use the Pro model with the @ reference.
   3. The Summary Loop:
   * Pipe the context to the Gemini CLI.
      * Prompt Strategy: "Review the provided dialogue/code from Codex and Claude. Output a 3-section summary: 1) Points of universal agreement. 2) Unique insights from Codex/Claude. 3) Your (Gemini) unique recommendations based on Zynq/ImageJ architecture."
   4. Eclipse Integration: Ensure the script outputs the summary to a file that the human can view in Eclipse without switching windows.

## 5. Specific Constraints

* The script must operate entirely within the CLI.
* No "Paste this into a browser" prompts.
* If an image/PDF needs analysis (like the camera board diagram), the script should handle the file path directly.

------------------------------
This approach allows you to stay in Konsole and keep your Eclipse view for code while agents perform tasks. By defaulting to Flash for minor tasks and calling Pro for the "Summary," speed and intelligence are balanced.


