docs: add nanobot and Kilo Code integration guides - #99
Open
MVS-source wants to merge 1 commit into
Open
Conversation
Both integrations were merged upstream (HKUDS/nanobot#4861 on 2026-07-09, Kilo-Org/kilocode#13169 on 2026-08-17) but had no page here. Configuration in both guides is taken from the merged upstream code rather than reconstructed: nanobot's provider registry entry and its docs/providers.md section, and the Eden AI page in kilo-docs. Every model id cited was checked against the live /v3/models catalogue.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the two missing developer docs for merged Eden AI integrations. Both are built-in providers upstream, no OpenAI-compat workaround needed:
nanobot.mdxkilo-code.mdxThese were the two largest audiences among our merged integrations with no page here. Same format as the last integration PRs (#73 to #82): frontmatter plus
<TechArticleSchema>,docs.jsonnav registration, and acurrentColorline icon in the style of the existing small ones.Where the configuration comes from
Not reconstructed from memory. Each guide's configuration is lifted from the merged upstream code:
ProviderSpecwe added tonanobot/providers/registry.py(backend="openai_compat",env_key="EDENAI_API_KEY",default_api_base="https://api.edenai.run/v3",is_gateway=True) and the section we added to their owndocs/providers.md. Config path~/.nanobot/config.jsonand the${ENV_VAR}placeholder support come from theirdocs/configuration.md.ai-providers/edenai.mdpage we contributed tokilo-docs, which covers the VS Code flow, the CLI flow,auth.json, declaring a model that is not in the picker, the EU base URL and the@euvariants.Verification
/v3/modelscatalogue. Nine ids, zero dead.docs.jsonparses, and the two pages land last in their groups, matching the add-order those groups already use.Two things worth splitting off
anthropic/claude-sonnet-4-5is no longer served, and it is our house example in 13 of 24 integration pages. I checked all 38 model ids cited acrossv3/integrations/*.mdxagainst the live catalogue: 10 are dead.anthropic/claude-opus-4.7is a typo, the real id uses dashes (claude-opus-4-7) and exists.openai/gpt-5.1-codex*exist underazure/, notopenai/.cohere/command-r-plusneeds its date suffix.meta/llama-3-70bandmeta/llama-3-8bhave nometa/vendor at all.openai/dall-e-3is absent from/v3/images/modelstoo, so it is genuinely gone.For the recurring one,
anthropic/claude-sonnet-latestis a real servable alias resolving toclaude-sonnet-5, which is the fix that will not rot again. I used it in the nanobot guide. Happy to do that sweep as a separate PR.Execution Testsis red on every PR in this repo since around 11 August, including this one. It dies inpytest_sessionstartbefore any test runs, ontests/helpers/api.pygetting401 Unauthorizedfromhttps://staging-api.edenai.run/v2/user/custom_token/. Same error on #90 through #98. Last green run was #88 on 4 August. Looks like the staging credential in the CI secrets expired or was rotated.