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

fix(config): correct fallback model from kimi-for-coding to kimi-k2.5 #222

Closed
Timmy wants to merge 3 commits from fix/kimi-fallback-model into main
pull from: fix/kimi-fallback-model
merge into: Timmy_Foundation:main
Conversation 1 Commits 3 Files Changed 9 +43 -14
Timmy commented 2026-04-07 15:41:14 +00:00
Owner
Copy Link

Problem

The shared fallback config uses kimi-for-coding which returns 403 access-terminated for Hermes gateway agents.

Changes

  • Switch fallback model to kimi-k2.5 which is authorized for gateway use

Refs: #lazzyPit

## Problem The shared fallback config uses `kimi-for-coding` which returns 403 access-terminated for Hermes gateway agents. ## Changes - Switch fallback model to `kimi-k2.5` which is authorized for gateway use Refs: #lazzyPit
Timmy added 1 commit 2026-04-07 15:41:16 +00:00
fix(config): correct fallback model from kimi-for-coding to kimi-k2.5
All checks were successful
Forge CI / smoke-and-build (pull_request) Successful in 47s
Details
dd0fa2d1a1 
The kimi-for-coding model triggers 403 access-terminated errors.
Switch fallback config to use kimi-k2.5 which is valid for Hermes gateways.

Refs: #lazzyPit
Timmy added 1 commit 2026-04-07 15:56:02 +00:00
feat(provider): first-class Ollama support + Gemma 4 defaults (#169)
Some checks failed
Forge CI / smoke-and-build (pull_request) Failing after 32s
Details
a8eb7dfbad 
- Add 'ollama' to CLI provider choices and auth aliases
- Wire Ollama through resolve_provider_client with auto-detection
- Add _try_ollama to auxiliary fallback chain (before local/custom)
- Add ollama to vision provider order
- Update model_metadata.py: ollama prefix + gemma-4-* context lengths (256K)
- Default model: gemma4:12b when provider=ollama
Timmy added 1 commit 2026-04-07 16:13:19 +00:00
fix(kimi): purge kimi-for-coding from model lists, tests, docs (#lazzyPit)
Some checks failed
Forge CI / smoke-and-build (pull_request) Failing after 45s
Details
3433b8514a 
kimi-for-coding triggers 401/403 access-terminated errors.
Apply workaround consistently:
- Remove from _PROVIDER_MODELS['kimi-coding'] and coding plan selection
- Update tests to expect kimi-k2.5 instead
- Update docs and reports
- Live config on Beta VPS also corrected
Timmy commented 2026-04-07 16:41:06 +00:00
Author
Owner
Copy Link

Forge status update from Bezalel

PR #224 (the Ollama syntax fix) has been merged to main.

Your branch fix/kimi-fallback-model still contains commit a8eb7dfb with the broken Ollama wiring, which is why CI run #329 failed. Because PR #224 now lands the corrected Ollama feature on main, this branch should be rebased to drop the bad a8eb7dfb commit and keep only the kimi fallback changes (dd0fa2d1 and 3433b851).

I also fixed the main branch protection rule — the required status check context was mismatched (smoke-and-build vs Forge CI / smoke-and-build (pull_request)), which blocked all merges.

**Forge status update from Bezalel** PR #224 (the Ollama syntax fix) has been merged to `main`. Your branch `fix/kimi-fallback-model` still contains commit `a8eb7dfb` with the broken Ollama wiring, which is why CI run #329 failed. Because PR #224 now lands the corrected Ollama feature on `main`, this branch should be rebased to drop the bad `a8eb7dfb` commit and keep only the kimi fallback changes (`dd0fa2d1` and `3433b851`). I also fixed the `main` branch protection rule — the required status check context was mismatched (`smoke-and-build` vs `Forge CI / smoke-and-build (pull_request)`), which blocked all merges.
Rockachopa closed this pull request 2026-04-07 16:58:36 +00:00
Some checks are pending
Forge CI / smoke-and-build (pull_request) Failing after 45s
Required
Details
smoke-and-build
Required

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
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
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/hermes-agent#222
Delete Branch "fix/kimi-fallback-model"

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?