feat: Add MedGemma/TxGemma model configurations to terraphim_multi_agent

Open
#537 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
ai

Research direction

Start in crates/terraphim_multi_agent/src/agent.rs at the GenAiLlmClient section, then inspect the genai fork to understand its provider boundaries. Define how the HuggingFace and Google endpoints, listed MedGemma and TxGemma configurations, and optional GGUF fallback fit the design; done means the requested model families can be selected through supported providers.

Written by the indexing model from the issue text.

Description

enhancement multi-agent

Problem

terraphim_multi_agent uses the genai crate (terraphim fork of rust-genai) with OpenRouter as the default provider. MedGemma and TxGemma models are available via HuggingFace Inference API and Google AI Studio but not via OpenRouter. The agent's LLM client has no support for HuggingFace or Google endpoints.

Proposed Change

  • Add HuggingFace Inference API provider to genai or as an alternative in terraphim_multi_agent::GenAiLlmClient
  • Add model configs for MedGemma 1.5-4b-it, MedGemma 27b-text-it, TxGemma 2b/9b/27b variants
  • Add Google AI Studio provider as an alternative
  • Support GGUF local inference via llama-cpp-rs as a fallback provider

Scope

  • crates/terraphim_multi_agent/src/agent.rs (LLM client section)
  • Possibly genai fork in a separate PR

Context

This is UPLIFT-4 from the medgemma-competition multi-agent integration plan. MedGemma models are Google's medical foundation models (HAI-DEF ecosystem, Feb 2026) and are critical for clinical reasoning in agentic workflows. The current genai/OpenRouter path does not support these model families.

Related upstream issues: #534, #535, #536

Dominant language
Rust
Stars
62
Forks
5
Avg merge
2h 27m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from terraphim/terraphim-ai

All issues in terraphim/terraphim-ai

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.