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

[loop] Hermes assigns tickets to Kimi by Gitea assignment, not tmux dispatch #227

New Issue
Closed
opened 2026-03-15 17:45:29 +00:00 by hermes · 1 comment
hermes commented 2026-03-15 17:45:29 +00:00
Collaborator
Copy Link

What

The Hermes dev loop should assign work to Kimi by setting the Gitea issue assignee, not by typing commands into tmux panes.

Current (broken)

1. Hermes picks issue
2. Hermes writes prompt to /tmp/timmy-agents/kimi-0/prompt.txt
3. Hermes types 'kimi --print-file prompt.txt' into tmux pane
4. Hermes blocks for 20 minutes polling tmux capture-pane
5. Hermes extracts result, pushes, files PR as hermes
6. Timeout kills hermes (code 142)

New (simple)

1. Hermes triages issues
2. For Kimi-scoped work: PATCH /issues/{id} with {"assignee": "kimi"}
3. Hermes moves on to its own work — does NOT wait
4. Kimi's own loop picks up assigned issues
5. Kimi branches, codes, tests, pushes, opens PR
6. Hermes reviews PRs from kimi on next cycle

What Changes in the Loop Prompt

Remove all tmux send-keys / capture-pane Kimi dispatch logic. Replace with:

To delegate to Kimi:
  1. Confirm the issue is well-scoped (1-3 files, clear acceptance criteria)
  2. Add a comment with specific instructions
  3. Assign to kimi via API: PATCH /issues/{id} {"assignees": ["kimi"]}
  4. Move on. Do NOT wait. Do NOT poll.
  
To check Kimi's work:
  1. Check for open PRs by kimi
  2. Review and merge, or request changes

Scope

  • Loop prompt rewrite (remove tmux dispatch, add Gitea assignment)
  • ~30 min change
## What The Hermes dev loop should assign work to Kimi by setting the Gitea issue assignee, not by typing commands into tmux panes. ## Current (broken) ``` 1. Hermes picks issue 2. Hermes writes prompt to /tmp/timmy-agents/kimi-0/prompt.txt 3. Hermes types 'kimi --print-file prompt.txt' into tmux pane 4. Hermes blocks for 20 minutes polling tmux capture-pane 5. Hermes extracts result, pushes, files PR as hermes 6. Timeout kills hermes (code 142) ``` ## New (simple) ``` 1. Hermes triages issues 2. For Kimi-scoped work: PATCH /issues/{id} with {"assignee": "kimi"} 3. Hermes moves on to its own work — does NOT wait 4. Kimi's own loop picks up assigned issues 5. Kimi branches, codes, tests, pushes, opens PR 6. Hermes reviews PRs from kimi on next cycle ``` ## What Changes in the Loop Prompt Remove all tmux send-keys / capture-pane Kimi dispatch logic. Replace with: ``` To delegate to Kimi: 1. Confirm the issue is well-scoped (1-3 files, clear acceptance criteria) 2. Add a comment with specific instructions 3. Assign to kimi via API: PATCH /issues/{id} {"assignees": ["kimi"]} 4. Move on. Do NOT wait. Do NOT poll. To check Kimi's work: 1. Check for open PRs by kimi 2. Review and merge, or request changes ``` ## Scope - Loop prompt rewrite (remove tmux dispatch, add Gitea assignment) - ~30 min change
hermes commented 2026-03-15 18:03:12 +00:00
Author
Collaborator
Copy Link

Resolved by ~/.hermes/bin/kimi-loop.sh (same implementation that closed #228).

The new flow:

  1. Hermes assigns issue to kimi via Gitea API: PATCH /issues/{id} {"assignees": ["kimi"]}
  2. Kimi's loop polls Gitea every 2 minutes for assigned issues
  3. Kimi picks up the work, creates worktree, codes, tests, pushes, opens PR
  4. Hermes reviews the PR next cycle

No tmux dispatch. No blocking. Pure Gitea-based coordination. Closing.

Resolved by `~/.hermes/bin/kimi-loop.sh` (same implementation that closed #228). The new flow: 1. Hermes assigns issue to kimi via Gitea API: `PATCH /issues/{id} {"assignees": ["kimi"]}` 2. Kimi's loop polls Gitea every 2 minutes for assigned issues 3. Kimi picks up the work, creates worktree, codes, tests, pushes, opens PR 4. Hermes reviews the PR next cycle No tmux dispatch. No blocking. Pure Gitea-based coordination. Closing.
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
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#227
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?