v0.8 release docs by artberger · Pull Request #333 · kagent-dev/website

artberger · 2026-03-12T15:07:07Z

Follow up to #321, #332

Adds concepts, guides, and release notes for new 0.8 features, including:

Human-in-the-Loop (HITL) — tool approval gates and interactive ask_user tool.
Agent Memory — vector-backed long-term memory for agents.
Go ADK runtime — new Go-based agent runtime for faster startup and lower resource usage.
Agents as MCP servers — expose A2A agents via MCP for cross-tool interoperability.
Skills — markdown knowledge documents loaded from OCI images or Git repositories.
Go workspace restructure — the Go codebase is split into api, core, and adk modules for composability.
Prompt templates — reusable prompt fragments from ConfigMaps using Go template syntax.
Context management — automatic event compaction for long conversations.
AWS Bedrock support — new model provider for AWS Bedrock.

iplay88keys · 2026-03-13T18:59:31Z

src/app/docs/kagent/resources/helm/page.mdx

@@ -121,9 +121,6 @@ A Helm chart for kagent, built with Google ADK
 | database.postgres.url | string | `"postgres://postgres:kagent@pgsql-postgresql.kagent.svc.cluster.local:5432/postgres"` |  |


There are additional fields as part of the work to remove sqlite. See the values file in the PR.

iplay88keys · 2026-03-13T19:00:47Z

src/app/docs/kagent/resources/release-notes/page.mdx

+- The `database.type` configuration option has been removed.
+- SQLite-related Helm values (`database.sqlite.*`) have been removed.
+- A PostgreSQL instance with pgvector is now bundled in the Helm chart by default.
+- The bundled PostgreSQL is deployed automatically when both `database.postgres.url` and `database.postgres.urlFile` are empty.


Probably worth mentioning the additional settable fields for configuring the bundled postgres image, resources, username/password, etc. See the values file in the PR.

…ntation Add 17 new MDX pages covering: - Core Concepts: tools ecosystem, human-in-the-loop, agent memory, prompt templates, multi-runtime (Go/Python ADK), git-based skills, context management - Resources: full Agent CRD reference (Agent, ModelConfig, RemoteMCPServer, MCPServer, ModelProviderConfig) - Solo Enterprise: overview, installation, security & access control, multicluster federation, observability (OTel/ClickHouse), enterprise UI, BYO agent frameworks (ADK/CrewAI/LangGraph), model providers, tools & MCP Update navigation.json with entries for all new pages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

1. All tool names wrong — kubectl_* prefix should be k8s_*, many tools fabricated or misnamed 2. Memory config YAML wrong — uses nonexistent enabled/embeddingProvider fields; should be modelConfig/ttlDays 3. Context management YAML wrong — eventsCompaction.enabled should be compaction with compactionInterval/etc. 4. Prompt template dataSources wrong — configMapRef.name should be flat kind/name/alias fields 5. BYO agent YAML nesting wrong — image/replicas should be under byo.deployment, not at byo level 6. Memory API endpoints wrong — uses path params but actual API uses query params, plus missing endpoints 7. OCI skills refs format wrong — refs is a string array, not objects with image key 8. Read-only mode (kagentTools.readOnly) — no evidence this exists 9. navigation.json indentation bug — line 292 lost leading whitespace Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

… items, namespace in YAML Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

…section Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

the rendering of the codeblock did not work Signed-off-by: Art Berger <art.berger@solo.io>

Signed-off-by: Art Berger <art.berger@solo.io>

- Concepts: add cards for Tools Ecosystem, Human-in-the-Loop, Agent Memory, Prompt Templates, Multi-Runtime, Git-Based Skills, Context Management - Getting Started: add Local Development card - Examples: add Agents via MCP, BYO CrewAI, BYO LangGraph cards - Resources: fix Helm chart href (/helm/helm -> /helm) Signed-off-by: Art Berger <art.berger@solo.io>

Signed-off-by: Art Berger <art.berger@solo.io>

Related to kagent-dev/kagent#1502 Signed-off-by: Art Berger <art.berger@solo.io>

Signed-off-by: Art Berger <art.berger@solo.io>

Signed-off-by: Yaniv Marom Nachumi <yanivmar@amdocs.com> Signed-off-by: Art Berger <art.berger@solo.io>

Signed-off-by: Art Berger <art.berger@solo.io>

kristin-kronstain-brown

I had lots of questions but I didn't see anything glaringly wrong.

