Repoint kbagent plugin install to the AI Kit marketplace - #1095
Repoint kbagent plugin install to the AI Kit marketplace#1095claude[bot] wants to merge 17 commits into
Conversation
The kbagent Claude Code plugin now ships from the keboola/ai-kit marketplace (keboola-claude-kit) instead of the CLI's own marketplace (keboola-agent-cli). - cli/for-agents: update the install code block to `/plugin marketplace add keboola/ai-kit` + `/plugin install kbagent@keboola-claude-kit`, reword the lede that called it "the CLI's own marketplace", and refresh the marketplace name in the page's provenance comment. - ai/ai-kit: list `kbagent` alongside the other plugins in the "enable the plugins you need" block. The CLI's on-disk config directory (~/.config/keboola-agent-cli) and the CLI install instructions themselves are unchanged.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The CLI docs were behind the product: they pointed Windows readers at a git+https uv install, led with a Storage API token when browser login now needs none, and said nothing about per-client setup at all. - cli/getting-started: replace the Windows tab with the canonical PowerShell path from keboola/cli's README (winget uv, release wheel, `uv tool update-shell`, open a new shell), plus the Git-bash and self-contained-zip alternatives and the package-manager warning. Add the POSIX PATH note. Rewrite Step 2 to lead with `auth login --register-projects` and demote the token to the CI / headless route, prompting for it instead of passing `--token`. - cli/for-agents: add a "Set up your client" section covering Claude Code, Claude Desktop, the plugin-less clients (Cursor, VS Code, Codex, Devin Desktop) and a plain terminal, and describe `/kbagent:setup` and why a plugin slash command cannot be skipped or run in a shell. - ai/ai-kit: qualify the kbagent install with its marketplace and link across to the per-client steps. Claude Desktop's chat accepting /kbagent:setup is flagged with a VERIFY comment; it has not been checked against a live build. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Tested against live clients on 2026-08-26, which contradicts what the
previous commit assumed: Cursor has a marketplace, Claude Desktop has no
slash-command surface at all, and /kbagent:setup completes nowhere.
- Claude Desktop: no /plugin and no /kbagent:setup ("Unknown command" and
"/plugin isn't available in this environment"), so its section is the
manual flow. Menu path corrected to Customise -> Plugins -> Add -> Add
from marketplace, install via the plus button on the card titled
"Kbagent". Drops the VERIFY comment the fact replaces.
- Cursor: promoted from the plugin-less group to its own section, with
the Import from Github full-URL requirement and the useless
[invalid_argument] Error the short form returns.
- /kbagent:setup: demoted to a shortcut that stops at the sign-in and
hands you a terminal command, with keboola/cli#704 as the tracking
issue for in-chat login. The manual sequence is the happy path again.
- Adds the once-per-machine sign-in tip (all clients share the local
config) and a line on asking the agent in plain language, which the
plugin's skill handles.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…t' into agent/kbagent-marketplace-repoint
Hand-testing each client showed the plugin installs everywhere, not only in Claude Code: Claude Desktop, Cursor, VS Code and the ChatGPT app all read the Claude plugin format that keboola/ai-kit publishes. The page claimed the opposite for VS Code and Codex, so a reader on those clients was told to skip the plugin that would have worked. Each client reaches it differently (short repo form vs full GitHub URL, a command palette entry, Developer mode), so the routes are written out per client rather than generalised. The terminal half is shared, because install, connect and doctor are the same everywhere and all three need a real TTY. Also drops the Devin section (hidden from the product's own setup surface) and adds the marketplace-move step for readers who followed the old keboola/cli instructions.
Step 2 sent readers to Project Settings → API Tokens to mint a Full Access token by hand. The UI now has a page that builds the whole `project add` command for the reader's project and stack, and can put a scoped read-only token in it, so the docs point there instead of walking through a token form they cannot fill in for you. Interactive setups need no token at all, which was the bigger gap: `project add` signs you in through the browser. The token route stays for CI and the features that still require a static token.
The install block already had kbagent in it, but the page still described three plugins and only documented those three, so the one plugin readers arrive for had no entry. It also claimed keboola-claude-kit is the only marketplace Keboola operates, which we cannot vouch for; what matters is that it is the one to install from. The CLI landing page called the same thing "the Claude Code plugin".
|
Reviewed against keboola/cli main, the live keboola/ai-kit marketplace, and issue #704. Mechanics are fine ( Blocking
Non-blocking
|
|
@eruveo two things in 1. Three lines disagree about Claude CodeLine 31: Line 33: "The other four clients... also cannot finish the sign-in it performs" (implies Claude Code can) Line 35, your HTML comment: "the login hand-off back to a terminal was reproduced in Claude Code, Cursor and Claude Desktop" keboola/cli#704, which line 33 cites, has a table saying Claude Code → finishes → no. So line 31 says one thing, and lines 33/35 plus #704 say another. Which is right? You hand-tested this, I didn't, and #704 was only filed this morning so it may already be stale. One of the two is wrong either way. If #704 is right, line 31 could read:
2. The
|
The branch's four CLI pages were written against an older main; merging now so the review fixes land on top of current content rather than diverging further.
Step 2 told readers `project add` would sign them in through the browser. It does not. In keboola/cli main `project add` resolves a token from `--token`, then `KBC_TOKEN`, then a hidden TTY prompt, and errors out. A reader arriving without a token hit that prompt with nothing on the page telling them what to type, and this branch had already removed the token-creation walkthrough. Browser sign-in is the separate `auth login` + `auth register-projects` pair, so document both routes and say which is which. The Agentic CLI settings page is feature-flagged off until launch while these docs deploy on merge, so the token route now also names Settings → API Tokens as the way in for anyone who cannot see it. Drops the orphaned screenshot the removed walkthrough used, and the internal VERIFY note that was shipping into the public page.
The /kbagent:setup section said the command "signs you in", while the sentence below it and the page's own HTML comment said the browser hands back to a terminal. keboola/cli#704 settles it: no client completes the sign-in in-chat, its table marks Claude Code "finishes: no". The command starts the browser sign-in and the reader finishes it in their terminal. Drops the customer-facing link to #704. It is an open issue whose title reads as an admission that the documented flow does not work, and this page links no other GitHub issues. The reference stays in the HTML comment. The "other four clients" sentence said they cannot run the command and then explained they cannot finish its sign-in, so it now just says they cannot run it and points at the terminal route. Also: - `keboola-cli` is a current v1.1.1 project-review toolkit built on the older `kbc` sync CLI, not "the unrelated legacy kbc CLI". - The terminal steps deferred to getting-started's Step 2 rather than forking its `project add` example under a different alias, and they no longer repeat the "no token needed interactively" claim that `project add` does not honour. - The sign-in tip contradicted every client section's unconditional "Do the terminal steps above", so it is now conditional on `project list`. - Two provenance comments were attesting reviews that did not cover what sits under them: Padak's v0.66.1 review predates the `keboola-claude-kit` marketplace, and "verified 2026-07-13" was covering 2026-08-26 claims.
Two pre-existing lines here disagreed with getting-started once Step 2 grew a browser-login route. The "in one minute" block demanded `--token YOUR_TOKEN` from a reader who has no token yet, and the page claimed kbagent "never needs a browser" one section later. The quickstart now signs in the way Step 2 does, and the browser sentence says what is actually true: one browser round-trip to sign in, or a Storage API token to skip it.
This branch pins the page to keboola/ai-kit and asserts a plugin count, so the count has to be right. The live `keboola-claude-kit` marketplace ships seven plugins, and none of them is named `developer`. The page promised four, told readers to run `/plugin install developer`, and linked `plugins/developer`, which 404s. Documents the four plugins that were missing (keboola-cli, keboola-git, sl-toolkit, powerbi-to-sl), drops the Developer Plugin section along with the intro and best-practice sentences that referred to it, and qualifies every install string with `@keboola-claude-kit` so they work as written.
|
@Iamfle4ka @KaroEverling both reviews were right on the load-bearing claims. All twelve items are addressed across four commits. Base was behind On the Iamfle4ka — blocking
Iamfle4ka — non-blockingAll four done: Windows KaroEverling
One thing I did not do, deliberatelyDocumenting I bumped it to v0.91.0 locally to see what happens, then reverted: #1044 ( So the three new Spotted in passing, not changed
@KaroEverling on keboola_com#531 / #538: outside this repo, so I can't touch them from here. The wording to carry over is "starts the browser sign-in… You finish the sign-in in your terminal." Checks
(The Astro dev server on :4321 was 500ing on every page including the homepage and untouched routes after the merge pulled in the new content files. Stale server, not this branch — verified against a fresh build of the same tree.) |
The `auth login` lines carried `kbagent-check: skip-next` because the checked-in reference was v0.76.1, which predates the `auth` group. Bumping it to v0.91.0 removes the reason for all three skips. The two regressions that bump exposes both resolve by deletion rather than by guessing at a replacement, which is what made them look risky: - `kbagent tool` is gone, and "tool" appears nowhere in the v0.91.0 reference. Nothing succeeded it, so the three places offering it as a way to call MCP tools were offering a command that does not exist. - `kbagent doctor` now takes no options at all, so `--fix` cannot be described as repairing anything. Troubleshooting says what doctor reports and leaves the fixes to the manual steps already listed under it. The `--version` sample moves to v0.91.0 with the reference, and its provenance comment stops pinning a version it no longer shows. The remaining skips are the chat prompts, which are prompts rather than commands and always will be.
Removed on Michal's call. This reverses one of Jordan's two conditions for merging #1015 (PRDCT-490, commit 968e0cb), so it is called out in the PR body rather than left to be found in a diff. Nothing else Keboola ships labels kbagent beta: the keboola.com /cli page does not, keboola/cli's README does not, and the product badges the connect card NEW where Kai gets a Beta badge. The docs carried the label alone.
Brings the kbagent docs in line with what the product shows on Settings → Developer settings → Agentic CLI, after each AI client was hand-tested. Then corrected in review: two claims that came out of that testing were wrong.
Everything that changed
keboola/cli,kbagent@keboola-agent-clikeboola/ai-kit,kbagent@keboola-claude-kit, plus/plugin marketplace remove keboola-agent-clifor anyone on the old oneproject add,doctor), then the client's own plugin UIproject addprompts for a token with hidden input, which needs a real TTY. It cannot be handed to an agentkbagent doctor~/.claude/plugins/cache, so it is blind to a Cursor or VS Code install and cannot vouch for the plugin half/kbagent list my projectskbagent list my projects, no leading slash/kbagentwith "Unknown command"/kbagent:setupauth loginneeds a human at a browser; keboola/cli#704 marks every client, Claude Code included, as unable to finish it in-chatauth login --register-projectsauth login+auth register-projectsfor the browser,project add --tokenfor a static tokenproject addresolves--token, thenKBC_TOKEN, then a hidden prompt. A reader with no token had nothing to typedeveloperplugindeveloperdeveloper; its link 404'dcli/index.mdquickstart--token, said kbagent "never needs a browser"keboola-clikbcCLI"kbcsync CLIkbagentin every list$veremptyVERIFY(owner: Padak)and a #704 repro note contradicting the proseproject list, defers to Step 2skip-nextmarkers forauthauthgroupkbagent toolkbagent doctor --fixdoctorreports, the manual steps below fixdoctortakes no options at all in v0.91.0--versionsamplekbagent v0.66.0kbagent v0.91.0cli/index.md:::caution[Beta]Still open
kbagent list my projectskeeps askip-next. It is a chat prompt, not a command, so the gate will never know it./cli/for-agents/was not renamed. It returns 200 and keboola.com's hero links to it, so/cli/ai-agents/would 404.npm run buildclean (361 pages) ·node scripts/check-cli-reference.mjs0 findings · base merged frommain, no conflicts.🤖 Generated with Claude Code