WIP: Fragments

[simonw]

Refs:

• Option for passing in longer context fragments, stored in a deduped table #617

TODO:

• Make aliases such as llm prompt -f alias work
• Document how to use -f option
• llm fragments list needs non-JSON output (that truncates)
• Documentation for the llm fragments family of commands
• Does this need documentation in the Python docs?
• Fix the problem where prompt_json still duplicates the prompt
• Comprehensive tests
• Update llm logs to handle this new mechanism
• Add this to llm chat - so you can do llm chat -f docs
• Consider if this should be added to templates (maybe not?)

[simonw]

Here's a but of a weird problem. We're storing fragments in the logs.db database - but that means this logic here isn't quite right:

llm/llm/cli.py

Lines 476 to 482 in 9b2d4d6

	# Log to the database
	if (logs_on() or log) and not no_log and not async_:
	log_path = logs_db_path()
	(log_path.parent).mkdir(parents=True, exist_ok=True)
	db = sqlite_utils.Database(log_path)
	migrate(db)
	response.log_to_db(db)

Here we are only even creating that logs.db database at the very end of prompt() if the user has logging enabled.

But now we need that database at the start of that CLI command in case we need to resolve any fragment aliases using it.

It's a bit weird that it's called logs.db now that it's supporting an additional feature that's not related to if logs are turned on or not. I think I can live with that though.

[simonw]

Lots more fragments available now - I added Datasette, sqlite-utils, s3-credentials and shot-scraper docs to https://github.com/simonw/llm-docs