kristin-kronstain-brown · 2026-03-19T11:55:15Z

src/app/docs/kagent/concepts/agent-memory/page.mdx

+- **Searchable.** Agents retrieve relevant memories via cosine similarity.
+- **Automatic.** Agents extract and save user intent, key learnings, and preferences without explicit user action.
+- **Time-bounded.** Memories expire after a configurable TTL (default 15 days).
+- **Shared storage.** Memory uses the same kagent database (PostgreSQL), not a separate database.


Suggested change

- **Shared storage.** Memory uses the same kagent database (PostgreSQL), not a separate database.

- **Shared storage.** Memory uses the kagent database (PostgreSQL), not a separate database.

I don't know why, but with same, I want it to say something like "Memory uses the same database as kagent..." Like with "same" I want an "as". Maybe a preference rather than a requirement.

kristin-kronstain-brown · 2026-03-19T11:56:47Z

src/app/docs/kagent/concepts/agent-memory/page.mdx

+
+To enable memory, set the `memory` field on the declarative agent spec. The `modelConfig` field references a `ModelConfig` object whose embedding provider generates memory vectors.
+
+You can also configure memory in the kagent UI when you create or edit an agent by selecting an embedding model and setting the memory TTL.


Should these be steps? It's not an overly complicated sentence but there is an "or" and an "and" on something that could potentially be steps.

Or are you saying that by running this YAML, then you can change these settings in the UI?

kristin-kronstain-brown · 2026-03-19T11:59:22Z

src/app/docs/kagent/concepts/agent-memory/page.mdx

+|------|-------------|
+| `save_memory` | Explicitly save a piece of information. |
+| `load_memory` | Search for relevant memories by query. |
+| `prefetch_memory` | Automatically run before response generation. |


Run what exactly? The agent?

kristin-kronstain-brown · 2026-03-19T12:01:17Z

src/app/docs/kagent/concepts/agent-memory/page.mdx

+
+### Viewing Memories
+
+In the kagent UI, you can view the memories that an agent has saved. This lets you inspect what the agent has learned and retained from past interactions.


Suggested change

In the kagent UI, you can view the memories that an agent has saved. This lets you inspect what the agent has learned and retained from past interactions.

In the kagent UI, you can view the memories that an agent has saved. With saved memories, you can inspect what the agent has learned and retained from past interactions.

kristin-kronstain-brown · 2026-03-19T12:02:21Z

src/app/docs/kagent/concepts/agent-memory/page.mdx

+
+## Limitations
+
+- **No per-memory deletion.** You can clear all memories for an agent, but you cannot delete individual memory entries.


Does clear mean the same thing as delete?

kristin-kronstain-brown · 2026-03-19T12:37:41Z

src/app/docs/kagent/resources/release-notes/page.mdx

