Introduce the LLM session manager classes #141
Conversation
There was a problem hiding this comment.
Left some feedback! Great start. From an interface design perspective, I'd think about what are the key public methods that the user will have access to in order to manipulate or read from the session state. this is what I was able to derive :)
conversation_history- loads full conversation history. What about just last 10 messages (the naive session retrieval approach)?fetch_context- fetches session data based on semantic similarity to text inputload_previous_sessions- loads previous session data (how is this diff than the first method)store- store exchanges into the db!
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #141 +/- ##
==========================================
- Coverage 88.60% 83.07% -5.54%
==========================================
Files 29 31 +2
Lines 1667 1778 +111
==========================================
Hits 1477 1477
- Misses 190 301 +111 ☔ View full report in Codecov by Sentry. |
justin-cechmanek
force-pushed
the
jc/semantic-session-manager
branch
from
d9ccb26
to
c20d23e
Compare
|
|
||
| schema = IndexSchema.from_dict({"index": {"name": name, "prefix": prefix}}) | ||
|
|
||
| schema.add_fields( |
There was a problem hiding this comment.
Style comment: might make a function for creating index and adding fields outside the init
…alidation to field names
tylerhutcherson
changed the title
tylerhutcherson
changed the title
Here's the proposed class for LLM session management. It support recent or full conversation storage & retrieval, as well as relevance based conversation section retrieval.