[GEMINI-04] Agent dispatch framework — replace the ad-hoc dispatch scripts #402

Closed
opened 2026-04-08 10:52:57 +00:00 by Timmy · 0 comments
Owner

Part of Epic: #398

Timmy built dispatch scripts per-agent: Ezra has dispatch-direct.sh, the orchestrator hits the Gitea API. It's fragile and inconsistent.

Build a unified dispatch framework:

  • Agent registry with capabilities, endpoints, health status
  • Issue-to-agent matching based on skills, not just assignment
  • Dispatch via llama.cpp API (not Ollama, not hermes gateway)
  • Retry with fallback to another agent on failure
  • Track dispatch state: assigned, working, completed, failed

This replaces: orchestrator.py dispatch logic, ezra/dispatch-direct.sh, agent-loop.sh issue picker.

Acceptance Criteria

  • Single dispatch entry point for all agents
  • Agent registry with health checks
  • Skill-based matching (not random assignment)
  • Dispatch traces logged for debugging
Part of Epic: #398 Timmy built dispatch scripts per-agent: Ezra has dispatch-direct.sh, the orchestrator hits the Gitea API. It's fragile and inconsistent. Build a unified dispatch framework: - Agent registry with capabilities, endpoints, health status - Issue-to-agent matching based on skills, not just assignment - Dispatch via llama.cpp API (not Ollama, not hermes gateway) - Retry with fallback to another agent on failure - Track dispatch state: assigned, working, completed, failed This replaces: orchestrator.py dispatch logic, ezra/dispatch-direct.sh, agent-loop.sh issue picker. ## Acceptance Criteria - [ ] Single dispatch entry point for all agents - [ ] Agent registry with health checks - [ ] Skill-based matching (not random assignment) - [ ] Dispatch traces logged for debugging
gemini was assigned by Timmy 2026-04-08 10:52:57 +00:00
bezalel was assigned by Timmy 2026-04-08 16:46:39 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#402