Timmy_Foundation/hermes-agent
16
0
Fork 0
Code Issues 34 Pull Requests 1 Actions 9 Packages Projects Releases Wiki Activity

[CONFIG] Add Kimi model to fallback chain for Allegro and Bezalel #151

New Issue
Closed
opened 2026-04-06 22:43:31 +00:00 by Timmy · 4 comments
Timmy commented 2026-04-06 22:43:31 +00:00
Owner
Copy Link

Problem

Allegro and Bezalel are choking because the Kimi model code is not on their fallback chain. When primary models fail or rate-limit, Kimi should be available as a fallback option but is currently missing.

Expected Behavior

Kimi model code should be at the front of the fallback chain for both Allegro and Bezalel, so they can remain responsive when primary models are unavailable.

Context

This was reported in Telegram by Alexander Whitestone after observing both agents becoming unresponsive. Ezra was asked to investigate the fallback chain configuration.

Related

  • timmy-config #302: [ARCH] Fallback Portfolio Runtime Wiring (general fallback framework)
  • hermes-agent #150: [BEZALEL][AUDIT] Telegram Request-to-Gitea Tracking Audit

Acceptance Criteria

  • Kimi model code is added to Allegro fallback chain
  • Kimi model code is added to Bezalel fallback chain
  • Fallback ordering places Kimi appropriately (front of chain as requested)
  • Test and confirm both agents can successfully fall back to Kimi
  • Document the fallback chain configuration for both agents

/assign @ezra

## Problem Allegro and Bezalel are choking because the Kimi model code is not on their fallback chain. When primary models fail or rate-limit, Kimi should be available as a fallback option but is currently missing. ## Expected Behavior Kimi model code should be at the front of the fallback chain for both Allegro and Bezalel, so they can remain responsive when primary models are unavailable. ## Context This was reported in Telegram by Alexander Whitestone after observing both agents becoming unresponsive. Ezra was asked to investigate the fallback chain configuration. ## Related - timmy-config #302: [ARCH] Fallback Portfolio Runtime Wiring (general fallback framework) - hermes-agent #150: [BEZALEL][AUDIT] Telegram Request-to-Gitea Tracking Audit ## Acceptance Criteria - [ ] Kimi model code is added to Allegro fallback chain - [ ] Kimi model code is added to Bezalel fallback chain - [ ] Fallback ordering places Kimi appropriately (front of chain as requested) - [ ] Test and confirm both agents can successfully fall back to Kimi - [ ] Document the fallback chain configuration for both agents /assign @ezra
ezra was assigned by Timmy 2026-04-06 22:43:31 +00:00
ezra was unassigned by Rockachopa 2026-04-07 02:47:36 +00:00
claw-code was assigned by Rockachopa 2026-04-07 02:47:36 +00:00
Rockachopa commented 2026-04-07 02:48:07 +00:00
Owner
Copy Link

[BURN-DOWN] Dispatched to Code Claw (claw-code worker) as part of nightly burn-down cycle. Heartbeat active.

[BURN-DOWN] Dispatched to Code Claw (claw-code worker) as part of nightly burn-down cycle. Heartbeat active.
Timmy added the claw-code-in-progress label 2026-04-07 04:03:49 +00:00
Timmy commented 2026-04-07 04:03:49 +00:00
Author
Owner
Copy Link

🟠 Code Claw (OpenRouter qwen/qwen3.6-plus:free) picking up this issue via 15-minute heartbeat.

Timestamp: 2026-04-07T04:03:49Z

🟠 Code Claw (OpenRouter qwen/qwen3.6-plus:free) picking up this issue via 15-minute heartbeat. Timestamp: 2026-04-07T04:03:49Z
claw-code added claw-code-done and removed claw-code-in-progress labels 2026-04-07 04:04:02 +00:00
claw-code commented 2026-04-07 04:04:03 +00:00
Collaborator
Copy Link

✅ Code Claw completed a pass on this issue.

Branch: claw-code/issue-151
PR: #177
Exit: 1

✅ Code Claw completed a pass on this issue. Branch: `claw-code/issue-151` PR: https://forge.alexanderwhitestone.com/Timmy_Foundation/hermes-agent/pulls/177 Exit: 1
Timmy commented 2026-04-07 14:15:45 +00:00
Author
Owner
Copy Link

Closed. hermes-agent tracks upstream NousResearch only. Sovereign work belongs on Timmy_Foundation/timmy-config. Refile there if still needed.

Closed. hermes-agent tracks upstream NousResearch only. Sovereign work belongs on Timmy_Foundation/timmy-config. Refile there if still needed.
Timmy closed this issue 2026-04-07 14:15:46 +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
 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
security
Security hardening, vulnerability fixes
 stale
No activity, pending triage or closure
 velocity-engine
Auto-generated by velocity engine
 wont-fix
Closed as intentionally not fixing — explicit descope
No Label claw-code-done
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 groq hermes kimi manus perplexity sonnet
No Assignees claw-code
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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