Timmy_Foundation/hermes-agent
15
0
Fork 0
Code Issues 113 Pull Requests 98 Actions 16 Packages Projects Releases Wiki Activity

cron: evennia-morning-report remains flagged with stale tool_choice failure after direct run succeeds (job 64fe44b512b9) #347

New Issue
Closed
opened 2026-04-13 07:04:25 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-13 07:04:25 +00:00
Owner
Copy Link

Follow-up to #343.

Observed job: evennia-morning-report (64fe44b512b9)
Stored last_error:

TypeError: AIAgent.__init__() got an unexpected keyword argument 'tool_choice'

Current manual diagnosis:

  • direct run_job() execution now succeeds and produces a complete Tower morning report
  • the stored failure is residue from the old tool_choice regression, not the current runtime behavior
  • hermes cron run 64fe44b512b9 still only queues the job for a future scheduler tick instead of giving an immediate verified result

Root cause:

  • cron has no synchronous/persistent manual re-run path, so jobs can stay visibly broken even after the underlying bug is fixed

Acceptance criteria:

  1. a manual cron re-run can execute immediately and persist fresh job state
  2. operators can clear stale tool_choice failure residue by revalidating the job directly
  3. cron status/reporting distinguishes historical failure residue from current runnable state
Follow-up to #343. Observed job: `evennia-morning-report` (`64fe44b512b9`) Stored last_error: ``` TypeError: AIAgent.__init__() got an unexpected keyword argument 'tool_choice' ``` Current manual diagnosis: - direct `run_job()` execution now succeeds and produces a complete Tower morning report - the stored failure is residue from the old tool_choice regression, not the current runtime behavior - `hermes cron run 64fe44b512b9` still only queues the job for a future scheduler tick instead of giving an immediate verified result Root cause: - cron has no synchronous/persistent manual re-run path, so jobs can stay visibly broken even after the underlying bug is fixed Acceptance criteria: 1. a manual cron re-run can execute immediately and persist fresh job state 2. operators can clear stale `tool_choice` failure residue by revalidating the job directly 3. cron status/reporting distinguishes historical failure residue from current runnable state
Timmy closed this issue 2026-04-13 14:03:09 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, production audit
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Task assigned to KimiClaw for processing
 blocked
Blocked by external dependency or merge conflict
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 duplicate
Duplicate of another issue
 epic
Epic - large feature with multiple sub-tasks
 epic:memory
Unified Memory Architecture epic
 gaming
Gaming agent capabilities
 infra
Infrastructure, VPS, DNS, deployment
 kimi-done
KimiClaw has completed this task
 kimi-in-progress
KimiClaw is actively working on this
 mcp
MCP (Model Context Protocol) tools & servers
 morrowind
Morrowind Agent gameplay & MCP integration
 needs-review
PR or issue requires reviewer sign-off before merge/close
 p0-critical
p1-important
phase:1-activate
Phase 1: Activate existing systems
 phase:2-operational
Phase 2: Operational memory bridge
 phase:3-episodic
Phase 3: Proactive episodic recall
 phase:4-hygiene
Phase 4: Memory hygiene and quality
 phase:5-integration
Phase 5: Integration and testing
 poka-yoke
research
security
Security hardening, vulnerability fixes
 stale
No activity, pending triage or closure
 tool-evaluation
velocity-engine
Auto-generated by velocity engine
 wont-fix
Closed as intentionally not fixing — explicit descope
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/hermes-agent#347
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?