Skip to content

learned: Session data uses K8s CRDs not PostgreSQL (demo mo8yev8c) #1394

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

Closed
jeremyeder wants to merge 1 commit into from
Closed

learned: Session data uses K8s CRDs not PostgreSQL (demo mo8yev8c) #1394

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 10 additions & 0 deletions ...rrections/2026-04-21-session-data-uses-k8s-crds-not-postgresql-demo-mo8yev8c.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
---
type: correction
date: 2026-04-21T18:26:27Z
author: system-serviceaccount-ambient-code-test-user
title: "Session data uses K8s CRDs not PostgreSQL (demo mo8yev8c)"
---

The Ambient Code Platform stores session data in Kubernetes Custom Resources (AgenticSession CRDs), not in PostgreSQL. The backend creates the CR, the operator watches it and creates a K8s Job to run the agent. PostgreSQL is only used by the ambient-api-server component for its own data model.

Source: User corrections during session — agent incorrectly described the storage layer.
Loading