We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very often with bigger/longer prompts (or if using prompt for data), conversation name is meaningless, leaving user hard time searching db.
Very often setting name of the conversation by the user at prompt time would solve the problem.
Easy solution: --name TEXT -> sets conversation_name to TEXT
Better: --name TEXT -> sets conversation name to TEXT + prompt or system_prompt (meaning this is prefix for name)
Best: allow --name TEXT be used in 'llm prompt' but also in 'llm logs list --name TEXT' returning all conversations having TEXT in conversation_name
p.s. this would be ultra helpful for use cases like this: https://til.simonwillison.net/llms/claude-hacker-news-themes where I would like to put HN url at the begining of conversation_name :)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Very often with bigger/longer prompts (or if using prompt for data), conversation name is meaningless, leaving user hard time searching db.
Very often setting name of the conversation by the user at prompt time would solve the problem.
Easy solution:
--name TEXT -> sets conversation_name to TEXT
Better:
--name TEXT -> sets conversation name to TEXT + prompt or system_prompt (meaning this is prefix for name)
Best:
allow --name TEXT be used in 'llm prompt' but also in 'llm logs list --name TEXT' returning all conversations having TEXT in conversation_name
p.s. this would be ultra helpful for use cases like this: https://til.simonwillison.net/llms/claude-hacker-news-themes where I would like to put HN url at the begining of conversation_name :)
The text was updated successfully, but these errors were encountered: