simonw/llm

Figure out truncation strategy for continue conversation mode

Open

#73 opened on Jul 1, 2023

View on GitHub
 (11 comments) (2 reactions) (0 assignees)Python (877 forks)github user discovery
help wantedresearch

Repository metrics

Stars
 (12,006 stars)
PR merge metrics
 (PR metrics pending)

Description

I'm still not clear on the best way to truncate messages in continue mode, right now I'm going to leave that and allow the model to return an error - but it would be good to have a strategy for that involving automatic truncating later on.

Originally posted by @simonw in https://github.com/simonw/llm/issues/65#issuecomment-1616021169

Contributor guide

Research direction
Study the current continue conversation implementation in the codebase. Explore truncation strategies such as limiting token count or message count, and evaluate trade offs between context preservation and API limits.
Tech stack
python
Domain
cli
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.
Half day
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.
Needs investigation
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35