Mechanism for models to influence Markdown display of their logs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.5k
- Forks
- 991
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
It's a bit annoying that the only way to see the log probs is to dig around in the SQLite database for them.
[...]
One option would be to teach the
llm logsMarkdown output how to display them. That's nicer than messing around in SQLite directly.It's a bit weird to have code in
llm logsthat's specific to the OpenAI models though. Maybe I should add a model plugin mechanism that allows models to influence the display of logs?
Originally posted by @simonw in https://github.com/simonw/llm/issues/284#issuecomment-1724782862
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the llm logs Markdown output path and its existing OpenAI-specific handling, then inspect how log probabilities are stored in SQLite. Define what a model plugin must control and consider the issue complete when model-specific log display works without hard-coded OpenAI logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100