Conversation
Updated references from 'Kai' to 'KAI' and improved descriptions for clarity and context awareness. Added sections on usage and support.
Updated the 'Getting Started' guide for Kai, changing the title and permalink, and enhancing the content to include detailed use cases and examples for data engineering tasks.
Updated use cases for Kai assistant with additional tips and examples for data engineering tasks.
ai/kai-assistant/index.md
Outdated
|
|
||
| ### Embedded Experience | ||
| Kai is built into the Keboola platform with no installation required. It's already authenticated and understands your current location within the platform, making it seamless to use. | ||
| | Feature | ChatGPT / Claude | KAI | |
There was a problem hiding this comment.
@jerab111 @jordanrburger this section makes me confused. We are comparing KAI with Other AI tools but without MCP? If so, it feels like comparing apples to oranges. I don't see the value in saying that Keboola in platform assistant is different than plain ChatGPT or Claude. On the other hand mentioning explicitly Claude, which is most heavily used in combination with MCP server makes the listed differences seem untruthful.
Question how is KAI different from Claude imo implies the use of MCP server and is valid, however this section does not answer it. Maybe it would be enough to just be explicit that we are talking about general AI assistant/llm with no MCP connection. Because it is true that it is a common pattern for people to generate SQL in ChatGPT and then copy-paste it back.
ai/kai-assistant/index.md
Outdated
| |---------|------------------|-----| | ||
| | **Context** | No access to your project | Full access to configs, schemas, job logs | | ||
| | **Actions** | Can only suggest code | Creates, modifies, and runs components | | ||
| | **Authentication** | Manual setup required | Already authenticated in platform | |
There was a problem hiding this comment.
If we are comparing generic AI Assistant with no MCP than authentication is not a valid difference.
ai/kai-assistant/index.md
Outdated
|
|
||
| ## See KAI in Action | ||
|
|
||
| Animated video displaying something like this: |
There was a problem hiding this comment.
Videos in docs seems like a bad idea to me. It's impossible to keep it up to date. It's something that belongs on the website, not the docs.
| - url: /ai/kai-assistant/technical/ | ||
| title: Technical Details |
There was a problem hiding this comment.
You removed the page, but left it in the navigation. This needs to be removed.
Updated the KAI assistant documentation to reflect branding changes and improve clarity.
3 participants
I believe:
Users don't read sequentially - they scan for what they need NOW. That's why it's better to split content in more pages (getting started; use cases; best practises; troubleshooting) and edit the structure
Every extra section = 20% higher abandonment
index.md - aimed for more user friendly approach + initial visual.
use-cases - aimed for different approach - content might need work
best-practises - really well done by Jordan!
-added troubleshooting - we need it, but the content is pure claude's work
added security and privacy.md - some content there might be junk, but we 100% need it
deleted technical.md - i don't think we need it