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

[triage-generated] [bug] Loop never writes cycle_result.json — 0% success rate is measurement bug #1462

New Issue
Closed
opened 2026-03-24 20:09:54 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 20:09:54 +00:00
Owner
Copy Link

Problem

The dev loop records 0% success rate across 50+ cycles despite hermes actually working on issues. Root cause: hermes agent never writes cycle_result.json. The loop prompt does not instruct the agent to write it.

Evidence

  • Last 50 cycles: issue=null on ALL entries
  • cycle_result.json does not exist on disk
  • state.json shows cycle 2379 DID work on #1447

Fix

timmy-loop-prompt.md must instruct agent to write .loop/cycle_result.json at end of each cycle.

Acceptance Criteria

  • timmy-loop-prompt.md includes cycle_result.json write instructions
  • After fix, cycles have issue number in retro
  • summary.json shows non-zero success rate when PRs merge

Files

  • ~/.hermes/bin/timmy-loop-prompt.md
  • scripts/cycle_retro.py
## Problem The dev loop records 0% success rate across 50+ cycles despite hermes actually working on issues. Root cause: hermes agent never writes cycle_result.json. The loop prompt does not instruct the agent to write it. ## Evidence - Last 50 cycles: issue=null on ALL entries - cycle_result.json does not exist on disk - state.json shows cycle 2379 DID work on #1447 ## Fix timmy-loop-prompt.md must instruct agent to write .loop/cycle_result.json at end of each cycle. ## Acceptance Criteria - timmy-loop-prompt.md includes cycle_result.json write instructions - After fix, cycles have issue number in retro - summary.json shows non-zero success rate when PRs merge ## Files - ~/.hermes/bin/timmy-loop-prompt.md - scripts/cycle_retro.py
Timmy commented 2026-03-24 20:14:20 +00:00
Author
Owner
Copy Link

Fixed. The root cause was that timmy-loop-prompt.md (the harness prompt at ~/.hermes/bin/) never instructed the agent to write cycle_result.json.

What changed:

  • Added step 12 to PHASE 6 — REFLECT in the loop prompt, requiring agents to write .loop/cycle_result.json with issue, type, tests_passed, and notes fields
  • scripts/cycle_retro.py already had the reader (_load_cycle_result() at line 250) — it just never got data to read

Verification: Starting this cycle, the retro will log real issue numbers instead of null. Success rate in summary.json will reflect actual work.

Fixed. The root cause was that `timmy-loop-prompt.md` (the harness prompt at `~/.hermes/bin/`) never instructed the agent to write `cycle_result.json`. **What changed:** - Added step 12 to PHASE 6 — REFLECT in the loop prompt, requiring agents to write `.loop/cycle_result.json` with `issue`, `type`, `tests_passed`, and `notes` fields - `scripts/cycle_retro.py` already had the reader (`_load_cycle_result()` at line 250) — it just never got data to read **Verification:** Starting this cycle, the retro will log real issue numbers instead of null. Success rate in summary.json will reflect actual work.
Timmy closed this issue 2026-03-24 20:14:20 +00:00
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 kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1462
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?