[BUG] Conversation History Not Persisted — brain/ directories empty, no Knowledge Items generated

Description

Conversation history (brain logs, artifacts, knowledge items) is never persisted to disk. The agent cannot retrieve or reference any past conversations.

Environment

  • Antigravity Version: 1.19.6
  • VSCode OSS Version: 1.107.0 (user setup)
  • Commit: d2597a5c475647ed306b22de1e39853c7812d07d
  • Date: 2026-02-26T23:07:23.202Z
  • Electron: 39.2.3 / Chromium: 142.0.7444.175
  • Node.js: 22.21.1 / V8: 14.2.231.21-electron.0
  • OS: Windows_NT x64 10.0.26200
  • Language Server CL: 875890115

Problem

The agent’s persistent context system is non-functional. While conversation .pb files are correctly saved to ~/.gemini/antigravity/conversations/, all supporting data structures that enable cross-conversation memory are empty:

  1. brain// directories are all empty: Directories are created for each conversation but no files (logs, overview.txt, artifacts) are ever written inside them. The system prompt references <appDataDir>/brain/<conversation-id>/.system_generated/logs but this path never gets populated.

  2. knowledge/ directory contains only a lock file: No Knowledge Items (KIs) are generated. The knowledge subagent either never runs or has no source data (brain logs) to process.

  3. context_state/ directory is empty: No cross-conversation context state is maintained.

  4. implicit/ contains .pb files with IDs not matching any conversation: 2 .pb files exist with UUIDs that don’t correspond to any conversation in conversations/.

Impact

  • Agent cannot reference or build upon previous conversations
  • No Knowledge Items are generated, making the knowledge discovery system non-functional
  • Conversation summaries shown at the start of each chat are the only cross-conversation context available, but the agent cannot read the actual logs/artifacts from those conversations
  • The “persistent context” feature described in the system prompt is entirely broken

Evidence (filesystem snapshot)

~/.gemini/antigravity/
├── conversations/ → 9 .pb files (conversations ARE saved)
├── brain/ → 9 subdirectories, ALL EMPTY (0 files each)
├── knowledge/ → only knowledge.lock (0 KIs)
├── context_state/ → empty
├── implicit/ → 2 .pb files (IDs don’t match any conversation)
├── mcp_config.json
├── onboarding.json
└── installation_id

App log reference

From Antigravity.log, the app does reference the correct data path:
“Touching accessed time for KI ~/.gemini/antigravity/knowledge/knowledge.lock”
This confirms ~/.gemini/antigravity/ is the intended data directory, but brain logs and KIs are never written.

Steps to Reproduce

  1. Open Antigravity (v1.19.6) on Windows
  2. Have multiple chat conversations across different sessions (I have 9 conversations saved)
  3. Start a new conversation and ask the agent to reference a previous conversation
  4. Agent fails to retrieve past conversation details because brain/ directories are empty

Verification steps (run in PowerShell):

Check that conversations are saved:

ls ~/.gemini/antigravity/conversations/

→ Shows .pb files ✓

Check that brain dirs are empty:

ls ~/.gemini/antigravity/brain/ -Recurse

→ Only empty directories, no files ✗

Check knowledge is empty:

ls ~/.gemini/antigravity/knowledge/

→ Only knowledge.lock, no KI folders ✗

Expected: brain// directories should contain conversation logs, artifacts, and overview files. knowledge/ should contain generated Knowledge Items.
Actual: All brain directories are empty. No KIs exist. Agent has no way to access past conversation content.

1 Like

Hello @San0304, welcome to AI Forum!
Thank you for bringing the issue with conversation history to our attention. Our engineering team is currently investigating the matter, and we appreciate your patience as we work toward a resolution.

2 Likes

I have solved this problem and explained at Knowledge: how to make it works? - #19 by BJ1

Is this supposed to fix knowledge item creation too?

in the lastest version still the same problem chat bug. and this error too Trajectory ID: 71f9f26a-50c6-4e70-ab2f-9c6563746a42

Error: agent executor error: trajectory converted to zero chat messages

(1) attached stack trace

– stack trace:

| google3/third_party/jetski/cortex/cortex.(*CascadeManager).executeHelper.func1

| third_party/jetski/cortex/cascade_manager.go:2096

| […repeated from below…]

Wraps: (2) agent executor error

Wraps: (3) attached stack trace

– stack trace:

| google3/third_party/gemini_coder/framework/generator/generator.(*requestBuilder).buildRequest

| third_party/gemini_coder/framework/generator/request_builder.go:122

| google3/third_party/gemini_coder/framework/generator/generator.(*PlannerGenerator).generateWithAPIRetry

| third_party/gemini_coder/framework/generator/planner_generator.go:279

| google3/third_party/gemini_coder/framework/generator/generator.(*PlannerGenerator).generateWithModelOutputRetry

| third_party/gemini_coder/framework/generator/planner_generator.go:156

| google3/third_party/gemini_coder/framework/generator/generator.(*PlannerGenerator).Generate

| third_party/gemini_coder/framework/generator/planner_generator.go:94

| google3/third_party/gemini_coder/framework/executor/executor.(*Executor).executeLoop

| third_party/gemini_coder/framework/executor/executor.go:355

| google3/third_party/gemini_coder/framework/executor/executor.(*Executor).Execute

| third_party/gemini_coder/framework/executor/executor.go:277

| google3/third_party/jetski/cortex/cortex.(*CascadeManager).executeHelper.func1

| third_party/jetski/cortex/cascade_manager.go:2061

| google3/third_party/jetski/cortex/cortex.(*CascadeManager).executeHelper.func2

| third_party/jetski/cortex/cascade_manager.go:2144

| runtime.goexit

| third_party/go/gc/src/runtime/asm_amd64.s:1774

Wraps: (4) trajectory converted to zero chat messages

Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.leafError.