feat: add Gemini CLI session JSON normalizer

[adv3nt3]

Summary

Add _try_gemini_json parser for Gemini CLI session files stored at ~/.gemini/tmp/{project_hash}/chats/session-{timestamp}-{id}.json. This is the 7th normalize format for MemPalace, alongside Claude AI JSON, ChatGPT JSON, Claude Code JSONL, Codex CLI JSONL (#61), Slack JSON, and plain text.

Gemini CLI session format

Gemini CLI auto-saves every conversation as a single JSON file per session. Sessions are project-scoped — stored under a hash of the working directory. Retention defaults to 30 days / 100 sessions (configurable via settings.json).

Path: ~/.gemini/tmp/{project_hash}/chats/session-{timestamp}-{short_id}.json

Structure:

{
  "sessionId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "projectHash": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...",
  "startTime": "2026-03-30T10:28:04.070Z",
  "lastUpdated": "2026-03-30T10:28:16.793Z",
  "messages": [
    {
      "id": "xxxxxxxx-...",
      "timestamp": "2026-03-30T10:28:04.070Z",
      "type": "user",
      "content": [{"text": "Quick Terraform question about input validation..."}]
    },
    {
      "id": "xxxxxxxx-...",
      "timestamp": "2026-03-30T10:28:16.793Z",
      "type": "gemini",
      "content": "Yes, the validation is **worth adding**..."
    }
  ],
  "kind": "main"
}

Message types

type value	content format	Represents
"user"	List of {"text": "..."} blocks	User prompts
"gemini"	Plain string	Assistant replies

Other message types (model changes, tool calls, etc.) may appear in sessions but are skipped by this parser — only user and gemini carry conversation content.

Design decisions

Custom content extraction instead of shared _extract_content

Gemini user content blocks are {"text": "..."} without a "type" field. The shared _extract_content helper in normalize.py expects {"type": "text", "text": "..."} (the Claude/OpenAI convention) and returns empty string for Gemini blocks. Rather than modifying the shared helper (which could affect 5 other parsers), _try_gemini_json does its own extraction:

• Plain string → use directly
• List of dicts → extract "text" key from each block
• List of strings → join directly

Fingerprints on sessionId + messages keys

The parser requires both sessionId and messages in the top-level dict. This prevents false positives on:

• ChatGPT — has mapping key, no sessionId
• Claude AI — flat list or chat_messages wrapper, no sessionId
• Slack — is a list (not dict)
• Arbitrary JSON — unlikely to have both keys

Single JSON file (not JSONL)

Unlike Codex (JSONL per line) and Claude Code (JSONL per line), Gemini stores the entire session as one JSON object with a messages array. This means the parser registers in the _try_normalize_json dispatcher alongside the other JSON parsers (after json.loads), not in the JSONL section.

What's NOT handled (and why)

• Checkpoints / forked sessions: Gemini supports /resume save <tag> for manual checkpoints and conversation forking. These may create additional session files. The parser handles them the same as regular sessions — if it has sessionId + messages, it normalizes.
• Aborted/empty sessions: Sessions with fewer than 2 messages return None (same threshold as all other parsers).
• Tool call details: Only "user" and "gemini" message types are extracted. Tool calls, model changes, and thinking level changes are skipped — they're operational metadata, not conversation content.
• /chat share exports: Gemini can export conversations to Markdown or JSON via /chat share. The exported JSON format may differ from the auto-saved session format. This parser targets auto-saved sessions only.

Prior art

• PR docs: add Gemini CLI setup guide #106 (merged) added a Gemini CLI setup guide (docs only, no normalizer)
• Issue docs: Support Gemini CLI integration and hooks #107 (open) tracks Gemini CLI integration and hooks
• Format verified against real session files on disk and confirmed via Gemini CLI session management docs and Context7 (google-gemini/gemini-cli library)

Changes

1 file changed (mempalace/normalize.py), 47 insertions:

• New _try_gemini_json() parser function with custom content extraction
• Registered in _try_normalize_json() dispatcher alongside other JSON parsers
• Module docstring updated to list Gemini CLI JSON as supported format

Test plan

• ruff check mempalace/normalize.py passes clean
• ruff format --check already formatted
• python3 -m py_compile mempalace/normalize.py compiles OK
• Tested against 2 real local Gemini CLI sessions (2-turn and multi-turn) — produces correct > marker transcripts
• False positive check — returns None for Claude AI JSON, ChatGPT JSON, Slack JSON, plain dict, empty dict, and list inputs
• Pyright reports 0 new diagnostics
• Session storage path and format confirmed via Gemini CLI docs and Context7

Refs: #59

[adv3nt3]

@bensig Same CI failure as PR #44 — not from this PR. Both failing tests are in test_dialect.py, unrelated to normalize.py:

1. TestCompressionStats::test_stats — KeyError: 'ratio'
2. TestCompressionStats::test_count_tokens — old heuristic vs new word-based counting

Pre-existing test-vs-code mismatch on main since PR #147 changed the stats API. PR #150 is the fix. All 97 other tests pass.

[web3guru888]

✨ Review of #155 — feat: add Gemini CLI session JSON normalizer

Scope: +47/−1 · 1 file(s)

• mempalace/normalize.py (modified: +47/−1)

Suggestions

• 💡 No tests included — consider adding coverage for the new code paths

🟢 Approved — clean, well-structured PR. Good work @adv3nt3!

---

_{🏛️ Reviewed by MemPalace-AGI · Autonomous research system with perfect memory · Showcase: Truth Palace of Atlantis}

[igorls]

Hi, thanks for the contribution.

This PR has merge conflicts with develop, and the branch has not been updated in over 7 days, which puts it before our most recent release. The conflicts are likely against work that landed in that release.

Could you rebase onto develop so we can take another look?

If this change is no longer relevant, feel free to close the PR.

(This message is part of a periodic backlog pass, sent to all open PRs that match this state.)

[adv3nt3]

Closing — superseded by #1234 (merged), which adds Gemini CLI session support via `_try_gemini_jsonl` against the actual JSONL session format (`~/.gemini/tmp/<project_hash>/chats/session-*.jsonl`, per google-gemini/gemini-cli#15292).

This PR (#155) was written against an older single-JSON shape (`session-*.json` with `sessionId` + `messages` array) that doesn't match what Gemini CLI actually writes today. Milla's #1234 also landed a follow-up (#e7fe6ca) hardening detection so user/gemini turns appearing before the `session_metadata` sentinel are discarded — that's stronger than what was in this PR.

No code worth porting. Thanks for the patient backlog ping.