GoogleCloudPlatform/kubectl-ai

[Feature]: Add session persistence for unimplemented LLM providers

Open

#461 opened on Aug 8, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (708 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (7,532 stars)
PR merge metrics
 (PR metrics pending)

Description

#443 added session persistence for Gemini, but other providers were left unimplemented.

We should add similar implementation for other providers, where Initialize() will convert api messages to provider-specific messages and add them to the chat history. We should add this for all the providers that don't have them, and keep it in mind for any future providers added.

Adding tests is also very welcomed. Basic flows like saving and loading sessions, creating a new session, deleting a session, and listing sessions should be covered. Edge cases like invalid session ID and corrupted save file should also be covered.

Contributor guide

Research direction
Read the implementation in PR #443 to understand the pattern for session persistence with Gemini. Then identify all other LLM providers that lack this feature. For each provider, replicate the pattern: modify `Initialize()` to convert API messages to provider specific messages and add them to chat history. Write tests covering basic flows (save, load, create, delete, list sessions) and edge cases (invalid session ID, corrupted save file).
Tech stack
go
Domain
backendai
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Gokubectl ai basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60