Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ This will work with any resource yaml manifest, or link to a file containing the
It will also work with individual resource names, or a list of resource names.
```

Ok, now we have a much better prompt. The agent will now better understand how and when to use the tools, in response to it's own internal queries, or user prompts.
Ok, now we have a much better prompt. The agent will now better understand how and when to use the tools, in response to its own internal queries, or user prompts.

We can still do better. One major thing that was left out of the above prompt is the agent's behavior. LLMs are statistical models that output the most likely next token, this means that being explicit about the agent's behavior makes it more likely that the agent will behave as expected.

Expand Down
5 changes: 2 additions & 3 deletions src/app/docs/kagent/operations/debug/page.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,8 @@ This should give you the reason why the agent was rejected.
If it's not there, you can try to get the logs of the agent:

```shell
kubectl logs -n kagent deployment/kagent -c controller
kubectl logs -n kagent deployment/kagent -c app
kubectl logs -n kagent deployment/kagent-controller
kubectl logs -n kagent deployment/kagent-ui
```

You can also set the logging level to `DEBUG` to get more detailed logs from the agent pod. To do that, edit the agent resource and add the `LOG_LEVEL` environment variable to the `deployment` field:
Expand All @@ -46,4 +46,3 @@ spec:
```

You can also ask for help in the [community](https://discord.gg/Fu3k65f2k3) or log an issue on [GitHub](https://github.com/kagent-dev/kagent). You can create a bug report using the kagent CLI by running `kagent bug-report`. Before attaching files to your bug report, make sure they don't contain any sensitive information!