Skip to content

spec(agent-provider-chain): v3 -- a Kie route right after zai - #8180

Merged
gHashTag merged 1 commit into
masterfrom
claude/agent-provider-kie
Oct 9, 2026
Merged

gHashTag merged 1 commit into
masterfrom
claude/agent-provider-kie

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Closes #8179

What

automation/agent-provider-chain v3: a Kie route right after zai.

  • ORDER_DEFAULT = zai,kie,zai-lite,nemotron,reserve,ollama, PROVIDERS 6.
  • Kie: key KIE_AI_API_KEY, base https://api.kie.ai/<model>/v1, model gemini-2.5-flash (override KIE_CHAT_MODEL), tools declared, vision/audio not declared, no thinking block, AGENT_MODEL never renames it, max_tokens 8192.
  • New fns kie_available, ceiling_for (which providers send max_tokens).

Why

The 999 agent turn of 2026-10-09 ended in "no model provider answered": zai 429 code 1305, nemotron silent 120 s, zai-lite silent 60 s, reserve 402. The owner asked to turn the agent on through Kie, the vendor the project already funds for every image, video, song and voice.

Checks

  • t27c test-report: 10 tests, 10 pass (2 pre-existing constant-only tests and the VERSION test fold at compile time, as in sibling specs).
  • Negative controls on a scratch copy, 8/8 caught: kie after nemotron, kie available without key, kie without ceiling, zai with a ceiling, vision declared, max 1024, PROVIDERS 5, VERSION 2.
  • Sealed; NOW entry added.

Host PR in 999-multibots-telegraf follows (provider.ts).

🤖 Generated with Claude Code

https://claude.ai/code/session_01FJktaYxNrfAUdxSwdQw3gV


Generated by Claude Code

The 999 agent turn of 2026-10-09 ended with no provider answering (zai
1305, nemotron and zai-lite timed out, reserve 402). Kie is the vendor the
project already pays for media; it serves Gemini over an OpenAI-compatible
chat endpoint. v3 puts it second: free zai first, then a funded vendor.
gemini-2.5-flash by default, tools declared, vision/audio not, max_tokens
8192. New fns kie_available and ceiling_for; 8 negative controls caught.

Closes #8179

phi^2 + 1/phi^2 = 3 | TRINITY

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FJktaYxNrfAUdxSwdQw3gV
This was referenced Oct 9, 2026
@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-09 12:58:00 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 48
PRs with All Checks Green 2
READY 0
FAILING 48
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 48 + 0 + 0 = 48, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=3c0ade9e73e4 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

gHashTag commented Oct 9, 2026

Copy link
Copy Markdown
Owner Author

t27b-native-ratchet is red here. It is not this PR's: it is a non-required check that is red on master too, and this PR only changes one spec under specs/automation/ (plus its seal and NOW entry), which the native ratchet does not read. No fix is ported. The four required checks (validate, check-linked-issue, parse-ratchet, own-language) gate the merge.


Generated by Claude Code

@gHashTag
gHashTag merged commit 3281618 into master Oct 9, 2026
28 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

agent-provider-chain v3: a Kie route right after zai

2 participants