From 69ff97382bba737bfc0446c44bc9bdd4e65e7b40 Mon Sep 17 00:00:00 2001 From: Art Berger Date: Thu, 4 Dec 2025 13:56:44 -0500 Subject: [PATCH] Revise GS - based on user feedback Signed-off-by: Art Berger --- .../getting-started/quickstart/page.mdx | 39 ++----------------- .../kagent/introduction/installation/page.mdx | 4 +- 2 files changed, 5 insertions(+), 38 deletions(-) diff --git a/src/app/docs/kagent/getting-started/quickstart/page.mdx b/src/app/docs/kagent/getting-started/quickstart/page.mdx index 915bfc4..fa70184 100644 --- a/src/app/docs/kagent/getting-started/quickstart/page.mdx +++ b/src/app/docs/kagent/getting-started/quickstart/page.mdx @@ -44,10 +44,10 @@ To run the AI agents you'll also need an [OpenAI](https://openai.com) API key. Y curl https://raw.githubusercontent.com/kagent-dev/kagent/refs/heads/main/scripts/get-kagent | bash ``` -3. Install kagent to the cluster by using the CLI. By default, kagent installs a demo profile with agents and MCP tools preloaded for you. If you don't want these default agents, include the `--profile minimal` flag. +3. Install kagent to the cluster by using the CLI. The following command installs a demo profile with agents and MCP tools preloaded for you. If you don't want these default agents, include the `--profile minimal` flag. ```bash - kagent install + kagent install --profile demo ``` Example output: @@ -143,41 +143,8 @@ Interact with kagent in your terminal. ```shell kagent invoke -t "What Helm charts are in my cluster?" --agent helm-agent ``` - - Example output: - - ```console - Event Type: ToolCall(s) - Source: helm_agent - +---+--------------------+-----------------------------------------+ - | # | NAME | ARGUMENTS | - +---+--------------------+-----------------------------------------+ - | 0 | helm_list_releases | {"all_namespaces":true,"deployed":true} | - +---+--------------------+-----------------------------------------+ - ---------------------------------- - - Event Type: TextMessage - Source: helm_agent - - I found the following Helm release deployed across all namespaces: - - - **Release Name:** kagent - - **Namespace:** kagent - - **Revision:** 11 - - **Updated:** 2025-03-13 19:18:49 UTC - - **Status:** Deployed - - **Chart:** kagent-v0.0.18-4-g4926e59-dirty - - If you need more details about any specific release, let me know! - ---------------------------------- - - Usage: Prompt Tokens: 6573, Completion Tokens: 229 - helm-agent--test> - ``` - -As you can see from the example, the agent found the `kagent` Helm chart release. If anything else is running in your cluster, it will probably find that too. -Now, keep chatting with the agent to see what other things it can do :) + In the output, verify that the agent found the `kagent` Helm chart release. If any other Helm charts are in your cluster, it finds those, too. Keep chatting with the agent to see what other things it can do :) ## Next Steps diff --git a/src/app/docs/kagent/introduction/installation/page.mdx b/src/app/docs/kagent/introduction/installation/page.mdx index f47c86b..313e7b0 100644 --- a/src/app/docs/kagent/introduction/installation/page.mdx +++ b/src/app/docs/kagent/introduction/installation/page.mdx @@ -40,10 +40,10 @@ Install kagent by using the kagent CLI or Helm. curl https://raw.githubusercontent.com/kagent-dev/kagent/refs/heads/main/scripts/get-kagent | bash ``` -3. Install kagent to the cluster by using the CLI. By default, kagent installs a demo profile with agents and MCP tools preloaded for you. If you don't want these default agents, include the `--profile minimal` flag. +3. Install kagent to the cluster by using the CLI. The following command installs a demo profile with agents and MCP tools preloaded for you. If you don't want these default agents, include the `--profile minimal` flag. ```bash - kagent install + kagent install --profile demo ``` ```console