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

[claude] Build agent dispatcher — route tasks to Claude Code, Kimi, APIs (#1072) #1123

Merged
claude merged 1 commits from claude/issue-1072 into main 2026-03-23 18:25:39 +00:00
Conversation 0 Commits 1 Files Changed 2 +1304
claude commented 2026-03-23 18:21:31 +00:00
Collaborator
Copy Link

Fixes #1072

Summary

  • AgentRegistry with capabilities for Claude Code, Kimi Code, Agent API, and Timmy — each with strengths, Gitea label, interface type, and max_concurrent limit
  • TaskType enum covering architecture, refactoring, code review, routine coding, research, triage, planning, etc.
  • select_agent() routing table maps task types to best-fit agents
  • infer_task_type() heuristic infers task category from title/description keywords
  • dispatch_task() top-level entry point: auto-selects agent, dispatches via Gitea label + comment (claude-ready / kimi-ready), HTTP API, or local Timmy execution; retries on failure; escalates with Gitea comment
  • wait_for_completion() polls a Gitea issue until closed or timed out
  • 44 unit tests covering registry, routing, inference, dispatch flows, retry/escalation, and completion monitoring

Files changed

  • src/timmy/dispatcher.py — new dispatcher module
  • tests/timmy/test_dispatcher.py — 44 unit tests (all passing)
Fixes #1072 ## Summary - `AgentRegistry` with capabilities for Claude Code, Kimi Code, Agent API, and Timmy — each with strengths, Gitea label, interface type, and `max_concurrent` limit - `TaskType` enum covering architecture, refactoring, code review, routine coding, research, triage, planning, etc. - `select_agent()` routing table maps task types to best-fit agents - `infer_task_type()` heuristic infers task category from title/description keywords - `dispatch_task()` top-level entry point: auto-selects agent, dispatches via Gitea label + comment (`claude-ready` / `kimi-ready`), HTTP API, or local Timmy execution; retries on failure; escalates with Gitea comment - `wait_for_completion()` polls a Gitea issue until closed or timed out - 44 unit tests covering registry, routing, inference, dispatch flows, retry/escalation, and completion monitoring ## Files changed - `src/timmy/dispatcher.py` — new dispatcher module - `tests/timmy/test_dispatcher.py` — 44 unit tests (all passing)
claude added 1 commit 2026-03-23 18:21:33 +00:00
feat: add agent dispatcher — route tasks to Claude Code, Kimi, APIs (#1072)
Some checks failed
Tests / lint (pull_request) Failing after 14s
Details
Tests / test (pull_request) Has been skipped
Details
d11199888a 
Implements the task dispatch system described in issue #1072:

- AgentRegistry with capabilities for Claude Code, Kimi Code, Agent API,
  and Timmy — each with strengths, Gitea label, interface type, and
  max_concurrent limit
- TaskType enum covering architecture, refactoring, code review,
  routine coding, research, triage, planning, etc.
- select_agent() routing table maps task types to best-fit agents
- infer_task_type() heuristic infers task category from title/description
- dispatch_task() top-level entry point: auto-selects agent, dispatches
  via Gitea label + comment (claude-ready / kimi-ready), HTTP API, or
  local Timmy execution; retries on failure; escalates with Gitea comment
- wait_for_completion() polls a Gitea issue until closed or timed out
- 44 unit tests covering registry, routing, inference, dispatch flows,
  retry/escalation, and completion monitoring

Fixes #1072

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
claude merged commit cf82bb0be4 into main 2026-03-23 18:25:39 +00:00
claude deleted branch claude/issue-1072 2026-03-23 18:25:40 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
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
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1123
Delete Branch "claude/issue-1072"

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?