Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

Build agent dispatcher — route tasks to Claude Code, Kimi, APIs #1072

New Issue
Closed
opened 2026-03-23 13:11:55 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-23 13:11:55 +00:00
Collaborator
Copy Link

Parent: #1070

Objective

Timmy needs to know what agents are available, what they're good at, and how to send them work. This is the dispatch system.

Agent Registry

Agent Strengths Interface Max Concurrent
Claude Code Architecture, refactoring, complex reasoning, code review CLI / API 1
Kimi Code Parallel implementation, routine coding, fast iteration CLI / API 1
Agent APIs Research, analysis, specialized tasks HTTP API Varies
Timmy (self) Triage, planning, creative writing, orchestration Local 1

Dispatch Logic

  1. Match task type to agent strengths
  2. Check agent availability (is it idle or working?)
  3. Send task with context (issue link, requirements, acceptance criteria)
  4. Monitor for completion or timeout
  5. Review output quality
  6. If output fails QA → reassign or flag

Acceptance Criteria

  • Timmy can programmatically invoke Claude Code and Kimi Code on specific issues
  • Task assignment is logged in Gitea (comment on issue: "Assigned to Claude Code")
  • Completion is detected and logged
  • Failed tasks are retried or escalated
Parent: #1070 ## Objective Timmy needs to know what agents are available, what they're good at, and how to send them work. This is the dispatch system. ## Agent Registry | Agent | Strengths | Interface | Max Concurrent | |---|---|---|---| | Claude Code | Architecture, refactoring, complex reasoning, code review | CLI / API | 1 | | Kimi Code | Parallel implementation, routine coding, fast iteration | CLI / API | 1 | | Agent APIs | Research, analysis, specialized tasks | HTTP API | Varies | | Timmy (self) | Triage, planning, creative writing, orchestration | Local | 1 | ## Dispatch Logic 1. Match task type to agent strengths 2. Check agent availability (is it idle or working?) 3. Send task with context (issue link, requirements, acceptance criteria) 4. Monitor for completion or timeout 5. Review output quality 6. If output fails QA → reassign or flag ## Acceptance Criteria - Timmy can programmatically invoke Claude Code and Kimi Code on specific issues - Task assignment is logged in Gitea (comment on issue: "Assigned to Claude Code") - Completion is detected and logged - Failed tasks are retried or escalated
claude self-assigned this 2026-03-23 13:32:57 +00:00
claude added the harnessmemory-sessionp0-critical labels 2026-03-23 13:53:09 +00:00
claude commented 2026-03-23 18:21:40 +00:00
Collaborator
Copy Link

PR #1123 created.

Implemented the full agent dispatcher in src/timmy/dispatcher.py:

  • AgentRegistry with Claude Code, Kimi Code, Agent API, and Timmy entries
  • select_agent() routing table mapping TaskTypes to best-fit agents
  • infer_task_type() keyword heuristic
  • dispatch_task() with retry logic and Gitea escalation comments
  • wait_for_completion() polling Gitea issue state

44 unit tests all passing.

PR #1123 created. Implemented the full agent dispatcher in `src/timmy/dispatcher.py`: - AgentRegistry with Claude Code, Kimi Code, Agent API, and Timmy entries - select_agent() routing table mapping TaskTypes to best-fit agents - infer_task_type() keyword heuristic - dispatch_task() with retry logic and Gitea escalation comments - wait_for_completion() polling Gitea issue state 44 unit tests all passing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness memory-session p0-critical
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1072
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?