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

[loop] Kimi needs its own agent loop that picks up assigned issues #228

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

Kimi needs a simple loop (cron or tmux-based) that:

  1. Polls Gitea for issues assigned to kimi
  2. Picks the highest priority one
  3. Creates branch kimi/issue-{number}
  4. Does the work in its own worktree
  5. Runs tests (tox -e unit)
  6. Pushes the branch
  7. Opens a PR (authored by kimi, assigned to hermes for review)

Design

# Kimi's loop (simplified)
while true; do
  # Find assigned issues
  issues=$(curl "...?assignee=kimi&state=open")
  
  if [ -n "$issues" ]; then
    # Pick top issue
    # Create worktree at ~/worktrees/kimi-{issue}
    # Run kimi CLI with the issue as context
    # Push and PR
  fi
  
  sleep 120  # Check every 2 minutes
done

Kimi's Git Identity

The workspace must use kimi's own credentials:

git config user.name "kimi"
git config user.email "kimi@localhost"
# Push URL includes kimi's token for auth

Token: ~/.hermes/kimi_token

What Kimi's PR Should Look Like

  • Branch: kimi/issue-{number}-{slug}
  • PR title: [kimi] {issue title} (#{number})
  • PR body: what was changed and why, references the issue
  • Assigned reviewer: hermes
  • Tests must pass before PR is opened

Scope

  • New script: ~/.hermes/bin/kimi-loop.sh
  • Kimi workspace setup with kimi git identity
  • Cron or tmux session to run it
## What Kimi needs a simple loop (cron or tmux-based) that: 1. Polls Gitea for issues assigned to `kimi` 2. Picks the highest priority one 3. Creates branch `kimi/issue-{number}` 4. Does the work in its own worktree 5. Runs tests (`tox -e unit`) 6. Pushes the branch 7. Opens a PR (authored by kimi, assigned to hermes for review) ## Design ```bash # Kimi's loop (simplified) while true; do # Find assigned issues issues=$(curl "...?assignee=kimi&state=open") if [ -n "$issues" ]; then # Pick top issue # Create worktree at ~/worktrees/kimi-{issue} # Run kimi CLI with the issue as context # Push and PR fi sleep 120 # Check every 2 minutes done ``` ## Kimi's Git Identity The workspace must use kimi's own credentials: ``` git config user.name "kimi" git config user.email "kimi@localhost" # Push URL includes kimi's token for auth ``` Token: `~/.hermes/kimi_token` ## What Kimi's PR Should Look Like - Branch: `kimi/issue-{number}-{slug}` - PR title: `[kimi] {issue title} (#{number})` - PR body: what was changed and why, references the issue - Assigned reviewer: hermes - Tests must pass before PR is opened ## Scope - New script: `~/.hermes/bin/kimi-loop.sh` - Kimi workspace setup with kimi git identity - Cron or tmux session to run it
hermes commented 2026-03-15 18:02:07 +00:00
Author
Collaborator
Copy Link

Issue #228 is complete. The kimi agent loop is fully implemented and operational.

What exists:

  • ~/.hermes/bin/kimi-loop.sh — 200+ line script covering the full lifecycle
  • Polls Gitea every 2 minutes for issues assigned to kimi
  • Creates worktrees at ~/worktrees/kimi-{issue} with kimi's git identity
  • Runs kimi CLI with issue context, tests (tox -e unit), and lint (tox -e lint)
  • Pushes branch kimi/issue-{number}, opens PR assigned to hermes for review
  • Comments on issues at each stage (starting work, submitting PR, or reporting failure)
  • Cleans up worktrees after completion
  • Running now in tmux session Kimi (PID active)

Currently active worktrees: kimi-231, kimi-233

All requirements from the issue are met. Closing.

Issue #228 is complete. The kimi agent loop is fully implemented and operational. **What exists:** - `~/.hermes/bin/kimi-loop.sh` — 200+ line script covering the full lifecycle - Polls Gitea every 2 minutes for issues assigned to `kimi` - Creates worktrees at `~/worktrees/kimi-{issue}` with kimi's git identity - Runs kimi CLI with issue context, tests (`tox -e unit`), and lint (`tox -e lint`) - Pushes branch `kimi/issue-{number}`, opens PR assigned to `hermes` for review - Comments on issues at each stage (starting work, submitting PR, or reporting failure) - Cleans up worktrees after completion - Running now in tmux session `Kimi` (PID active) **Currently active worktrees:** `kimi-231`, `kimi-233` All requirements from the issue are met. 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#228
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?