+
+The `kagent-builtin-prompts` ConfigMap ships with five reusable templates: `skills-usage`, `tool-usage-best-practices`, `safety-guardrails`, `kubernetes-context`, and `a2a-communication`.
+
+For more information, see the [Agents](/docs/kagent/concepts/agents#prompt-templates) concept guide.


Suggested change

For more information, see the [Agents](/docs/kagent/concepts/agents#prompt-templates) concept guide.

For more information, see [Agents](/docs/kagent/concepts/agents#prompt-templates).

kristin-kronstain-brown · 2026-03-19T12:38:19Z

src/app/docs/kagent/resources/release-notes/page.mdx

+
+Long conversations can now be automatically compacted to stay within LLM context windows. You can configure the `context.compaction` field to enable periodic summarization of older events while preserving key information.
+
+For more information, see the [Agents](/docs/kagent/concepts/agents#context-management) concept guide.


Suggested change

For more information, see the [Agents](/docs/kagent/concepts/agents#context-management) concept guide.

For more information, see [Agents](/docs/kagent/concepts/agents#context-management).

Does the same link need be included in every paragraph?

kristin-kronstain-brown · 2026-03-19T12:39:14Z

src/app/docs/kagent/resources/release-notes/page.mdx

+
+**Migration:**
+
+If you were using the default SQLite backend, no migration is needed. The bundled PostgreSQL will be deployed automatically. You can optionally customize the bundled instance via `database.postgres.bundled.*` (storage size, image, credentials) as needed. See the [Database configuration guide](/operations/operational-considerations/#database-configuration) for details.


Suggested change

If you were using the default SQLite backend, no migration is needed. The bundled PostgreSQL will be deployed automatically. You can optionally customize the bundled instance via `database.postgres.bundled.*` (storage size, image, credentials) as needed. See the [Database configuration guide](/operations/operational-considerations/#database-configuration) for details.

If you were using the default SQLite backend, no migration is needed. The bundled PostgreSQL is deployed automatically. You can optionally customize the bundled instance via `database.postgres.bundled.*` (storage size, image, credentials) as needed. See the [Database configuration guide](/operations/operational-considerations/#database-configuration) for details.

kristin-kronstain-brown · 2026-03-19T12:39:32Z

src/app/docs/kagent/resources/release-notes/page.mdx

+
+If you were using the default SQLite backend, no migration is needed. The bundled PostgreSQL will be deployed automatically. You can optionally customize the bundled instance via `database.postgres.bundled.*` (storage size, image, credentials) as needed. See the [Database configuration guide](/operations/operational-considerations/#database-configuration) for details.
+
+Note that for production deployments, it is recommended to use your own external PostgreSQL instance. If you already are, you can keep your `database.postgres.url` or `database.postgres.urlFile` settings as before the migration.


Suggested change

Note that for production deployments, it is recommended to use your own external PostgreSQL instance. If you already are, you can keep your `database.postgres.url` or `database.postgres.urlFile` settings as before the migration.

Note that for production deployments, use your own external PostgreSQL instance. If you already are, you can keep your `database.postgres.url` or `database.postgres.urlFile` settings as before the migration.

kristin-kronstain-brown · 2026-03-19T12:41:21Z

src/app/docs/kagent/resources/tools-ecosystem/page.mdx

+
+| Tool | Description |
+|------|-------------|
+| `k8s_get_resources` | Query resources (pods, deployments, services, etc.). |


Signed-off-by: Art Berger <art.berger@solo.io>

https: //github.com/kagent-dev/kagent/pull/1527 Signed-off-by: Art Berger <art.berger@solo.io>

Signed-off-by: Art <artberger@users.noreply.github.com>

artberger self-assigned this Mar 12, 2026

artberger added documentation Improvements or additions to documentation kagent labels Mar 12, 2026

iplay88keys reviewed Mar 13, 2026

View reviewed changes

ProfessorSeb and others added 26 commits March 18, 2026 13:51

docs: remove CRD reference and enterprise pages, keep only core concepts

8cfb76d

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

memory topic updates based on demo

a6840b2

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

HITL topic updates based on demo

ef60ae8

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

add v0.8 release notes

d2872e6

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

apply style guide: second-person voice, active voice, periods on list…

9ea802f

… items, namespace in YAML Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

replace ASCII art diagram with structured prose in HITL architecture …

8e82391

…section Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>

add diagram for hitl

ef2a384

the rendering of the codeblock did not work Signed-off-by: Art Berger <art.berger@solo.io>

navigation

d912bd0

Signed-off-by: Art Berger <art.berger@solo.io>

revise based on testing

1b95400

Signed-off-by: Art Berger <art.berger@solo.io>

de-dupe

2be6f1b

Signed-off-by: Art Berger <art.berger@solo.io>

add links to blogs

d7431a8

Signed-off-by: Art Berger <art.berger@solo.io>

doc updates

be8c5eb

Signed-off-by: Art Berger <art.berger@solo.io>

local preview

30ceabf

Signed-off-by: Art Berger <art.berger@solo.io>

fix some cards

41dd62e

Signed-off-by: Art Berger <art.berger@solo.io>

rm unused images

7cd219f

Signed-off-by: Art Berger <art.berger@solo.io>

Remove SQLite

f977b76

Related to kagent-dev/kagent#1502 Signed-off-by: Art Berger <art.berger@solo.io>

more details on bundled Postgres

0f5a322

Signed-off-by: Art Berger <art.berger@solo.io>

link

1d6f03b

Signed-off-by: Art Berger <art.berger@solo.io>

emphasize external postgres for prod

7569e7d

Signed-off-by: Art Berger <art.berger@solo.io>

fix the sidebar nav

817d486

Signed-off-by: Art Berger <art.berger@solo.io>

Add yanivmn as co-author

17fd08c

Signed-off-by: Yaniv Marom Nachumi <yanivmar@amdocs.com> Signed-off-by: Art Berger <art.berger@solo.io>

Add yanivmn as co-author

334b149

Signed-off-by: Yaniv Marom Nachumi <yanivmar@amdocs.com> Signed-off-by: Art Berger <art.berger@solo.io>

dco test

0922925

Signed-off-by: Art Berger <art.berger@solo.io>

artberger force-pushed the add-comprehensive-docs branch from 683226e to 0922925 Compare March 18, 2026 17:53

artberger added 2 commits March 18, 2026 13:54

Merge branch 'main' into add-comprehensive-docs

e648ff3

Signed-off-by: Art Berger <art.berger@solo.io>

fix links

448a151

Signed-off-by: Art Berger <art.berger@solo.io>

kristin-kronstain-brown approved these changes Mar 19, 2026

View reviewed changes

artberger and others added 3 commits March 20, 2026 15:58

peer review

dcd4346

Signed-off-by: Art Berger <art.berger@solo.io>

Update for reworked bundled postrgres

89b6454

https: //github.com/kagent-dev/kagent/pull/1527 Signed-off-by: Art Berger <art.berger@solo.io>

Merge branch 'main' into add-comprehensive-docs

06c7b6e

Signed-off-by: Art <artberger@users.noreply.github.com>

Nadine2016 approved these changes Mar 20, 2026

View reviewed changes

artberger merged commit d5b609c into main Mar 20, 2026
3 checks passed

artberger deleted the add-comprehensive-docs branch March 20, 2026 20:14

		@@ -121,9 +121,6 @@ A Helm chart for kagent, built with Google ADK
		\| database.postgres.url \| string \| `"postgres://postgres:kagent@pgsql-postgresql.kagent.svc.cluster.local:5432/postgres"` \| \|

	- Shared storage. Memory uses the same kagent database (PostgreSQL), not a separate database.
	- Shared storage. Memory uses the kagent database (PostgreSQL), not a separate database.


		To enable memory, set the `memory` field on the declarative agent spec. The `modelConfig` field references a `ModelConfig` object whose embedding provider generates memory vectors.

		You can also configure memory in the kagent UI when you create or edit an agent by selecting an embedding model and setting the memory TTL.


		### Viewing Memories

		In the kagent UI, you can view the memories that an agent has saved. This lets you inspect what the agent has learned and retained from past interactions.


		## Limitations

		- No per-memory deletion. You can clear all memories for an agent, but you cannot delete individual memory entries.


		The `kagent-builtin-prompts` ConfigMap ships with five reusable templates: `skills-usage`, `tool-usage-best-practices`, `safety-guardrails`, `kubernetes-context`, and `a2a-communication`.

		For more information, see the [Agents](/docs/kagent/concepts/agents#prompt-templates) concept guide.

	For more information, see the [Agents](/docs/kagent/concepts/agents#prompt-templates) concept guide.
	For more information, see [Agents](/docs/kagent/concepts/agents#prompt-templates).


		Long conversations can now be automatically compacted to stay within LLM context windows. You can configure the `context.compaction` field to enable periodic summarization of older events while preserving key information.

		For more information, see the [Agents](/docs/kagent/concepts/agents#context-management) concept guide.


		Migration:

		If you were using the default SQLite backend, no migration is needed. The bundled PostgreSQL will be deployed automatically. You can optionally customize the bundled instance via `database.postgres.bundled.*` (storage size, image, credentials) as needed. See the [Database configuration guide](/operations/operational-considerations/#database-configuration) for details.


		If you were using the default SQLite backend, no migration is needed. The bundled PostgreSQL will be deployed automatically. You can optionally customize the bundled instance via `database.postgres.bundled.*` (storage size, image, credentials) as needed. See the [Database configuration guide](/operations/operational-considerations/#database-configuration) for details.

		Note that for production deployments, it is recommended to use your own external PostgreSQL instance. If you already are, you can keep your `database.postgres.url` or `database.postgres.urlFile` settings as before the migration.

	Note that for production deployments, it is recommended to use your own external PostgreSQL instance. If you already are, you can keep your `database.postgres.url` or `database.postgres.urlFile` settings as before the migration.
	Note that for production deployments, use your own external PostgreSQL instance. If you already are, you can keep your `database.postgres.url` or `database.postgres.urlFile` settings as before the migration.

	\| `k8s_get_resources` \| Query resources (pods, deployments, services, etc.). \|
	\| `k8s_get_resources` \| Query resources, such as pods, deployments, and services. \|

Conversation

artberger commented Mar 12, 2026

Uh oh!

iplay88keys Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kristin-kronstain-brown left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

iplay88keys Mar 13, 2026 •

edited

Loading