Repository navigation
refactor(llm-helper): graduate the LLM helper from examples/ to extensions/ - #46
Merged
Merged
Conversation
…sions/ The helper is no longer a sample to copy but a function host an installation runs to give its engines an LLM, so it moves to extensions/llm-helper/; examples/ keeps the demo app. Files, routes, contract and configuration keys are unchanged. The sdist and the type check include the new folder, the tests load the helper from it, and the README commands, the demo app's links, the consumer folder table, the test report and the CHANGELOG (Unreleased, Changed 2) follow. The Node.js twin still lives in mercury-nodejs examples/llm-helper until it moves the same way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
acn-ericlaw
added a commit
that referenced
this pull request
Nov 3, 2026
…M helper in extensions/, its loop contract); llm-chat-loop-contract closed Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
examples/llm-helper/moves toextensions/llm-helper/: three renames, no content change to the app (llm_helper.py, its README andresources/application.yml).examples/keeps the demo app.only-includeand the basedpyrightincludegainextensions; the tests load the helper from the new folder.system/AGENTS.md(a newextensions/row), the pack's test report (its link to the folder onmainand its reproduce command), and the repository structure inmemory/instructions.md. CHANGELOG Unreleased, Changed 2, with the upgrade note. Released CHANGELOG sections keep the old path as history.examples/llm-helperin the docstring and the README: mercury-nodejs has not moved yet./tmpwith absolute paths, the app logsConfiguration: .../extensions/llm-helper/resources/application.ymland answers/infoasllm-helper(the resources-folder rule holds in the new place).uv build --sdistlistsextensions/llm-helper/besideexamples/demo-app/.Why
The helper is no longer a sample to copy. It is a function host an installation runs to give its engines an LLM, and the next change makes it the model turn of the engines' agent loop (RFC-0011 in mercury-composable), with a transcript store of its own. The maintainer's direction is that it graduates from an example to an extension, as optional add-ons do in the engine repository. The move goes in a PR of its own, ahead of that feature, so a reviewer reads a pure rename here and the loop contract on its own in the next PR (
feat/llm-chat-loop-contract, which is rebased ontomainonce this merges).Upgrade note: start the helper as
mercury-serve extensions/llm-helper/llm_helper.py(orpython extensions/llm-helper/llm_helper.py); a script or a deployment that names the old path changes it. The routes, the contract and the configuration keys are unchanged.Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
🤖 Generated with Claude Code