Skip to content

Add Kai - AI Assistant section to navigation and main AI page #855

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
jordanrburger wants to merge 7 commits into
base: main
Choose a base branch
from
Open

Add Kai - AI Assistant section to navigation and main AI page #855

jordanrburger wants to merge 7 commits into from

Conversation

@jordanrburger
Copy link
Contributor

@jordanrburger jordanrburger commented Dec 16, 2025

Add Comprehensive Kai AI Assistant Documentation

Overview:
Added complete documentation structure for Kai, Keboola's embedded AI assistant, splitting content into focused, user-friendly sections.

New Pages Created:

  • /ai/kai-assistant/ - Main overview and introduction
  • /ai/kai-assistant/getting-started/ - Access requirements and first steps
  • /ai/kai-assistant/use-cases/ - Detailed examples and practical applications
  • /ai/kai-assistant/best-practices/ - Effective prompting and workflow guidance
  • /ai/kai-assistant/technical/ - Architecture, security, and deployment details

Key Features:

  • User-focused structure: Organized by user journey from introduction to advanced usage
  • Practical examples: Real prompts and workflows for common data engineering tasks
  • Clear differentiation: Explains relationship between Kai and MCP Server
  • Security emphasis: Covers governance, audit trails, and data protection
  • Navigation integration: Added hierarchical menu structure under AI Features

@jordanrburger jordanrburger self-assigned this Dec 16, 2025
jordanrburger
jordanrburger commented Dec 16, 2025
View reviewed changes
@jordanrburger jordanrburger reopened this Jan 8, 2026
cjayyy
cjayyy reviewed Jan 19, 2026
View reviewed changes
.playwright-mcp/kai-tool-response.png Outdated
Copy link
Contributor

@cjayyy cjayyy Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👎

@davidesner
Copy link
Contributor

davidesner commented Jan 28, 2026 •
edited
Loading

@jordanrburger I went through the docs locally:

I think we for sure need to add reference to the privacy policy or include a dedicated page like this https://github.com/keboola/connection-docs/pull/856/changes#diff-b504d79105e6b09adfd1804afe56a570a7f3e3cf82e8e3a14bf895a8ff6dd3af. This is imo very important to say loudly-> no training, data residency, compliance.

It would be nice to add the generic video with use cases to the main Kai page

Then this (prompt:) ):

  • Mention the available hotkeys -> A to open the (recent) chat window , SHIFT + A to open new chat
  • Update rate limiting: Every user will have 150 turns (user messages) per month per project for free. It resets every calendar month. If they need more they can reach out to support and we will need to deal with them individually (we have the technical option to set the limit per project). PAYG has lower limit of 15 messages per user per month
    • Users will see the rate limit usage in the chat UI
  • Elaborate more on contextual awareness and follow mode. That the agent has also a context of what the users sees in the UI and user can also follow along as the agent works with configurations. Refer to the implementation to understand more (ui repo path)
  • Expand tips with Don't type secrets in chat. KAI uses secure forms for credentials
  • Describe how to enable it. It is no longer private beta but public beta:
    • Every user will be able to see the Kai button in every project (if the stack has the appropriate feature, effectively excluding STs). It is also possible to enable it through settings -> features
    • Only Organization Admins will be able to enable the feature straight from the chat screen. Others will have to reach out to their org admins or our support if unsure.
  • remove .playwright folder

The Kai Use Cases & Examples would deserve the video (generated). I am not so sure the prompt examples are too useful. I will for sure not copy paste these prompts and it's quite hard to read. At least I would think about the page structure so it looks nicer.

@jordanrburger
Copy link
Contributor Author

jordanrburger commented Jan 28, 2026 •
edited
Loading

@davidesner - Sadly, I think one issue with the videos in the docs is that I don't think we can auto-play them and I'm not sure how easily they can even be embedded.

I agree with all the rest, though. Updating it now.

@jordanrburger jordanrburger marked this pull request as ready for review January 28, 2026 16:31
jordanrburger and others added 5 commits January 28, 2026 17:31
@jordanrburger
Add Kai - AI Assistant section to navigation and main AI page
ec1b74c
@jordanrburger
Update Kai assistant documentation: remove unsupported regions and re…
c1b2fa1 
…sponse types, clarify action approval requirements, and enhance descriptions of capabilities and integration setup.
@jordanrburger
Remove technical documentation for Kai assistant, including architect…
68a78d2 
…ure, security, deployment, and integration details. Update use case example to reflect changes in error message handling for job failures.
@jordanrburger
Update Kai assistant documentation: remove outdated sections, enhance…
d7653fd 
… best practices for new users, and streamline troubleshooting guidance. Revise navigation structure to reflect changes in content organization.
@jordanrburger @claude
Update Kai documentation for public beta: add hotkeys, rate limits, c…
feb6194 
…ontextual awareness, and enablement instructions

- Update from Private Beta to Public Beta with enablement details
- Add keyboard shortcuts (A for recent chat, Shift+A for new chat)
- Update rate limits: 150 turns/month (free), 15/month (PAYG)
- Add Contextual Awareness & Follow Mode section with implementation details
- Add security tip about using secure forms for credentials
- Remove .playwright-mcp folder and add to .gitignore

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@davidesner
Copy link
Contributor

davidesner commented Jan 29, 2026 •
edited
Loading

@davidesner - Sadly, I think one issue with the videos in the docs is that I don't think we can auto-play them and I'm not sure how easily they can even be embedded.

I agree with all the rest, though. Updating it now.

I usually convert them to gif, that works. Here's an example https://help.keboola.com/ai/mcp-server/

@jordanrburger
Copy link
Contributor Author

jordanrburger commented Jan 29, 2026

I usually convert them to gif, that works. Here's an example https://help.keboola.com/ai/mcp-server/

Yeah, then we just have a ~15 second limit. I'll try to recreate the capabilities video to be a little shorter.

jordanrburger and others added 2 commits January 29, 2026 12:35
@jordanrburger @claude
Add Capabilities GIF to Kai use cases page
4c02ef3 
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@jordanrburger @claude
Add Kai - AI Assistant to home page AI section
9cb21b0 
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@jordanrburger
Copy link
Contributor Author

jordanrburger commented Jan 29, 2026

Okay, the .gif has been added. Now, I'm debating whether or not we should include an FAQ page in addition to what we already have.

davidesner
davidesner reviewed Jan 30, 2026
View reviewed changes
ai/kai-assistant/getting-started.md

## Rate Limits

Each user receives **150 turns (messages) per month per project** on the free tier. The limit resets at the beginning of each calendar month.
Copy link
Contributor

@davidesner davidesner Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jordanrburger on the free tier sounds misleading. Contracted customers get 150 messages, PAYG less

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cjayyy cjayyy cjayyy left review comments

@davidesner davidesner davidesner left review comments

At least 1 approving review is required to merge this pull request.

Assignees

@jordanrburger jordanrburger

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@jordanrburger @davidesner @cjayyy